New Lastedit extension

[pftnhr]

I made a little extension that shows the last modification date of your pages. The only requirement is that the page setting Published: must be present. If this is missing, nothing is output.

The extension is available here: https://github.com/pftnhr/yellow-lastedit

If you find the extension useful, I would be happy if you try it out and report issues to me if necessary.

[GiovanniSalmeri]

Thank you very much for your useful extension! Just an observation and a question.

Regarding the output, I wonder whether a more CSS-friendly one would be better, for example

$output .= "<p class=\"lastedit\">" . $lasteditText . ": " . $page->getDateHtml("modified") . "</p>";

(without the previous <br />). In this way the appearance of the output could be easily modified without tampering with the PHP code, but only adding a CSS declaration.

The question: is there a specific reason why you chose to avoid any output when Published is not set? I can imagine several uses when a "last modified" date would be useful even when this setting is lacking.

Thank you!

[pftnhr]

Hello Giovanni,

you're absolutely right. At this point, I had started from my theme, in which I want to use as few CSS classes as possible. But I changed it and now it is easier to handle in the end.

The question: is there a specific reason why you chose to avoid any output when Published is not set? I can imagine several uses when a "last modified" date would be useful even when this setting is lacking.

My reason for this is that I use the feature for blog posts and only want to output it there if the release date is at least 24 hours before the last edit. Since no publish date is generated by default for pages, the calculation is not necessary and it is probably also easier to simply write the date of the last edit in the content.

PS.: But since I have you "on the line" right now, could you please give me the correct Italian translation so I can add to it? 😄

[markseuffert]

About languages, I suggest to use the following process. New extensions should include at least the English language strings and they should include max en de sv. Additional languages should be collected somewhere else, apart from the installation files, otherwise they grow too large over time. Of course, once an extension becomes published it can make full use of our multi language support with about 20 languages. See also #841.

[GiovanniSalmeri]

This is the italian 🇮🇹 translation:

Language: it
LasteditText: Ultima modifica