johndavidhunt

I just tried swapping out all of the wp core files for new ones I just downloaded,( in case there was something amiss in there), and I also set file permissions to be a little more liberal in case it was that (which I highly doubted), but the WordPress.com and Google+ logins are still not working.

Haha, well I wanted to give it a rating since the plugin asked for one, but I didn’t feel that I had enough experience/time with it to give it a proper one.

“Awesome, you’ve been using WP Staging for more than 1 week. May we ask you to give it a 5-star rating on WordPress?” 1 weeks time experience isn’t enough to merit a full 5 stars in my opinion, you need to figure out what else is good/bad about a plugin before rating it, but since you asked for a rating after 1 week, I settled on the 4/5 stars, still pretty good. I do like this plugin a lot so far.

Since you are asking, here is a couple of things. I would love the ability to very easily and properly push changes back to production install from staging area, as well as being able to differentiate from the two different installs easier, (the ‘STAGING’ word is to subtle for me and I as still getting confused, a color change of dashboard could be good), there were other things as well, but they were quite minor.

All in all, I’m very grateful for the plugin, and I appreciate the work you have done so far.
Thanks.

So I disabled all caching, and deactivated all plugins except Postmatic and Social Commenting and it seems to have made no difference at all. I don’t believe it is a conflict with another plugin, and I don’t believe it is a caching problem.

I’ll keep trying…

Yes, as far as caching goes, there is w3 total cache and we are also using cloudflare. I had tried emptying the cache when I reset things ( deleted WordPress.com connection and made a new one), but it didn’t seem to do any good. But we were using those before as well, although cloudflare may not have been picking everything up then. Let me try messing with the cache setting some and get back to you.

OK, thanks, trying it now…….

It seems to be working , (yay, great!)

My site seems slower now, I hope/think it’s unrelated. I’ll let you know if anything else pops up (new errors etc).

Thank You!!!

Thank you, by the way, any guesses on how I could fix it in the short term, or even if the plugin update may be coming in the next couple days or not? I’m just trying to find a fix in the short term. Either way, I really appreciate your work and efforts. Thank You.

Yep, I had
define (‘wp_memory_limit’, ’64M’);
in wp-config.php, and just updated it to
define(‘WP_MEMORY_LIMIT’, ’99M’);
and still same error:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 83 bytes) in /nfs/c192/h0246/mnt/19456/domains/**********.com/html/wp-includes/wp-db.php on line 2350

The line of code it references is querying the database I believe, and it seems to be returning something to large for the server to handle I guess? There are a lot of comments already in the system of the site I’m trying to install this on, could it be that when the Rating System plugin goes to be activated it calls on all of the comments in the database in such a way that it crashes and gives the fatal error? I’m beyond my expertise in trying to sort this out at the moment, but any help given could be greatly appreciated, thanks.

This is what was in the error log.

[21-Dec-2015 16:25:00 UTC] PHP Fatal error: Out of memory (allocated 262930432) (tried to allocate 72 bytes) in /nfs/c117/h0217/mnt/198351/domains/*********.com/html/wp-includes/wp-db.php on line 2350

Also, I had followed up with my hosting provider and they had me up the allowed memory in the php.ini but I still got the same error…..

Any suggestions?

Thank you for your response, so far I am having trouble getting this to work. Either there is no output, or their is something not working in getting the output to the file. I have followed the instructions above, and I still get no results. I am troubleshooting this to see if I can get some output of some kind, but so far nothing shows in the debug.log.

If you have any other suggestions, great, otherwise I’ll report back after I get something more than just ‘fatal error’.