Many thanks to everyone! Deleted Give plugin directory and installed 2.7.2. Seems to be working now. Hopefully, Give will fix this bug in 2.7.4.
@drywallbmb The above fatal PHP error occurs when trying to delete GiveWP 2.7.3 and is different from the error mentioned at the top of this thread. I was able to replicate the error you’re experiencing and I have notified the development team on this. You can follow the progress in the public GitHub repo here: https://github.com/impress-org/givewp/issues/4981.
Just got the same issue on Give 2.7.4
Hi @drywallbmb @munikho @samdahl7 @aglamb,
We’ve had multiple developers on this for the last couple of days trying to replicate the errors that you all are seeing, with no luck so far. We need to be able to replicate the issue somewhere in order to track down what’s going on.
The error on the initial post here indicates that a class is missing. The class in question is housed in its own PHP file. A missing file is usually caused by one of two things:
1. The ZIP downloaded from WordPress.org doesn’t have that file containing the class at all, or is corrupted somehow.
2. Something at the file permissions level is preventing that file from being saved.
If the ZIP were corrupted or incomplete, EVERYONE would be telling us about it (and we’d easily be able to replicate the problem with a ZIP). Also, if it were just one instance, then re-downloading the ZIP would fix it.
That makes us lean toward file permissions being the culprit here.
Please reply here with your server environments if you have not already.
We’ll definitely get to the bottom of this.
Hey all!
We’ve released the new version of GiveWP (2.7.5), which fixes a few issues we discovered and that were reported by our users (you all included too).
If you have problems with your database, please deactivate and reactivate the GiveWP plugin, and it should fix it too.
Please let us know if you have further questions on this or need any additional assistance!
Hi all!
We’ve released GiveWP 2.7.5, which fixes some issues described here. I encourage you to update your plugins to see if it fixes your issues.
I’d also recommend taking a backup of the site that you can confidently restore from. Here’s an article we wrote that explains more clearly how to do that: https://givewp.com/backup-for-faster-troubleshooting/
If that doesn’t resolve things, we’re more than happy to help you! Feel free to open a new ticket for your issues and we’ll happily jump on it. Your success with online donations is our number one priority.
Have a great day!
TO all who have this issue and used composer on their site to install something else,change the last line of the give.php file which includes vendor autoload file to:
require dirname(__FILE__) . '/vendor/autoload.php';
-
This reply was modified 3 months, 2 weeks ago by
karix.
-
This reply was modified 3 months, 2 weeks ago by karix.
@karix, that finally fixed it. Thanks so much!
Is there any way to fixing this without changing the give.php file? Or @benmeredithgmailcom and @matheusfd, could this be integrated in the plugin so it doesn’t require manually changing the file each time there is an update?
Thanks!
@karix Hi! I’m the Lead Developer of GiveWP. Thanks for the snippet! I could see providing an absolute path being more solid across different systems. I’ll go ahead and make an Issue for this on the repository to get this included in the next release.
Have a great day!
Wonderful, thank you so much @jason_the_adams!
Me again! Just wanted to pop in and point out that I just put together a Pull Request for this. It should be approved tomorrow and then that will guarantee it’s in the next upcoming version.
Thanks for all the feedback and for using GiveWP!
Hello,
I’ve just install GiveWP 2.9.5 and the problem came back @jason_the_adams
I’ve fixed with @karix tips (thx)
Hi @sebastienserre That fix will be released in GiveWP 2.9.6. Thanks!
Just wanted to loop back and let everyone know that GiveWP 2.9.6 has been released with this fix included. 🎉
