Sunday, January 08 2017
  6 Replies
  3.1K Visits
  Subscribe
Three days ago joomla I updated to the latest version, and updated seo glossary to version 2.4.1. For three days the site worked fine. This morning, the site went down. I solved a problem disconnecting the plug-seo glossary (for the entire site) and off of the menu item (component). Rolling back to 2.4.0 is not done.

The previous version of seo glossary 2.4.0 on another site is working properly.

Report is attached. Who is aware of the reasons?

Error seo glossary component page


500 - Table './ismanku_j3/#__seoglossary' is marked as crashed and last (automatic?) repair failed SQL=SELECT a.*,uc.name AS editor FROM `#__seoglossary` AS a LEFT JOIN #__users AS uc ON uc.id=a.checked_out LEFT JOIN #__seoglossaries AS g ON g.id = a.catid WHERE g.state = 1 AND (a.state IN (1)) AND (a.catid=2) AND ( g.language LIKE 'ru-RU' OR g.language = '*' ) AND (a.publish_up = '0000-00-00 00:00:00' OR a.publish_up <= '2017-01-08 09:10:59') AND (a.publish_down = '0000-00-00 00:00:00' OR a.publish_down >= '2017-01-08 09:10:59') ORDER BY a.tterm asc Table './ismanku_j3/#__seoglossary' is marked as crashed and last (automatic?) repair failed SQL=SELECT COUNT(*) FROM `#__seoglossary` AS a LEFT JOIN #__users AS uc ON uc.id=a.checked_out LEFT JOIN #__seoglossaries AS g ON g.id = a.catid WHERE g.state = 1 AND (a.state IN (1)) AND (a.catid=2) AND ( g.language LIKE 'ru-RU' OR g.language = '*' ) AND (a.publish_up = '0000-00-00 00:00:00' OR a.publish_up <= '2017-01-08 09:10:59') AND (a.publish_down = '0000-00-00 00:00:00' OR a.publish_down >= '2017-01-08 09:10:59')


Error seo glossary content plugin


144 - Table './ismanku_j3/#__seoglossary' is marked as crashed and last (automatic?) repair failed SQL=SELECT t.* FROM #__seoglossary t LEFT JOIN #__seoglossaries g ON t.catid = g.id WHERE t.state = 1 AND g.state = 1 AND ( LOWER('\r\n') LIKE CONCAT('%', LOWER(t.tterm), '%') OR '\r\n' REGEXP REPLACE(REPLACE(tsynonyms, ', ', '|'), ',', '|') ) AND ( g.language LIKE 'ru-RU' OR g.language = '*' ) AND (t.publish_up = '0000-00-00 00:00:00' OR t.publish_up <= '2017-01-08 09:08:32') AND (t.publish_down = '0000-00-00 00:00:00' OR t.publish_down >= '2017-01-08 09:08:32') ORDER BY ordering;
A
5 years ago
@Ismankulov
Please create a ticket in ticket support with your access so i can take a look at issue.
I
5 years ago
Sorry, I can not. I am a technician working on the project. E-mail belongs to the owner. I can not get an answer from you this way, or it will be very long. I think this problem may occur for many users. Perhaps a better look at it right here?
T
Hi,

As we can't reproduce this issue on our side, you'll need to proceed with a support ticket.
Thanks a lot.

Cheers,
I
5 years ago
Well, later I will create a ticket and try to get a fast communication via email owner. My question is: how can we communicate? I need only reproduce the situation in which an error occurs to show you? Or you will need access to the site to an active component? It is clear that I can not grant full access, only limited.
T
OK, you can do both, do a staging copy of the website or give an access (confidentiel full access is needed though).

Cheers,
I
5 years ago
The problem disappeared, the components work properly after the update to version 2.4.2. I suppose the error contained in the previous version and was patched. Thank you for the quick completion component!
  • Page :
  • 1
There are no replies made for this post yet.
Be one of the first to reply to this post!