slobizman

Thanks. I’ve seen that but am confused on how to populate it. For example, I see there is a heading for Analytics with nothing under it. How do I know what to put under it? And I don’t see anything for Adsense–is this Google approved with out?

The only other thing I have is Mailchimp and would need to find get that wording from somewhere.

Where would I get the wording for these?

Thanks. But on the Create Privacy Policy page I don’t see a question for if we use Analytics. There is the question as to if we use Adsense, but not Analytics.

I just tried it only another mac with Safari 14 and it worked there. So there is obviously something messing it up on my macbook. Not your problem then. Thanks.

The only extension I have running in Safari is 1password. By the way, I’m running Safari 14. Is that what you tried it on? Someone told me that 14 it has new privacy features built in, but I don’t see any.

It also doesn’t work in in a Private Window.

Thanks, fast support!

If any user reading this wants to send me a link to their site, I’d love to see one in action…

Are they corrected in the plugin itself, or with your system it communicates with? I’m asking because I’m using Version 5.89 already, in case that’s where the changes were made.

Thanks.

It’s happening to me as well on three sites. No rhyme or reason to the types of links.

Obviously this plugin is not being supported, so I guess it’s time to deactivate it.

I knew this was a tough one….

I have the same problem here, but I do have Preload set to on. I get one or two of the “Preload may have stalled.” messages a day. A web search show this seems to be a common problem. Is there no answer?

• This reply was modified 8 years, 3 months ago by slobizman.

Thanks for the reply. I did end up getting it right. Here’s the code,and it’s working flawlessly (knock on wood):

function insert_ad1()  {
	return '<style>
@media (max-width: 800px) { .floating {float:none; text-align:center;} }
@media (min-width: 801px) { .floating {float:right; width: 336px; height: 280px; padding-left:0; margin-left:15px; margin-right:10px;} }
</style>
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
<!-- CI responsive -->
<ins class="adsbygoogle floating"
     style="display:block"
     data-ad-client="ca-pub-****************"
     data-ad-slot="***********"
     data-ad-format="rectangle"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>';
}
add_shortcode( 'ad1', 'insert_ad1' );

Well, it turns out my server was actually at 128 MB. I had my web host bump it up to 256 MB. Now, all of my sites are able to run the scan. I don’t know what will happen if they all try to run it at the same time, if that is what will happen when they automatically run. I was meaning to purchase the paid version of it anyway, and then I guess I can schedule the times.

Here’s is how my largest site ended, if it means anything to you:

[Oct 14 17:26:19] Wordfence used 141.03MB of memory for scan. Server peak memory usage was: 223.78MB

My web host, Liquid Web, is very conservative (careful), which I appreciate, and they didn’t sound too excited about bumping it up to 256 MB. They asked me to watch my memory usage carefully (not that I know how). But my question for you is, is there a way to make my websites only use up to 256 MB for Wordfence only and not for anything else? They’ve been running just fine at 128 MB.

Thanks for your help.

Well…I got it working with the “Scan file contents for backdoors, trojans and suspicious code” by excluding /cache (I use Super Cache) and also excluding *.gz. Is that okay to exclude .gz? I wasn’t sure since it was not in the exclusions as a default.

I have a much larger size website I’ll try this on next. However, I really would like to get the memory thing figured out, why it’s says 128MB instead of 256MB in diagnostics.

I fear it’s not going work for much longer since it said it used 89.4 MB of memory and I believe only 90 MB is available.

Note: I tried on my larger site, and even with cache and other folder exclusions I added, it will only run with “Scan file contents for backdoors, trojans and suspicious code” unchecked. That site also has the exact same memory settings and results I mentioned for the first site we’re talking about.

• This reply was modified 8 years, 4 months ago by slobizman.

Thanks for the reply.

WP_MEMORY_LIMIT = 256
WP_MAX_MEMORY_LIMIT = 256

Wordfence > Options > How much memory to use: 256

Memory test results:

–Starting test–
Current maximum memory configured in php.ini: 128M
Current memory usage: 64.50M
Setting max memory to 90M.

After seeing the 128MB instead of the 256MB I expected, I went into php.ini in the root of my wordpress folder and checked to see what it was set at. It was at 128MB:

max_execution_time = 90
max_input_time = 300
memory_limit = 128M
post_max_size = 32M
upload_max_filesize = 32M

So I changed it to 256MB and ran the Diagnostics again. It still told me the Current max memory configured in php.ini is 128M. So I don’t understand that.

NOTE:

I tried unchecking and checking the scan options until I figured out which step is causing the problem. It only gives me the memory error when I have “Scan file contents for backdoors, trojans and suspicious code” checked.

HA! That’s interesting. I hadn’t seen your comment here, but had just checke my site with the same plugin, PHP Compatibility Checker (assume you used this), and I got the same warning. I was coming over here to post the same question, and I see you’ve done it for me!

So, make that two people that would like to know.

I also ran it for 5.6 to see what that would say, and here’s that:

FILE: …./wp-content/plugins/broken-link-checker/modules/checkers/http.php
———————————————————————————————–
FOUND 1 ERROR AFFECTING 1 LINE
———————————————————————————————–
100 | ERROR | preg_replace() – /e modifier is deprecated since PHP 5.5
———————————————————————————————–

FILE: …./wp-content/plugins/broken-link-checker/includes/utility-class.php
————————————————————————————————-
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————————-
42 | WARNING | INI directive ‘safe_mode’ is deprecated from PHP 5.3 and forbidden from PHP 5.4.
————————————————————————————————-

• This reply was modified 8 years, 4 months ago by slobizman.

I’m not on Wp-Engine, on LiquidWeb. Anyway, I installed your WP Control plugin in case I needed it, and that ran PHP Compatibility Checker on one of my 3 sites. It worked with no issues. I ran it to check PHP 5.5 and the only odd thing is that it says the Cloudflare plugin is not compatible with 5.5. I have a feeling that can’t be right since Cloudflare is such an important and updated plugin. Do you think this is accurate? Here’s the details:

FILE: /home/********/public_html/wp-content/plugins/cloudflare/vendor/cloudflare/cloudflare-plugin-backend/src/SecurityUtil.php
—————————————————————————————————————————–
FOUND 1 ERROR AFFECTING 1 LINE
—————————————————————————————————————————–
13 | ERROR | The function random_bytes is not present in PHP version 5.6 or earlier
—————————————————————————————————————————–

FILE: /home/*****/public_html/wp-content/plugins/cloudflare/vendor/sebastian/global-state/src/Snapshot.php
————————————————————————————————————-
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
————————————————————————————————————-
383 | WARNING | INI directive ‘register_long_arrays’ is deprecated from PHP 5.3 and forbidden from PHP 5.4.
————————————————————————————————————-