Support

Akeeba Backup for Joomla!

#36364 updating latest fof40

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 nicholas on Friday, 07 January 2022 08:46 CST

gstyles

After updating FOF40 to the latest version today my site is Bricked, I can not exit the admin page,the "Return to Dashboard does nothing" all menu items do nothing? I am unable to access the front of the site,I get  0 Class "FOF40\Container\Container" not found .Help please.G Styles.

gstyles

Just seen the other post about FOF40 and I am using engage as well.

nicholas
Akeeba Staff
Manager

Delete plugins/system/engage. Log into your administrator. Upgrade to Engage 3.

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!

gstyles

I have deleted the system plugin and have my site back.

When installing engage 3 I get ;

This command is not supported in the prepared statement protocol yet Package Update: There was an error installing an extension: com_engage.zip danger Error installing package

gstyles

I have restored from the backup I made before updating and all is well for now. When the engage 3 is sorted will it just update or will I need to delete the plugins first? Thanks GS

nicholas
Akeeba Staff
Manager

This command is not supported in the prepared statement protocol yet

This is a Joomla bug.

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!

nicholas
Akeeba Staff
Manager

To clarify, it's a Joomla bug that's only trigger on MariaDB databases. This does not happen with MySQL itself.

I saw this problem myself on a live server using MariaDB and found that there was an issue in Joomla but it was closed as something that has to do with the DB server, not with Joomla itself.

I will publish a new version of Engage 3 which does not use these SQL queries to let you update on MariaDB servers.

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!

gstyles

Good morning,just tried the update of Engage and the FOF on a local test site and there are errors.Please see attached.

nicholas
Akeeba Staff
Manager

You are still trying to install Akeeba Engage 2. As I said before, please install Akeeba Engage 3.0.1. It is the only version of Akeeba Engage we currently support on Joomla 4.

If you do not see this version in your Joomla extensions update page download it from our site and install it on your site using System, Install, Extensions without uninstalling the previous version.

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!

gstyles

Good day Nicholas,I used engage 3.0.1

nicholas
Akeeba Staff
Manager

The screenshot you sent me shows me that the code that is running is Akeeba Engage 2.x. The path of the file that throws the error and the path of the file it tries to load are only present in Akeeba Engage 2.x.

As I've been saying for the last 17 years, Joomla has a weird issue where it sometimes does NOT replace files on update. It's rare enough that nobody has been able to reproduce it reliably to fix it yet. There is a simple workaround. Install the new package twice in a row, without uninstalling it before or in between, to make Joomla remove the old version's files and install the new ones.

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!

gstyles

I have tried reinstalling engage 3.0.1 twice now and the result is the same. Attached is a text file of the complete error dump from engage if that helps.

gstyles

nicholas
Akeeba Staff
Manager

Your site complains that the file administrator/components/com_engage/tmpl/common/phpversion_warning.php does not exist. However, I can see that the file is shipped with the component and is installed just fine on every site I have tried.

I think something is going wrong with your local site. Try deleting the administrator/components/com_engage, components/com_engage and media/com_engage folders. The install Akeeba Engage 3 twice in a row.

I am aware of a couple of issues (e.g. the Category options don't save) but other than that 3.0.1 installs just fine.

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!

gstyles

Good afternoon Nicholas, I have completely deleted the local site,DB and the virtual server and started again with a jpa from the live site and installed from that on the new virtual server. That works fine. I now installed engage 3.0.1 twice and I have exactly the same issues. I have tried various php versions,normally 8.0.13 then7.4.26 and 8.1(don't work on J4.0.5).

Just to test if it is my local server which is causing problems I tried it on the live site, exactly the same result. I have restored from backup and all is well except I am running engage 2 . I cant give you access to my local server (TeamViewer perhaps?) but I can to the live site if this will help you.Thanks GS.

gstyles

This attachment is from a vanilla install of J4.0.5 on php8.0.13. The only thing I have tried to  install is Engage, well its not installed as you can see.Thanks GS

gstyles

nicholas
Akeeba Staff
Manager

Please try using this dev release that another 5 people had no problem with: https://www.akeeba.com/download/developer-releases/engage-development/3-0-2-dev202201061337-reva4f112d.html

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!

gstyles

Good morning Nicholas, I have tried to install this on local and a live server with much the same problems;

JInstaller: :Install: Error SQL Specified key was too long; max key length is 1000 bytes Extension installation aborted. Package Install: There was an error installing an extension: com_engage.zip danger Error installing package

gstyles

Maybe useful , Live servers are maria db and local server is MySql. On live servers it will not install,on local server it installs with front end appearing to be OK backend is just a huge error page.

nicholas
Akeeba Staff
Manager

Can you please check if you have a leftover #__engage_unsubscribe table on your site? If you do, try removing that table and install the dev release again.

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!

gstyles

Hi, went through the DB and removed all traces of engage, went through the file system and removed all traces found of engage.

So on the live server with just J4 I tried to install engage and it failed see attachment, this is the server with Maria db.

On localhost with MySql it installs and the frontend seems OK but the back end is just a huge error dump.nb local server install was upgrade not clean install.

nicholas
Akeeba Staff
Manager

I have tried the upgrade on a server using MariaDB 10.3.32, namely my own blog. I cannot reproduce this issue — and it makes perfect sense I can't.

I have a suspicion about what kind of default configuration in MariaDB may be causing this issue on a clean installation, though.

Try this dev release:  Version 3.0.2-dev20220107133 

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!

gstyles

Some success , on the live server maria db it installed and seems to work.

on the local server mysql db it wouldn't update,so deleted everything and still wouldn't install,went to DB and removed al traces of engage and it installed.

Went to back end and did basic config,ok, went to frontend and made post ,ok went back to backend and...

D:\wamp64\www\j4\administrator\components\com_engage\src\View\Mixin\LoadAnyTemplate.php(99): Akeeba\Component\Engage\Administrator\View\Comments\HtmlView->loadTemplate('warning', false, Array)
#1 D:\wamp64\www\j4\administrator\components\com_engage\tmpl\comments\default.php(41): Akeeba\Component\Engage\Administrator\View\Comments\HtmlView->loadAnyTemplate('common/phpversi...', false, Array)
#2 D:\wamp64\www\j4\administrator\components\com_engage\src\View\Mixin\LoadAnyTemplate.php(224): include('D:\\wamp64\\www\\j...')
#3 D:\wamp64\www\j4\libraries\src\MVC\View\HtmlView.php(218): Akeeba\Component\Engage\Administrator\View\Comments\HtmlView->loadTemplate(NULL)
#4 D:\wamp64\www\j4\administrator\components\com_engage\src\View\Comments\HtmlView.php(140): Joomla\CMS\MVC\View\HtmlView->display(NULL)
#5 D:\wamp64\www\j4\libraries\src\MVC\Controller\BaseController.php(692): Akeeba\Component\Engage\Administrator\View\Comments\HtmlView->display()
#6 D:\wamp64\www\j4\administrator\components\com_engage\src\Controller\Mixin\ControllerEvents.php(74): Joomla\CMS\MVC\Controller\BaseController->display()
#7 D:\wamp64\www\j4\libraries\src\Dispatcher\ComponentDispatcher.php(146): Akeeba\Component\Engage\Administrator\Controller\CommentsController->execute('main')
#8 D:\wamp64\www\j4\administrator\components\com_engage\src\Dispatcher\Dispatcher.php(75): Joomla\CMS\Dispatcher\ComponentDispatcher->dispatch()
#9 D:\wamp64\www\j4\libraries\src\Component\ComponentHelper.php(389): Akeeba\Component\Engage\Administrator\Dispatcher\Dispatcher->dispatch()
#10 D:\wamp64\www\j4\libraries\src\Application\AdministratorApplication.php(143): Joomla\CMS\Component\ComponentHelper::renderComponent('com_engage')
#11 D:\wamp64\www\j4\libraries\src\Application\AdministratorApplication.php(186): Joomla\CMS\Application\AdministratorApplication->dispatch()
#12 D:\wamp64\www\j4\libraries\src\Application\CMSApplication.php(278): Joomla\CMS\Application\AdministratorApplication->doExecute()
#13 D:\wamp64\www\j4\administrator\includes\app.php(63): Joomla\CMS\Application\CMSApplication->execute()
#14 D:\wamp64\www\j4\administrator\index.php(32): require_once('D:\\wamp64\\www\\j...')
#15 {main}

 

I am not confident with live site to test there as yet. Thanks for your efforts Nicholas.

addendum: the live server test site is using Cassiopeia and it worked, Live site and local test site are using a Rockettheme template and they don't work,coincidence? 

gstyles

Just tried local server site with Cassiopeia and no difference.

Just seen this;

500 Layout phpversion_warning not found.

File <root>\administrator\components\com_engage\src\View\Mixin\LoadAnyTemplate.php Line 234

The content below this point is for developers and power users.

Joomla 4.0.5 – PHP 8.0.13 on WINNT

nicholas
Akeeba Staff
Manager

Regarding your PS: Complete coincidence since we're talking about the backend throwing an error, not the frontend.

Something is broken on your local server. It keeps insisting that the file administrator/components/com_engage/tmpl/common/phpversion_warning.php is not there. The file is there, we do ship it with our extension.

I have tried to reproduce this on Windows, Linux and macOS (with my own MySQL / Apache / PHP setup in all cases) as well as a live site — my blog. I can tell you with absolute certainty that this issue cannot be reproduced because, well, the file is there and is loaded just fine.

My suspicion is that you have some kind of antivirus which may be removing or renaming this file automatically. That's nothing to do with out code, I can't fix your computer for you so I am closing this ticket as fully resolved on our end.

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!

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!