Possibly want to make the link configuration driven, so that the installation can override if they have a specific 'interim' page explaining a custom version. That is, company uses phpESP for core functionality, but tweaks it slightly for their needs. They want to link to a tweaked version information page, then that page can link back to phpESP.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I like the approach that the authors of Gallery take: only display this on administrative pages; user pages say nothing about the tool, allowing the administrator/deployers to customize it as they see fit (e.g.: a link to the company's IT group responsible for supporting the application).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Makes sense to me: +1
Possibly want to make the link configuration driven, so that the installation can override if they have a specific 'interim' page explaining a custom version. That is, company uses phpESP for core functionality, but tweaks it slightly for their needs. They want to link to a tweaked version information page, then that page can link back to phpESP.
I like the approach that the authors of Gallery take: only display this on administrative pages; user pages say nothing about the tool, allowing the administrator/deployers to customize it as they see fit (e.g.: a link to the company's IT group responsible for supporting the application).
go ahead and patch it :-)
If it gets patches soon enough, it can still get in this version.
Franky