Content does not display after payment

Hello, glad you like it! I gave it a try on your site and see the same symptom you described (paywall still showing even after payment is made).

I do see that the cookie is successfully being set, so that means the payment was processed by your browser.

What other plugins do you have enabled?

I recommend:
1. Disable your caching plugins and try again. This seems logical that it could be the problem.
2. Check the WordPress database for processed transactions. The table in the database you want to check is called wp_somenano_payments. The wp_ might be different depending on your WordPress install.

Let me know what you find and we can continue troubleshooting.

@frankxplor
I have tested with a number of the most popular caching plugins and it seems to be the issue. All of them store static snapshots of a page.

Meaning, if the snapshot is made of the page when the paywall is not yet paid, all users (regardless of payment) will see the unpaid paywall. And if the snapshot is made of the page when the paywall has already been paid … all users (including those that did not pay) will see the extra content.

The more popular caching plugins have the ability to customize pages that are cached. I recommend disabling caching for the posts/pages that have a paywall. Maybe this can be done by a common category or tag for ease?

First, I lowered the payment to $0.05 to make it cheaper in case you have to troubleshoot more.

Here are more details:
The caching plugins I use are:
-SG Optimizer (in conjunction with SiteGround Hosting)
-Autoptimize
-Async Javascript
-and I use Cloudflare CDN

First I tried turning off all the caching settings, putting cloudflare into development mode, and purging all the caches. Then I opened the page in a Chrome Incognito window and tested. Still will not show below the paywall after payment.

SG Optimizer Plugin:
– Has option to exclude URL’s from dynamic caching. I excluded the url where I am using the nano paywall

Autoptimize Plugin:
– Does not have the option to exclude URL’s.
– It does have the option to exclude scripts and css (Currently I do not exclude anything)

AsyncJavascript Plugin:
– Does not have the option to exclude URL’s
– It does have options to exclude scripts and plugins
— Note: I had to exclude brainblocks.min.js in order for the payment button to work
— I tried excluding the plugin SomeNano, but it made no difference

Regarding other plugins (non-caching):
– I understand sometimes there are plugin conflicts. I do not have the time to go into investigating this. If you can see something on your end when looking at my site with Developer tools that will point me in a specific direction, then I will try. Otherwise, I’ll need to take a break from this and just wish you luck and try again in the future when I have more time :).

Thanks! Please let me know if you have any more insight.

• This reply was modified 5 years, 10 months ago by frankxplor.

pro-tip; you can disable Autoptimize on a per-request basis by adding ?ao_noptimize=1 to the URL and for AsyncJS you can do the same with ?aj_noptimize=1, that should allow to see if either of those have an impact here. also looking at the browser console for JS errors can help identifying the problem.

For autoptimize there are troubleshooting tips and info on how to exclude in the AO FAQ.

hope this helps debugging,
frank (ao dev)

Thanks for the tip @optimizingmatters
@pwlk FYI: I tried both ?ao_noptimize=1 and ?aj_noptimize=1 and they did not change the result.

@frankxplor
I tried all those plugins in my test environment and was unable to recreate the issue. I did have to add the BrainBlocks to the Async Javascript exception list as you mentioned.

I pushed v0.1.1 of the plugin which adds a database view tab on the Settings->SomeNano page. Request you update and take a look at the table.

Are there rows of transactions listed?
Do a test payment to yourself, does that transaction show up in the table?

Appreciate your willingness to troubleshoot!

Marking as resolved. Please reply if you are still experiencing this issue.