[Plugin: eShop] Fatal error in upgrade

hmm you could try commenting out the chmod lines of eshop_install.php

haven’t had an issue of this type before.

Hi elfin,

Thanks for the suggestion.

I tried commenting out the chmod lines (1155, 1166, 1168, 1180 and 1198) then got this error:

Plugin could not be activated because it triggered a fatal error.

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 35 bytes) in /home/puckline/public_html/wp-includes/wp-db.php on line 958

ahh in that case:
https://codex.www.ads-software.com/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Worked!

Thanks elfin!

All I’m getting (at upgrade to v 5.2.0) is –

Plugin could not be activated because it triggered a fatal error.

No other error info supplied, yet the plugin is then active, and it’s settings can then be changed, saved etc.

However, every page in admin carries the header warning –

eShop 5.2.0 is now ready to use. You must now deactivate and re-activate the plugin.

Every time I deactivate and reactivate, I get the fatal error warning, and an active plugin. When the plugin is active, I have the warning to deactivate and reactivate.

Seems to me there is either vital setup information missing somewhere (that the author is assuming everyone knows about, but very few do) or the setup and install is broken.

I tried to discuss this in Rich’s blog with him but he trotted out the old non-explanatory mantra that my WP install must have deeper issues etc etc blah blah blah – extremely NOT helpful in debugging his plugin.

_____________
NOT RESOLVED
————-

I’ve also tried the memory fix posted above

I’ve tried the “buried” fix mentioned in the activation section of the in-plugin help file – the one about deactivate, upload an image using WP media manager, then reactivate – did not solve the problem.

I have tried everything that has been posted anywhere, and cannot get eshop to behave itself since v2.x came out.

In trying to fix this, I’ve now also had TWO hosting account suspensions for server resource abuse directly attributable to this plugin … and what does the author do? He marks this topic solved after seeing my previous post.

Word of advice to everyone – if you want to stay sane and save yourself a LOT of trouble – ignore this plugin and install something like osCommerce instead – it’s a lot simpler to maintain.

I cannot mark any topic here solved. Yet you have posted in a resolved thread.

Considering that many many people can install the plugin with no problems, this does lead me to believe it is an issue at your end.

Now onto your issues:

Plugin could not be activated because it triggered a fatal error.

More details please, if no extra details appear on screen, is there anything in the error log?

The deactivate/reactivate still appearing has been an ongoing issue for quite some time, though I believe I am finally closing in on the issue.

If you have been having problems since version 2, then why on earth are you still using the plugin? At the end of the day no one is forcing you to use it.

You say that you have had

TWO hosting account suspensions for server resource abuse directly attributable to this plugin

please provide proof, and details that were supplied as I have never ever heard of this before. Plus if this really is happening for you then I would suggest you don’t use eShop and look at alternatives.

As explained elsewhere the fact you didn’t do a database backup has hampered any chance of helping you revert back to an earlier version. Your refusal to look for entries in the database gave me very little hope that the issue would ever be solved.