Solved Unable to install Library 4.2 when updating from 4.0

[Stevebenson223]

J! 5.0.03
Fabrik 4.0
PHP 8.2.22
I've been trying to update to Fabrik 4.2 and J!5.1.4 and I encountered exactly the same problem as @fstorch in this thread:
https://fabrikar.com/forums/index.php?threads/updating-from-4-0-to-4-2.54634/

I have two Fabrik Base Packages (see attachments) so I deleted the one named "pkg_fabrik" leaving the one with the ID matching the package ID of the other Fabrik plugins. Then I installed Fabrik Base 4.2 and everything is good: 4.2 is showing in Extensions as the only Package, it has the same package ID that matches the other plugins and, after Update Sites, I'm able to enter my download ID. And the front end works fine.

However, when I try to install Libraries 4.2 I get the "Whoops..." 500 error. Looking in phpMyAdmin, I have several Fabrik Libraries, one of which has no package ID (see attachments). I tried deleting this in phpMyAdmin but still got the 500 error. I've tried this six times in slightly different ways (using staging sites every time, of course) but I still get the 500 error.

I've successfully installed 4.2 Base and 4.2 Libraries on another site with no issues (same hosting account) so seems specific to this site. Major packages I have on this site which are not on the other site are Admin Tools and Kunena Forum. Not sure whether they might be affecting it?

Any ideas?

 

[achartier]

Cab you enable J! debug and get the call stack for what and where the problem is?

 

[Stevebenson223]

Out of Memory error!
Call Stack shows:
"Symfony\Component\ErrorHandler\Error\OutOfMemoryError:
Error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 68729486 bytes)
at /home/ynpengmc/public_html/staging7/libraries/vendor/joomla/archive/src/Zip.php:432"

Memory limit was set at 128M and I got a similar call stack message, so I increased it to 256M (initially tried 192M but that caused problems with the back end) and tried to install Libraries 4.2 again but got the above error message. Do I need to change one of the other PHP settings? Wonder why it's a problem on this site when the other site has memory limit at 128M?

 

[Stevebenson223]

Another problem, possibly related: I'm trying to upload an mp4 video to the site which is 39.4MB. Despite the fact that my php settings are memory_limit 256M, post_max_size 128M, upload_max_filesize 128M and I've set the Media maximum size to 50MB in Joomla, it fails to upload with the message that it's too large.

 

[achartier]

Can you try unpacking the libraries package into a folder inside your tmp directory, then install from folder and see if it make a difference?

 

[Stevebenson223]

That worked! Which is a little confusing as I tried that earlier and still got the 500 error. The only difference was that earlier I unpacked the libraries package into a new folder I called fabrik42 because there was already stuff in the tmp folder. So this time I cleared out the tmp folder and extracted it there and hey presto! I didn't think the name of the folder made a difference!

I still have the problem of trying to upload the large video file, so maybe there is a problem with this site. It probably needs tidying up. Meanwhile, I guess I can always upload the video via FTP or cPanel File Manager.

Thanks so much for your help.

 

[Stevebenson223]

Sad update:
Not solved! Although I achieved success with my staging site, I have encountered problems again trying to update my live site!

First, I created another staging site and recreated the successful steps from yesterday. However, I got a timeout error. So in cPanel -> PHP Selector -> Options, I updated max_execution_time to 60s from the default 30s. Success: Libraries 4.2 installed. Then I followed the same steps to update my live site. And got a timeout error again. Updated the max_execution_time to 90s and got the same again. Enabled J! Debug and got an error message: Unable to process the request. Went to cPanel -> MultiPHP INI Editor and changed the max_execution_time there to 60s for both the Home and site locations. Tried again and got a "Whoops.. 500 error". (This is all using the Upload from Folder option in Joomla.)

This is what I can see:
Update Sites = when I Rebuild, Fabrik Base Package is showing download key, but Libraries is not there at all.
Manage Extensions = (after Refresh Cache) Fabrik Library is 4.2, Fabrik Libs Library is 4.2, Fabrik Vendor Library is not there.
phpMyAdmin #_extensions = Fabrik Vendor Library is not there (the other two are).
cPanel File Manager = ...libraries/fabrik = all three folders are there but vendor.xml is missing from the vendor folder. Enums folder from fabrik folder is also missing. Possibly one or two others.

Any ideas on what is going wrong here?
Can I manually copy across any missing files?

(I know I can always push the staging site to live, but I'd really like to know what the problem is. Plus, I'm still concerned that 6 months down the line, I might find something that no longer works!)

 

[achartier]

The enums folder is part of the 4.2 Libraries package. Since the Libraries package is not installing, its package xml and update sites are not being populated which is likely why you don't see it in the Update Sites and why the rebuild does not find it.

Do you have a restricted .htaccess on that site? Could it be interfering? If so try renaming it and then copy htaccess.txt to .htaccess and try the install again. If it works you can copy back your original one and then do some digging into what is in there that might be causing your issue. Just a guess though.

Otherwise I have no idea. We have not had this particular issue reported before.

 

[Stevebenson223]

Alas, no. The .htaccess is the same as htaccess.txt so no joy there. I tried clearing some disk space as it was close to the limit, but no joy there either. I've sent a message to my hosting support. If I get it resolved, I'll post here just in case any other poor soul comes across it.
Thank you.

 

[Stevebenson223]

Update: My hosting support were able to install the Libraries update using the Joomla Install from Folder option with no problem. I assume it must be some sort of restriction with my router.