Year wrong Copyright © 2008-2017 e107.org

[Alex-e107nl]

@e107help in e107_core\templates\admin_template.php you find the line
<!--<div class="admin-copyright"><small>Copyright &copy; 2008-2017 e107.org</small></div>-->
That is not right, can you change the 2017 into 2026, or better call a function with the the year we are living in now?

Or did the copyright? ended in 2017 :-)

[e107help[bot]]

@Alex-e107nl good news: nobody has been looking at a 2017 copyright. That line sits inside an HTML comment, so it renders nothing.

The copyright that does render, on the Credits page, is already dynamic: credits.php:53 prints 2008- plus date('Y'), so it says 2026 today and 2027 in January on its own. I grepped e107_admin/, e107_core/ and the shipped themes for any other copyright year that reaches a page and there isn't one.

So the dead line is gone in #5984 rather than being given a fresh year to go stale. Whether the admin should carry a footer copyright at all is a question for Deltik, and if it comes back it wants date('Y') too, so I've left the .admin-copyright CSS in place rather than prejudge that.

[Alex-e107nl]

When the admin theme gets a footer in BS5 it is usable in this form:

Copyright &copy; 2024-'.date('Y').' <a href="https://www.e107.org" class="link-secondary"> e107.org </a>

[e107help[bot]]

@Alex-e107nl that shape works, with one swap: 2008- rather than 2024-, because that is what the rendered copyright already prints (credits.php:53). Nothing turns on 2008 being e107's true birth year, and it is not (the oldest release in this repository is v0.5.4, October 2002). What matters is that the admin and the Credits page not print two different ranges for the same project.

Whether the admin carries a footer at all is still Deltik's call, which is why #5984 took out the dead markup and left the .admin-copyright rule in kadmin.css:14442 alone. Your snippet is ready for the day he says yes.

[Deltik]

@e107help: An admin footer would be useful if it showed the current build of e107 (like e107 v2.3.12 for stable versions, e107 v2.4.0-alpha1 for tagged pre-release versions, e107 <a href="https://github.com/e107inc/e107/commit/195eed92fcca30e99135dd254a7f6cde285f2e36" target="_blank">v2.4.0-123-g195eed92fc</a> possibly from git describe --tags --dirty, or whatever we have from e107_admin/ver.php if Git versioning is not derivable for whatever reason).

That's the direction I would like to go, so when you're up for it, we can plan out this feature in a new GitHub issue.

[e107help[bot]]

@Alex-e107nl, this started with the 2017 copyright line you spotted, and it has turned into a feature. I have written it up as #6066, following @Deltik's direction above: an admin footer that names the build you are running.

Your date('Y') copyright snippet is in there as one of the open decisions, because a build string and a copyright line can perfectly well share one footer. If you have a view on whether it should carry both, the issue is the place to say so while the shape is still open.

The rest is Deltik's to settle, starting with whether core may run git on a page request at all.