slobizman

The following is made in regards to all plugin authors, not just Johan. When you have a plugin you that really love, really rely on, give a donation to the author. I know I gave something to Johan last year. 1) I wanted to show my appreciation, and 2) I want the plugin to continue to be supported. I do this with free plugins that are critical to me.

You can donate to Johan at: https://johansteen.se/donate/

Back to the parse error…

I, too, am waiting to to hear about this parse error before I update WP, as it would be a pretty big problem for me if it didn’t work. I’m sure Johan will reply to us here shortly.

Perhaps it only happens for some people because it’s related to the particular content of the snippet? To those having issues, are there any special characters or html in your content? Have you tried deactivating the the snippets one at a time to see if it’s one in particular? Or does it even throw off the error if there are no snippets active?

Are there any people running the plugin on 4.4.3 without any issues, and what kind of content is in the snippets?

Thanks for posting batfan. I’ll wait to hear what Johan says before I upgrade to 4.5.x.

Well, I just tried it (with the addition of *.zip and*. tar) and it didn’t work.

I might try that. What about potentially huge files like tar and zip files?

Unfortunately, I just have to give up. Wordfence scanning simply uses too much memory. I had a global limit on my server, but the web host changed things to allow me to override it per site with PHP.ini.

I took one site (my medium-sized one in terms of pages, plugins, traffic) and raised the memory limit and ran the scan. First time was 128 and it exhausted memory. Second time was 192 and it went further but then ran out of memory. Third time was 256, which got even further along and then exhausted memory. I then tried 256 on another site, and it ran out of memory too.

I told my web host thanks, but I’m going to give up on Wordfence for scanning, despite how cool it is. I was ready to buy it for three sites, but now I’ll see if there is still anything worthwhile running the free version for some of the features other than scanning.

Appreciate your help on this, though.

Can you tell me which plugin you replaced it with?

I’m kind of surprised this plugin author has not responded yet. I remember last year on a major release he was responsive and dealt with me on email too, and I was so happy about it I donated to him. Nice guy. I emailed him again and if I get word on the plugin I’ll let you know.

Have you been able to get this to work? I’d like to upgrade to the 4.5.x level but can’t afford to lose this plugin.

First of all, I appreciate you continued assistance…

So, my Diagnostics looks fine, as much as I can tell. I don’t know if I have LightSpeed, I’ve never heard that mentioned or seen in anywhere on my cpanels or WHM.

Is this following of interest? My dedicated server has 8GM memory. But when I run Wordfence’s Check Memory function in diagnostics, it shows:

Current maximum memory configured in php.ini: 96M
Current memory usage: 56.25M
Setting max memory to 90M.
Starting memory benchmark. Seeing an error after this line is not unusual. Read the error carefully
to determine how much memory your host allows. We have requested 90 megabytes.
Completing test after benchmarking up to 80.25 megabytes.

But also on that diagnostics page it shows my two WP memory limit settings set at 256MB.

I saw I had no php.ini file in my home directory, so I put one in with the 256MB limits. But then the test still so what I pasted above, “Setting max memory to 90M”.

I don’t understand enough about this end of this, does it sound somewhere my memory is simply not set high enough for the two larger sites (my smaller one works)?

Thanks again.

Well, I ran that one site on a manual scan basis, and it still go hung up on the Fetching Malware list part. So, it’s it’s not competition for resources. There’s something else wrong.

I cancelled the scan. Let it go for five hours or so.

Thank you very much for all the prompt answers. Yes, I have a pretty powerful server that only really runs three websites, with a combined traffic of about 35,000 page views a day. So it’s not overtaxed, and have never had any performance issues with it.

Since I have to subscribe to schedule — again, I’d love to subscribe but need to first see if this issue can be resolved — I thought of something to try. I unchecked the enabling of automatic scan on all sites. Then, on one of the two sites that give me fatal errors on the memory, I started a scan manually. It didn’t take long for the same error to occur. As it got to “Fetching list of known malware files from Wordfence,” it’s got stuck. Stuck here:

[May 06 16:09:23]Fetching list of known malware files from Wordfence …

Looking down at the detailed activity, here’s the error, which occurred just one second later.

[May 06 16:09:24] Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 76 bytes) in /home/******/public_html/wp-content/plugins/wordfence/lib/wordfenceHash.php on line 85

(Fetching a malware list from Wrodfrence seems like an odd place to run out of memory, no?)

This is run on a Friday evening (slow time) on one of the sites that would get about just 5,000 page views days.

“Do you have several separate installations of WordPress running next to each other on the same hosting account?”

They run on my dedicated server, each on their own cpanel.

Thank you very much for your reply. I installed the Performance Profiler and it didn’t show any issues. I used the option in WordPresss to check if I have over 80 MB available for Wordfence and I do.

On two of my three sites under Wordfence/Scan in the Scan Summary Window, the only scan it shows is May 3 (two days ago) and two of the items are still running. Both “Comparing core WordPress files against originals in repository” and “Comparing core WordPress files against originals in repository”, rather than showing Done, Success or some other status to the right, it shows the little animated bars icon that I assume means that the process is still active. I don’t know why it should still be active. Shouldn’t it have stopped (especially considering the next scan box “Detailed Activity” shows subsequent daily scans have been executed since then)?

It may be that just 15 seconds after the time of these two still “ongoing” processes, I see in the Detailed Activity box that it exhausted memory ([May 03 10:58:34] Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 1365628 bytes) in /home/*****/public_html/wp-content/plugins/wordfence/lib/wfConfig.php on line 686)

Again, this is happening on two of my three sites.

1. Could there be a problem because my sites might be scanning at the same or overlapping times with each other? Should I set them to go off at different times (by a wide margin so they complete)?

2. How do I stop the processes that are apparently still running (according to the icons). Or are those icons just “stuck” and the the processes are not really still running?

Over a week with no reply. I sure would like to pay this company every month, for three sites, but cannot until they address this issue with me. Not going to pay for a subscription just so I can ask a question to see if I want to purchase.

Upon further inspection, even after the robots.txt change, and even after turn off Cloudflare and Supercache, when I “Fetch and Render” I get a “Partial” result (just “Fetch” says complete), and it lists the following:

Googlebot couldn’t get all resources for this page

https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js

When I view the rendered pages, it shows Adsense ads on “How the user sees the page” and no Adsense ads on “How Googlebot sees the page”

Even after completely emptying out my robots.txt file, I still get the same thing.

What could possibly be blocking this js file?

CAN THIS AFFECT ADSENSE REVENUE?

On July 26 my adsense revenue dropped massively. My CPC’s and CTR’s were considerably lower than usual. (My traffic was normal.) After a few days of this, I figured I was getting a run of low-quality, irrelevant ads and hoped it would return to normal. This morning, 5 days later, the low revenue persisted. I figured I better look into it further.

I thought back to the July 28 (two days after seeing Adsense revenue drop) emails I received from Google about Googlebot not being able to access my js and css. So I did some research today and was helped by this thread and the article at Beachfront mentioned earlier in this thread.

So I went into the sites to remove the offending disallow wp-admin from the robots.txt files. But today, when I checked the robots.txt files in webmaster tools, it was still showing the older version.

So, I added the additional “allow” lines you suggested in the Beachfront article (although in my case I’m not sure I really need them, but can’t hurt!). In fact, those lines are all I have in the robots.txt files, except for a pointer to my site map:

User-Agent: Googlebot
Allow: /*.js*
Allow: /*.css*

Sitemap: https://www.mysite.com/sitemap.xml

* Two of my sites also have a disallow at the beginning of robots.txt of an an old folder unrelated to WP.

Then I deleted the Supercache cache on all my sites, and then purged the cache in Cloudflare. Then in Webmaster Tools I submitted the new robots.txt for each site, and it now shows the current file when I look at it in Webmaster Tools.

At this point my fingers are crossed, waiting to see if there is any immediate change in Adsense revenue. I should know my end of day, or tomorrow — IF Adsense immediately changes behavior when it sees the new robots.txt files.

I have no idea if this actually does affect Adsense, but I have read that if Googlebot has crawl issues it will show lower quality ads. The timing is so coincidental, I’m hoping that the robots.txt was the problem.

Hs anyone else noticed Adsense CTR and CPC drops this week?