Support

Akeeba Backup for Joomla!

#18197 JDispatcher fatal error: PLG_SRP_TITLE

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by lausianne on Thursday, 21 November 2013 01:24 CST

lausianne
EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:

Hi Nicholas,

I just updated Akeeba Bakup to 3.9.0, then noticed that I get a JDispatcher redeclare error when trying to open the Extensions Manager in the backend. Google led me to the above mentioned thread in your forum, so I disabled system plugins as you suggested and found that the issue comes from PLG_SRP_TITLE which apparently is your own plugin. So I hope you have a fix for it ...

Thanks!

nicholas
Akeeba Staff
Manager
I have an idea (based on other user's feedback). Can you please try clearing the Joomla! cache, both front-end and back-end, and tell me if it made any difference?

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

lausianne
Thanks for the suggestion. I should do that anyway after each installation. NoNumber extensions always ask to do that ...
Anyway, this time it did not help. I cleared Chrome browser cache and used Site Maintenance > Clear cache. Then I deleted all cache files manually. Anything else?
(One success was that the plugin has it's name back, "System - System Restore Points")

But NOW, just now: I updated another site, where the current version was 3.9.1. So after cleaning all caches, I searched for the same update (no announcement, I had to search for it), installed it on the problem site, and now it's fine.
What's funny, is that now I am asked to update from 3.9.1 to 3.9.0 ... won't do it.

nicholas
Akeeba Staff
Manager
3.9.1 was released half hour after my last reply, fixing the issue. Regarding the update number confusion it's because of the update caching and the CDN time to live. It will be sorted out in a few hours. So, recap:
- Upgrade to 3.9.1
- If it says 3.9.0 is the latest version wait 8-12 hours, it will fix itself

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

lausianne
All right, good to know. No big deal anyway. Have a good day!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!