jjennings
I'm new here

Historical Deployment - generation error on moved media

Jump to solution

Hi,

This is a specific question resulting from an historical deployment we have set up. The original post to Historical Deployment how-to can be found here:

https://community.e-spirit.com/thread/2380?tstart=0

We have the script and works almost as expected. We have noticed that media from a remote media project are not correctly generated if one of those media was moved.

The basic set up is:

- Through a script we generate an earlier state at a given date then generate the content.

- In the past an image for example was moved from one folder to another. On generating the folder from a point earlier to when the image was moved, the image is not deployed.

- If the generation is made after the move, the media is correctly deployed.

Are media references also revisioned? Is there something we can do about this?

Thanks in advance.

0 Kudos
1 Solution

Accepted Solutions
klein
Crownpeak employee

Hi,

I've got the answer from our developers and I grant them that the current behaviour isn't a bug, but a not implemented feature. Because historical generation applies only to the current project but not to Master-Remote project. Remote media nodes won't be generated but referenced only! So you reference always the last deployed state of remote media nodes.

That means if you want to reference historical media, then at first you should generate them and then care for their deployment!

By the way, don't hesitate to post in the community a new feature request in terms of these issue!

Best regards,

Walter.

View solution in original post

0 Kudos
10 Replies
re-lounge
I'm new here

Hallo Community,

unser Kunde hakt zu diesem Thema immer wieder nach und möchte den aktuellen Stand wissen. Da wir zu dieser Fragestellung bisher weder in diesem Thread noch in dem parallel erwähnten Thread eine Rückmeldung erhalten haben, müssen wir aktuelle davon ausgehen, dass eine historische Generierung in einem Remote-Media-Umfeld grundsätzlich nicht möglich ist.

Bitte bestätigen oder falsifizieren Sie dies, damit wir ggf. einen FeatureRequest erstellen und unserem Kunden Bescheid geben können.

Beste Grüße,

Stefan Häfele // re-lounge

0 Kudos

Hallo Herr Häfele,

es tut mir leid, aber ich verstehe das Szenario nicht Smiley Sad

- Sie führen eine historische Generierung in einem Projekt durch.

- Das Projekt hat Remote Referenzen.

- Ich nehme an, dass Sie nun eine historische Medien-Generierung im Remote Projekt durchführen, um die Ziele der entsprechenden Remote Medien Links zu erzeugen.

Soweit glaube ich folgen zu können.

Aber warum ein Medium, was verschoben wurde, nun nicht erzeugt wird, verstehe ich nicht so ganz.

Welche Startpunkte der Generierung haben Sie denn definiert? Diese müssen die entsprechenden Medien _zum Zeitpunkt der Generierung_ enthalten [haben].

Aufgrund der Beschreibung klingt es erst einmal für mich so, als würden die falschen Startpunkte gewählt werden [die Ordner, in denen die Medien sich aktuell befinden und nicht die, in denen sich die Medien sich damals befanden]

Andererseits klingen die Fragen danach, als würden die Medienreferenzen auf die falschen Zielpfade verweisen.

Können Sie bitte einmal klarstellen, was das genaue Problem ist?

Viele Grüsse aus Dortmund,

  Holger Höbbel

0 Kudos

Hi Holger,

Thanks for the response.

Your comment makes sense. It is so that the media was in another folder at that time. When I generate the current folder - it isn't there: that fits your suggestion. But if I generate the media itself, it generates it in its current folder: this seems strange and wouldn't fit your suggestion.

In addition, when the project HTML is generated, the path for the media is to its current folder, and not the folder where the media had been, so the media if of course not found. Again - this is inconsistant with your suggestion. Somewhere here seems to be an inconsitency.

Thanks.

0 Kudos

Hi Holger -

We are still waiting for a response to the problem we appear to have.

 

Here is this clarified once more:

We generate a page on a given date in the past and it produces this HTML:

<img src="/mediapool/media/bilder/produkte/erdgas_2/erdgas_kampagne_2009/2009_9/Erdgas_BIO_370px_BREITE_370.jpg" alt="">

We generate also for that date the parent folders for /media/bilder/produkte/erdgas_2/erdgas_kampagne_2009/ in the media pool. And it generates the expected files - in their proper folders for that date.

On that past date though - the images were under erdgas_kampagne_2009/ and not erdgas_kampagne_2009/2009_9 (as it currently is in the media pool).

So - the HTML generation generates on that date in the past a URL that links to the current media folder structure, and not that from the given date.

This seems like an error to us.

Could you please confirm this soon? We want to wrap up this problem here.

Thanks.

0 Kudos

Hello,

Since it indeed seems to be a bug, which cannot be analysed here in the community, I would ask you to set an appropriate helpdesk ticket so that I or my colleagues can take care of it. Just make a short summary, and otherwise refer you to this community entry

Best regards,

  Holger

0 Kudos
klein
Crownpeak employee

Hi,

this seems to be a bug (internal ID: 114667)

We will let you know as soon as we get further information concerning this bug or a bug-fix release is available.

Best regards,

Walter.

Helpdesk

0 Kudos
klein
Crownpeak employee

Hi,

I've got the answer from our developers and I grant them that the current behaviour isn't a bug, but a not implemented feature. Because historical generation applies only to the current project but not to Master-Remote project. Remote media nodes won't be generated but referenced only! So you reference always the last deployed state of remote media nodes.

That means if you want to reference historical media, then at first you should generate them and then care for their deployment!

By the way, don't hesitate to post in the community a new feature request in terms of these issue!

Best regards,

Walter.

0 Kudos

Hi,

Can you clarify exaclty what you mean:

That means if you want to reference historical media, then at first you should generate them and then care for their deployment!

We are already generating the media on a given date. How do we "care for their deployment"? Do you mean we need to generate and deploy the media for a given date and then generate and deploy the project on the given date so that then the references will be correct???

Not so clear here on how to realize this correctly - or if it is really possible.

0 Kudos
klein
Crownpeak employee

Hi,

We are already generating the media on a given date

but do you also generate the media on a historical date in you master project? So I mean if you generate histical content in your slave project, you also should generate historical state of the referenced media in your master project and then deploy the generated historical media to the remote path on your live webserver, where the deployed pages from your slave project reference these remote media.

Do you mean we need to generate and deploy the media for a given date and then generate and deploy the project on the given date so that then the references will be correct???

yes - see above.

0 Kudos