Support

Support is part of Event Gallery Extended.

Please get a subscription if you need support. Feel free to use the ticket system or the contact form for reporting defects or pre-sale questions. Make sure you're logged in in order to be able to create a new ticket.

For general information you can also jump to the manual.

Subscribe now!

#4182 Update Error

Posted in ‘Event Gallery - General’
This is a public ticket

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

Latest post by sbluege on Wednesday, 15 December 2021 16:27 UTC

CalaMur

Hello Support Team,

On two websites I have a problem updating the event gallery since a while. Three other pages run smoothly.

When I try to upgrade I get the following error message:

Warnung Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs Paket Update: Bei der Installation der Erweiterung trat ein Fehler auf: com_eventgallery_4_0_0.zip   With the last two versions I always could load the last stable version for my environment and it was working again. Now I get the error message "Internal Server Error" whenever I try to re-install an older package.   I read the following article here and followed the instructions: https://www.svenbluege.de/joomla-event-gallery/event-gallery-manual/faq-sql-error-during-install   I changed the version in the db, but the pages are not showing up.   This was the last thing I could copy from the System Check section when it was working (now I cannot access the area anymore):  Installed Event Gallery Package Version 3.12.8 (build 30c4f5cc) Database Version Target Version 3.12.6_2021-03-13   On the other websites were I don't have any problem the System Check looks like this (same PHP version, same Joomla version): Installed Event Gallery Package Version 4.0.0 (build d877de7) Database Version Target Version 3.12.12_2021-10-06   Do you have any idea what I can do to bring the two websites back online?   Thank you very much for your support! Sorry in case the ticket exists already somewhere in the forum. I didn't found it.   Alexander

CalaMur

Here the PHP settings for your reference:

Einstellungen zur Leistung und Sicherheit memory_limit  96M max_execution_time  30 (Standard) max_input_time  60 (Standard) post_max_size  20M upload_max_filesize  20M opcache.enable  on (Standard) disable_functions  opcache_get_status (Standard) Allgemeine Einstellungen include_path  .:/opt/plesk/php/7.4/share/pear (Standard) session.save_path  /var/lib/php/session (Standard) mail.force_extra_parameters    open_basedir  {WEBSPACEROOT}{/}{:}{TMP}{/} error_reporting  E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED (Standard) display_errors  off (Standard) log_errors  on (Standard) allow_url_fopen  on (Standard) file_uploads  on (Standard) short_open_tag  off (Standard) PHP-FPM-Einstellungen pm.max_children  10 (Standard) pm.max_requests    pm  ondemand (Standard) pm.start_servers  1 (Standard) pm.min_spare_servers  1 (Standard) pm.max_spare_servers  1 (Standard)

sbluege

Hi, 

thanks for bringing this up! So far, I never saw this issue.

  • Which database version do you use? 
  • Did all sites have 3.12.8 as base version? From what I see, there is no SQL change includes which would cause a change in the database row length.
  • Internal Server Error => usually this creates entries in error log files. Do you see a meaningful error message there?

Maybe this article helps: https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with-innodb/

We need to find the table in question. Converting the tables #__eventgallery_file and #__eventgallery_folder to row format = dynamic might help already. 

 

CalaMur

 Hi Sven,

You are right: The database version of the Webpages were it works are differnent from the ones were it doesn't work:

Working:

Datenbanktyp mysql Datenbankversion 5.5.5-10.4.21-MariaDB Datenbankzeichensatz utf8_general_ci Datenbankverbindungszeichensatz utf8mb4_general_ci

Not working:

Datenbanktyp mysql Datenbankversion 5.5.5-10.4.22-MariaDB Datenbankzeichensatz utf8mb4_general_ci Datenbankverbindungszeichensatz utf8mb4_general_ci

 

Here the error message from the log File. I replaced the URL with xxx since this is a public posting.

[Wed Dec 15 00:49:20.477290 2021] [proxy_fcgi:error] [pid 372:tid 139636030437120] [client 178.115.243.125:56292] AH01071: Got error 'PHP message: PHP Warning:  include_once(/var/www/vhosts/xxx.de/components/com_eventgallery/vendor/autoload.php): failed to open stream: No such file or directory in /var/www/vhosts/xxx.de/plugins/system/picasaupdater/picasaupdater.php on line 28PHP message: PHP Warning:  include_once(): Failed opening '/var/www/vhosts/xxx.de/components/com_eventgallery/vendor/autoload.php' for inclusion (include_path='.:/opt/plesk/php/7.4/share/pear') in /var/www/vhosts/xxx.de/plugins/system/picasaupdater/picasaupdater.php on line 28', referer: http://xxx/administrator/index.php [Wed Dec 15 00:49:23.618672 2021] [proxy_fcgi:error] [pid 8277:tid 139635946510080] [client 178.115.243.125:56456] AH01071: Got error 'PHP message: PHP Warning:  include_once(/var/www/vhosts/xxx.de/components/com_eventgallery/vendor/autoload.php): failed to open stream: No such file or directory in /var/www/vhosts/xxx.de/plugins/system/picasaupdater/picasaupdater.php on line 28PHP message: PHP Warning:  include_once(): Failed opening '/var/www/vhosts/xxx.de/components/com_eventgallery/vendor/autoload.php' for inclusion (include_path='.:/opt/plesk/php/7.4/share/pear') in /var/www/vhosts/xxx.de/plugins/system/picasaupdater/picasaupdater.php on line 28', referer: http://xxx/administrator/index.php?option=com_config [Wed Dec 15 00:49:24.498883 2021] [proxy_fcgi:error] [pid 8277:tid 139636299003648] [client 178.115.243.125:56482] AH01071: Got error 'PHP message: PHP Warning:  include_once(/var/www/vhosts/xxx.de/components/com_eventgallery/vendor/autoload.php): failed to open stream: No such file or directory in /var/www/vhosts/xxx.de/plugins/system/picasaupdater/picasaupdater.php on line 28PHP message: PHP Warning:  include_once(): Failed opening '/var/www/vhosts/xxx.de/components/com_eventgallery/vendor/autoload.php' for inclusion (include_path='.:/opt/plesk/php/7.4/share/pear') in /var/www/vhosts/xxx.de/plugins/system/picasaupdater/picasaupdater.php on line 28PHP message: PHP Warning:  include_once(/var/www/vhosts/xxx.de/components/com_eventgallery/vendor/autoload.php): failed to open stream: No such file or directory in /var/www/vhosts/xxx.de/plugins/content/eventgallery_multilangcontent/eventgallery_multilangcontent.php on line 45PHP message: PHP Warning:  include_once(): Failed opening '/var/www/vhosts/xxx.de/components/com_eventgallery/vendor/autoload.php' for inclusion (include_path='.:/opt/plesk/php/7.4/share/pear') in /var/www/vhosts/xxx.de/plugins/content/eventgallery_multilangcontent/eventgallery_multilangcontent.php on line 45', referer: http://xxx/administrator/index.php?option=com_config

I also changed the php version to 8.0.13, but I get the same error messages.

Please let me know if you need more details.

Thanks again for the swift reply.

Alexander

 

CalaMur

The hick-up started with 3.12.8 Here the screenshot.

Attachments

Screenshot_2021-12-15_093044.png

sbluege

Alright. So, the errors are there because there are no files. This is bad, but normal since the installation process deletes all files first.

There are some Event Gallery plugins which you need to disable: 

 

  • Event Gallery - Content
  • Event Gallery - Multi Language Content
  • Event Gallery - Google Photos and Flickr Updater

That should bring your sites up again. Now we need to fix the database. Did you have a chance to look at the article I linked? Setting the row format for eventgallery-tables to dynamic might do the trick. Maybe you can check if there are differences between the working/not working sites, too: https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with-innodb/#converting-the-table-to-the-dynamic-row-format

CalaMur

Hello Sven,

Unfortunately I'm not a developer / programer and have only limited SQL skills.

I'm able to execute a sql statement in the PHPmyAdmin tool but I don't know if this is the right code:

ALTER TABLE tab ROW_FORMAT=DYNAMIC;

Isn't the table name missing?

And I also don't see the Content Plugin. I attached a screenshot for your reference. Therefore the Component is still not running.

I will try again with the sql statement in the db.

Alexander

 

 

Attachments

Screenshot_2021-12-15_101756.png

sbluege

Ah, sure. You're on the free, support-less version. No content plugin for you. 

Check for your database table prefix and replace '#_' with it. Also, remove the space in the 'A LTER' Then execute this: 

 

A LTER TABLE #__eventgallery_folder ROW_FORMAT=DYNAMIC;
A LTER TABLE #__eventgallery_file ROW_FORMAT=DYNAMIC;
A LTER TABLE #__eventgallery_imagetype ROW_FORMAT=DYNAMIC;

 

sbluege

Maybe I missed adding a ;) in the answer above. 

Anyhow.. disabling the plugin might help the site to work. Of course, this will not help with the component. That is what we need to work on.

CalaMur

Incredible Support Sven!

By altering the three tables I was able to upgrade to the latest version; both Backend and Frontend are working again!

 

Thank you so much! You made my day!

 

Alexander

sbluege

You're welcome.

It would be great to know which table caused the issue. 

For new installations, the row format is already set correctly. I guess this issue might happen to older systems where, in addition, the row format was set to something else.