505 Error in Whole Website

Same Problem Exists when I purchase and Install Glossary By Codeat premium version.

I am Using Glossary by Codeat since I created my website https://www.wordtodictionary.com
I have also published more than 700 Posts in Glossary.
But Yesterday Suddenly my website shows “500 ERROR This site can’t be reached. When I get Support to my hosting provider they tell me that “This Error is due to the Glossary by codeat Installed Plugin. And, When I deactivated glossary from cpanel, My website starts working. But, I have lost all my glossary posts. And, When I again activate glossary plugin then my whole website again shows 500 Error.
I have purchased and install premium version.
Help me to recover this.

Hi,
are you facing that error 505? Because this error is about something wrong on the web server settings.
With the plugin active you can access the wordpress backend?
Also what version of PHP and WP are you using?

The Issue I am facing due to Glossary plugin is “This page isn’t working https://www.wordtodictionary.com is currently unable to handle this request.
HTTP ERROR 500”
No, When I activate plugin I cannot access the WordPress backend.
PHP Version 5.6.36
WordPress Version 4.9.8

I also report the same problem!

This happened to me as well and have been trying to figure out what is going on! In my case it took down the whole website and could not even access the backend. This is due to WordPress itself being an Addon to my XCart website. My hosting company said it was related to the use of Ioncube, but not sure I believe that reason …

It has happened 3 times and the hosting provider had to reset the server.

• This reply was modified 6 years ago by ouzillou.

The plugin is heavy of resources so is important to know the hardware.
Anyway in the case of wordtodictionary because you have 700 terms this means a query for every page of that size and php 5.x can have problems on manage this quantity of terms and move to a 500 that basically means that finished the memory and is blocking the access.

Our suggestion is to update your php version to 7.x and evaluate a cache system in the website.
For toniup and ouzillou because I don’t know the hardware I suggest anyway to check the php version.

The PHP version is 5.6.30. However, I had it at 7.2 originally as requested by my website dev team, but after these issues the host said I should downgrade to 5.6.

query_cache_size=1024000
query_cache_type=1
query_cache_limit=512000

I am running on a VPS with plenty of horsepower.

Do you use IonCube?

IonCube is not correlated often but this depends on the hosting, it is a tool in PHP as I know.
I don’t understand why downgrade from 7.2 to 5.6 but you did that for this glossary problem or for others problems?
In case is for other problems can you try to update the version again? WordPress too in the future will deprecate that php version and maybe you ioncube need an update.

I am releasing a new version with few various performance optimization in case the plugin is executed multiple times in the same page and reverting back few things for ACF/Genesis.
Wait an hour before check again in the dashboard for an update.

• This reply was modified 6 years ago by Daniele Scasciafratte.

I am doing another release with other performance improvements right now.

@mte90 Daniele Scasciafratte, I’m italian too ??
I have updated the plugin but it still does not work. My Php version is 5.4.16, do you think it is necessary to update?

• This reply was modified 6 years ago by toniup.

Ciao toniup,
I am releasing a new update right now 1.7.3 with other improvements but for PHP yes, is better to move to 5.6 or at least 7.0.
Consider that also wordpress soon will deprecate that version and many other plugins. We still support them but probably for 2.0 we will switch to php 7.0 because the performance are highly better.

Closing for inactivity