User tests: Successful: Unsuccessful:
We removed the message from new installs back in 2015 #6199
it has not been possible to use eaccelerator since 3.4 iirc
This file is just a remnant that should have already been removed
we certainly dont need to maintain the language strings or update the code ;)
/**
- Checks if the eAccelerator caching method is enabled.
- This check should be done through the 3.x series as the issue impacts migrated sites which will
- most often come from the previous LTS release (2.5). Remove for version 4 or when eAccelerator support is added.
- This check returns true when the eAccelerator caching method is user, meaning that the message concerning it should be displayed.
- @return integer
- @SInCE 3.2
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_admin |
Labels |
Added:
?
|
Category | Administration com_admin | ⇒ | Administration com_admin Language & Strings |
oops forgot to commit the change before pushing
I have tested this item
Labels |
Added:
?
|
update branch to retrigger drone
How to test?
@rmittl you will need to install the patch and check the deleted file has gone as well as the language strings. It will require FTP access. If you are doing PBF then you possibly may not have FTP which will mean a localised install. I'll give it a go so you can move onto another issue if you are still working.
Do we need to trash the message from the database? I don't remember exactly how this component works anymore
Status | Pending | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-11-11 22:26:31 |
Closed_By | ⇒ | wilsonge |
OK merging. I think we probably need to revisit that policy decision. Inconsistent release leads these days
Thanks. Policy is not my area
Remove language strings?