timestamp to date Problematik

[guay]

Wer mit dem Attribut 'timestamp' arbeitet, sieht sich bald mit folgendem Problem konfrontiert: Im Backend als 2011-08-20 erfasst, möchte ich diesen Wert in einer Liste nur als Jahr (2011) ausgeben, in der Detailansicht jedoch das ausgeschriebene, lokalisierte Datum sehen, z.B. 20. August 2011. Bei der lokalisierten Datumsabgabe muss ich jedoch mit Arrays arbeiten, da date() grundsätzlich nur Englische Begriffe ausgibt. Gibt es eine Möglichkeit im Backend das Datumsformat und die Sprachversion anzugeben?
(Anbei beide überarbeiteten Attributs-Templates)

[MiniModel]

This issue has been labeled with "testing" but got no feedback.

We are reliant on feedback to prove a ticket fixed as we can not tell if the ticket has been resolved if we receive no feedback.
I will close this ticket now, as I assume it has been resolved.
If the ticket should still be valid, please feel free to reopen it.

@guay could you please have a final look at this and tell if your issue has been resolved?

[guay]

Looks good. Tested with nightly dev (2013-07-10, 15:00).
The discription below the format field sounds a little bit too technical. "... The format string will be parsed with the PHP date() function." One or two simple examples like 2013-10-03 => d. M. Y => 03. Okt. 2013 would be helpful for those who know nothing about PHP. Thanx for the great job.

[tognit]

Hello,
after the update, I get the following error message:

Fatal error: Call to undefined method stdClass::get() in /system/modules/metamodelsattribute_timestamp/MetaModelAttributeTimestamp.php on line 63

Grüessli
Steven

[discordier]

Are you sure you are using the dev version of the nightly core with the dev version of the attribute?

[tognit]

With the dev version the error is no more. Thanks for the info!

But now I have the problem that in the backend list only the timestamp format appears. But I would like to sort by years. Like in the catalog.

Thank you

[discordier]

This is a seperate issue, please check if already reported and, if not, file a new one.
We rather do not clutter this ticket with unrelated stuff. Feel free to mention this ticket in the new one though.