Hi, i used Allura v1.0.2 to buid a site, i upgraded my EasyStore from version 1..0.8 to 1.0.10 and when inavigate to the settings area, i got errors, i downgraded to Easystore 1.0.9 and i still got same error.
please see error in the screenshot link: https://snipboard.io/mqIhbU.jpg
kindly help with a resolution please.
Your issue has been fixed. Please check your site.
Please accept the answer that helped you. It will be then easier to find the solution for the other users with the same issue. There is a button to accept answer after each comment.
Hello Rhema N. Abu
Apology for the inconvenience. Please share your administrator access here to check the issue. Use the Hidden Content box to share the credentials. Make sure that you have a full site backup with you before sharing.
Best regards
Hello Ofi Khan,
thanks for reaching out, kindly find the credentials in the private space.
Hello Ofi Khan , i tried to downgrade back to Easystore 1.0.8 and got another error:
https://snipboard.io/j7fkcq.jpg
kindly help please!
Please share your cPanel access. I will share it with the development team. They will check and fix your issue. Please do not try anything until they finish.
okay, pls check the private space
Please how soon should i expect a resolution from the developers?
client needs the site up as soon as possible please.
Hello Ofi Khan, any updates ??
You have to allow me some time.
okay , i will check back soon
hello
any progress pls ?
issue still persist, no feedback, no resolution !
i guess am left to my fate !
this is sad and not fair to say the least.
Hello?
please how much time ?
this is taking too long please?
Accepted,
just need to know what version of EasyStore is currently active on the site and why did upgrading to Easystore 1.0.10 crashed the site?
what happens to my other easystore powered sites if i upgrade to version 1.0.10, would i experience same issue?
please clarify these concerns for me .
thank you Offi Khan.
You are welcome 😊
You have set allow_url_fopen = 1 in your php.ini file to avoid this issue. If you have allow_url_fopen = 0 or off, only then you might see this issue. We will include a fix in the next release so that it does not conflict with allow_url_fopen.
okay, thanks Ofi Khan
much appreciation.
