Are you aware of a conflict with PopUp Maker?

Probably pop-up plugin checks via php so it cannot be compatible with any cache plugin.

Hi Emre,

This is the Popup Maker’s author reply to that statement:

“You said WSOD. That means fatal php error. That happens when there is a real conflict as in two functions with the same name etc.
They said we run php(going to assume they mean to check conditions etc and they are correct in a sense, see below) but that would simply make cache either never generate or generate improperly for your expectation.
Let me explain further.
Caching runs all php and saves the output for future requests. This means that if a Popup needs to check if a per user condition is met such as “is using google chrome” well the cache runs on the first person and then served to the rest. If first person visits and has chrome then everyone after will see the Popup no matter what browser as they get the cached version.
This doesn’t apply to any of the built in conditions that work on content. This is because of its on page X that won’t change the next time page X is loaded so it caches perfectly.
Our advanced targeting on the other hand had to be completely rebuilt for those reasons and will now use JavaScript to check things after the page loads.
So now that we cleared that up Popup Maker works with W3 Total Cache, Batcache, and most others no problem.
Plus the issue isn’t invalid cache ?? it’s a php error on the server. Can you check your error logs after getting the WSOD? Or enable WP_DEBUG and let the browser spit out the error instead of a white screen.”

I have tried WP_DEBUG true which does not display anything with the WSOD and also looked at the error-log which the last entry was this:
[27-Jan-2016 09:33:27 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home/example-site/wp-includes/wp-db.php on line 2350 which I don’t think is the issue.

Any help would be much appreciated.

The problem is not about fatal error. The exact reason is the below;

Caching runs all php and saves the output for future requests. This means that if a Popup needs to check if a per user condition is met such as “is using google chrome” well the cache runs on the first person and then served to the rest. If first person visits and has chrome then everyone after will see the Popup no matter what browser as they get the cached version.

OK but they say their plugin works fine with other caching plugins “W3 Total Cache, Batcache” so wouldn’t that reason mean that they shouldn’t work?

I did not read everything ??

Our advanced targeting on the other hand had to be completely rebuilt for those reasons and will now use JavaScript to check things after the page loads.
So now that we cleared that up Popup Maker works with W3 Total Cache, Batcache, and most others no problem.

Popup maker checks via javascript so it must work with WPFC as well. I will test and let you know.

It works in my site. Please send me an email: [email protected]

Hi Emre,

I have sent you an email with all the details that you will require, please let me know if you need anything else.

Fixed.

Glad you guys got it worked out. Thanks for testing Popup maker directly.

you are welcome @danieliser ?? If you vote, you make me so happy.

https://www.ads-software.com/support/view/plugin-reviews/wp-fastest-cache?rate=5#postform

Yes, all fixed and sorted. Thanks guys for your work and getting it working on my site.

@emre, does the new version 0.8.5.6 contain the amended code – i.e. if I update will the WPFC plugin still work on my site?

Many thanks,
Olly

Exaclty @g-olly ??

Thanks Emre! All good and working great ??

You are welcome ??