dimal

Is anyone reading this Forum?

@dastafford Hi,

Do you run ANY PAGE caching plugin?

@mahfuz87 Thanks for the reply and the offer.

I already have a few changes and i don’t want more code patches, since it will be hard for me to follow them after updates.

BUT Price field is so IMPORTANT and it should be allowed and available to be moved or added in othr areas in the builder. As other fieds do.

@avdajay Ok, then you could enable standard WordPress debug to a LOG and check in there for any errors?

Hi,

None of the two happens. It is random and thankfully it happens rarerly.

Could be because of the date/time code, since also future (scheduled) listings don’t work exactly well.

To revert, go to

https://www.ads-software.com/plugins/code-snippets/advanced/

get the 3.6.4 and use new plugin and upload it.

@avdajay Try to UNCOMPRESS your pages. Not sure how you do that, but try to disable it.

@specialk Hi there,

Some contradictory information about caching.

In your faq you say that WP Super Cache with Late Init set, works with Black Hole free version?

https://plugin-planet.com/blackhole-pro-cache-plugins/

So, does it work with WP SC or not? I’m a bit confused.

Thanks

@florismk Well, i have to guess here, since i’m not a Wordfence developer ??

If you use Wordfence optimized firewall, that prepends WF waf in your .htaccess (BEFORE WordPress loads), logically Wordfence is checking the requets BEFORE any caching (php mode) happens IN WordPress.

BUT in reality even with that, for example, Rate Limiting doesn’t work. I have no idea why. It should, since Wordfence sits infront of WordPress requests. Also i have no idea what else could be not working, since it is very hard to debug this. Very hard for a webmaster.

That is why i posted, it is a grey/unclear zone and better refrain from using PAGE caching with Wordfence. Better safe than sorry that is.

@florismk WPSC mod_rewrite mode is called Advanced mode and YES you should see it in your modified .htaccess.

Please note that mod_rewrite has the HIGHEST priority in execution of .htaccess.

(This is not an issue only for Wordfence but for all security plugins, bots fighting plugins also. And tests MUST be done AFTER all the pages are cached and not with a clear/empty cache).

@donncha Hi,

If WPSC (or any PAGE caching plugin) works in mod_rewrite mode, the pages are served BEFORE anything else.

BEFORE Wordfence php prepend waf.

It is unclear what happens related to that. As i posted in WF forum, using ANY page caching, both in php or mod_rewrite mode, overcomes several Wordfence features. Like RATE LIMITING for example.

So, better to be safe and not use page caching with Wordfence. Maybe use some object plugin like Redis, that doesn’t seem to conflict.

Anyways, this is what i have found and thanks for your time to reply.

@florismk PAGE Caching plugins and Wordfence are not a good idea. At least switch WP Super cache to LATE INIT settings.

Never mentioned any speed issues.

Thanks

Hi,

1. About the sitemap.xml. SEO Framework creates a virtual (on-thefly) sitemap.xml and i think that is why it doesn’t work. I mean there is no physical file.

2. I was able to make Preload to work (not with the sitemap but with the 1st option), after removing and re-installing FC plugin. For some reason CRON jobs are not created or work always after an installation. 3rd time i see this.

So i’m good.

Trying the Sitemap option (with /?action=wpfastestcache&type=preload), i get

No sitemap detected!

The sitemap is created by SEO Framework and yes i pressed Enter and the url is saved.