Staff replied EasyStore

Upgrade issues with EasyStore 1.4.0

Asked by Stuart Clark 1 year ago Last activity 1 year ago

I've run into numerous issues when trying to upgrade from EasyStore 1.3.4 to 1.4.0.

At this moment, users should NOT perform the upgrade!

Issues experienced so far:
Installation error (duplicate SQL column) when upgrading to 1.4.0 from 1.3.4 - https://prnt.sc/wjIhauhftl2M

Issue when trying to open existing product - https://prnt.sc/42-u9CMbMVxb

PayPal plugin is completely changed and so will not work until re-configured - https://prnt.sc/1owqcBvE7k9k

ENTIRE WEBSITE FRONT END BROKEN - https://prnt.sc/7Wv3lXc8tNBQ

Once again, it is extremely disappointing that another version of EasyStore has been released without even basic testing!

6 replies

Ofi Khan Staff

1 year ago

Hello Stuart Clark

Please go to System -> Database Maintenance and update EasyStore table structure. Then install the latest version. Let me know if this tip works.

We have updated the PayPal plugin. Hence the plugin needs to be re-configured.

Best regards

Stuart Clark Asked this

1 year ago

OK - it now installs (but I have to go through a failed install, then update the database, then re-install for it to function) - NOT GOOD

Next issue - where is the Collections sub-menu under EasyStore (like your documentation claims there is)???
https://prnt.sc/Ew7BQBZYNhD7 (I've tried this on 2 different browsers and cleared the cache!

Ofi Khan Staff

1 year ago

Please download and install it again. I am not sure which version you have installed. However, I get it on my localhost.

https://prnt.sc/LKoqLwMWQjo7

Stuart Clark Asked this

1 year ago

I used the standard Joomla extension upgrade process. This pulls the files directly from your (JoomShaper) servers. It is how 99% of users are going to perform the upgrade, so it is the method you need to make sure works 100% first time

Having manually downloaded and re-installed, I do now see the Collections sub-menu, but this is NOT a fix!

Stuart Clark Asked this

1 year ago

I guess this isn't a concern then?

Despite other users running into the same issues?

That's hardly good customer support!

Ofi Khan Staff

1 year ago

The issue is fixed in 1.4.1