MarioKnight

@wfmattr That’s what is confusing for me. I run a number of servers where I’ve just switched over our client websites to Wordfence. For various reasons, I did not automate this and installed them manually within the dashboards, and about 5 or 6 sites occasionally have that file changed to root ownership which I have been trying on and off to figure out why that happens and what is different with those sites. With all the threads here about the similar issues, I was hoping that we might be able to figure that out, but for now I’m going to go back to the drawing board and if I find anything that might requite y’all’s attention I’ll make a new thread. Thanks for the prompt fixes and responses these past 24 hours! =)

To add more onto this issue, it seems to be more than just fixing permissions once and being done. For a few sites I anticipated having this issue occurring, I did a recursive chown to wp-content/ before and after updating Wordfence a couple of hours ago. I had a client call in some minutes ago reporting their dashboard was blank, and wp-content/wflogs/config.php had reverted to being owned by root rather than the correct user account. I put that back to the correct user, and added the lines to functions.php in their theme in hopes that will prevent a repeat.

I kind of figured, but I appreciate the quick response and confirmation of this. Thank you!

Hello Julka,

Thank you for looking into this and getting a fix out so quickly! I’ve updated the plugin on the sites that have it, and all appears to be well again. Thank you!

I am using WP-CLI 0.21.1. Interestingly, this error didn’t pop up until I updated to the newer WP-CLI in prep for the 4.4 core update.

For your 4.4 site(s), is it also just within WP-CLI? I want to be sure before updating said sites to 4.4 which I would have done already before seeing this.

I just saw the update, and those sorting arrows are now working as intended. Marking this as resolved, thanks again!

Thanks for the quick response, and even quicker turnaround for having an update later! I will also be sure to use that support link going forward, I must have missed that somewhere when getting everything changed over last night.

I was just about to post about this and saw your sticky. However I just de-activated and re-activated Sprout Invoices and this error still shows. It appears to be limited to the payments section when I try to use the date filter. Is there anything else I can try for this issue?

It looks like I had the same issue, purged my CloudFlare cache, and FB shares are back. Thank you for the help!

I do use a caching plugin, but I clear the cache every time a plugin is updated. I cleared it earlier after your post as well and I still have the same results.

I just wanted to add in that I am also seeing the same behavior on one of my sites. The twitter count appears to be just fine, it’s limited to the Facebook count.

It looks like the prompt is legit, and pulls 1.4.1 from IWP servers rather than the www.remarpro.com repo. It would be nice for them to put 1.4.1 here, but I can confirm that updating via the IWP admin panel does update the plugin to 1.4.1.

Hello all,

I tried the update again a week later, and it went through with no issues, so that might have only been an issue for that day. Thank you for the additional email contact if I need it in the future. I will mark this topic as resolved.

There shouldn’t be. I could see where CloudFlare would have that cached so I purged that individual file as well again to be safe, but nothing. On a hunch, I tried a different browser and I see the count functioning as intended. So it looks like in my case, there’s browser caching which makes some sense as I do utilize browser caching for static resources. Will be a pain to see how I can get that “fixed” for people who aren’t me, but that’s my problem and not yours. It’s good to see that the FB count is working again, thanks for your help!