|
David Dadekian
|
March 15, 2015 at 9:15 am
1. I use Wordfence and have all the correct pages in the cache exclusions.
2. As an added test I completely turned of caching.
Even with both these changes when people try to buy tickets from a phone (seems find on my iPad) they get the “nothing in event queue” page.
The tickets are at: http://eatdrinkri.com/festival and from there it’s linked to the three events:
http://eatdrinkri.com/eventespressoevents/eat-drink-ri-festival-dinner-by-dames-thursday-april-30-6-10-p-m/
http://eatdrinkri.com/eventespressoevents/eat-drink-ri-festival-grand-tasting-saturday-may-2-12-4-p-m/
http://eatdrinkri.com/eventespressoevents/eat-drink-ri-festival-grand-brunch-sunday-may-3-11-a-m-2-p-m/
Thank you.
|
|
Dean
|
March 16, 2015 at 5:05 am
Hi,
When you disabled caching, did you do a complete clear of the cache? Which caching system are you using? Is there any caching occurring at a server level (you may need to query that with your host)?
|
|
David Dadekian
|
March 16, 2015 at 10:18 am
I use Wordfence for security and caching. First I put in exceptions for the five EE4 pages. Then I cleared the cache before and after disabling. I just checked with my host and they say there is no caching installed on the server.
|
|
Lorenzo Orlando Caum
|
March 16, 2015 at 11:40 am
Hi, I was able to see the issue using my iPhone:
http://cl.ly/image/0g2j1h3g3D39
Can you temporarily re-test with the caching feature turned off?
Also, does Wordfence have any settings for mobile devices?
—
Lorenzo
|
|
David Dadekian
|
March 16, 2015 at 1:27 pm
That’s exactly the issue. So I have caching turned off since yesterday, and you still received that issue. I looked all over the Wordfence docs and settings for mobile and the only thing I found was creating a caching exclusion for User-Agent contains “iPhone” or “android” both of which I set.
|
|
Josh
|
March 16, 2015 at 2:11 pm
Hi David,
I’m not familiar with how WordFence sets up the caching, but you can check the .htaccess file and the wp-config.php file to see if it’s added the cache rules there. If it is, when you’re disabling the caching, it may not be updating those rules for mobile correctly. It may help to get in touch with WordFence support to find out how to ensure those pages are not being served from a cache.
|
|
David Dadekian
|
March 16, 2015 at 5:49 pm
With Wordfence disabled (I completely disabled the plugin, not only the caching part) there’s nothing in wp-config to indicate Wordfence. And this is all that’s in the .htaccess:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteRule ^dadekian/?$ /wp-login.php [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
|
|
Tony
|
March 17, 2015 at 6:22 am
Hi David,
I tried registering with my Samsung Galaxy S4 and ran into the same issue, I then tried registering with a Nexus 7 and had no problems.
This suggests something is targeting mobile devices and doing ‘something’ with those requests. We’ve seen themes try to do some strange things with mobile visitors that has broken various settings in the past, can check if your theme is doing anything strange to mobile devices?
An easy way to do this is using Theme Test Drive which allows you to use a different theme on your site, without actually changing it for all visitors.
Do you have any other plugins that may target mobile devices? This can be anything from js/css minification to tracking mobile visitors just to try and track down if anything is messing with mobile requests.
Do you use Cloudflare through your hosting?
|
|
David Dadekian
|
March 17, 2015 at 9:54 am
I’m pretty sure it was the mobile feature in the WordPress Jetpack plugin. I deactivated it and it seems fine on my iPhone. If you could check it on your side to make sure that would be great. Thanks.
|
|
Tony
|
March 17, 2015 at 10:56 am
I can now register onto the event and select a payment method using my SGS4 so looks like it was a conflict with JetPack.
I’ll create a ticket so our developers can investigate this.
|
|
David Dadekian
|
March 17, 2015 at 11:01 am
Thank you.
|
|
Tony
|
March 17, 2015 at 11:32 am
Happy to help 🙂
|
