rembert

Just tried it. The answer is: no.

Yes, I do have quite some WordPress sites with InternetToday / Oxxa, without problems. This is the first one experiencing this problem. I have looked for the http-logs as I wanted to know what happens exactly. Couldn’t find them.

But my problems magically disappeared after I switched to TwentyFourteen, Twenty Ten and then back to the Virtue theme I was using.

I will raise a ticket with them today and refer to your ticket. But I don’t have a strong case as the issue got solved by fiddling with the themes I’m afraid.

Did you find a solution? I have the same issue with https://www.turnersports.nl

I’m using the Virtue theme on a just installed WordPress 2.9.3 setup and the %postname% permalink structure.

First, I reset my browser. Things work well at that point. To reproduce the issue, I just keep visiting the four menu items, until suddenly either a product detail page appears or the message “This webpage has a redirect loop” appears. For some reason, it’s always a random product detail page.

Very weird: if Chrome goes wrong, and I fire up FireFox, then FireFox just works properly for several clicks. Resetting a browser does result in the correct page to be displayed.

I checked the http traffic for the browsers. A 301 Moved Permanently response is returned. I then tried the same thing using telnet, but then a 200 OK message appears.

telnet www.turnersports.nl 80
Trying 87.236.100.120...
Connected to www.turnersports.nl.
Escape character is '^]'.
GET /over-ons/ HTTP/1.1
host:www.turnersports.nl

HTTP/1.1 200 OK
Date: Fri, 29 Aug 2014 22:25:34 GMT
Server: Apache
X-Pingback: https://www.turnersports.nl/xmlrpc.php
Link: <https://www.turnersports.nl/?p=13>; rel=shortlink
X-SATserver: S=CLN01B D=832290 uS
Vary: Accept-Encoding
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

I fail to understand the 301 message: why is it showing on one browser and not the other. Why is it never showing in terminal. If resetting the browser temporarily solves the issue, it sure sounds like cache, but why the HTTP response? And how does the webserver know about the

What I tried:

* deleted .htaccess and let WordPress generate a new one by modifying the permalinks setting
* reviewed all slugs and made sure they’re unique
* reset permalinks to standard – no problems occur
* using a different template for those product detail pages. No change
* tried Twenty Fourteen theme instead. Cleared cache. Error reoccurred. Cleared cache again. Error does not return. Then moved to Twenty Twelve theme and finally to my Virtue theme. Cannot reproduce the errors with any browser after clearing the cache.

Now I’m really lost. Why does it seem to work properly now? I cannot trust my site this way.

That’s a fast response. I do appreciate that! Thanks. Looking forward to the update.

For now I just disabled displaying the likebox by using

jQuery(“#bfblikebox”).hide();

in the cookies-not-allowed callback in the cookiecontrol plugin and

jQuery(“#bfblikebox”).show();

in the cookeis-allowed callback.

But, this doesn’t prevent loading the facebook code in the iframe nor does it prevent facebook cookies to be updated or placed.

So, I’d like to have the option to keep the likebox invisible AND not to load the facebook iframe content upon loading. Only when that .show() function is run, then the the facebook content can be loaded into the iframe and the likebox can be shown. That way the plugin will comply to even the (ridiculous) Dutch implementation of the EU cookie directive.

When you update the 1.0 version, you’ll get a new plugin with the 1.1.01 version. The 1.0 version will still exist, still requesting an update. Deleting that 1.0 version from within WP is not such a good idea as both plugins will then be removed.

As I don’t like having appearant pending updates in my plugin list, I decided to disable the 1.0 plugin and to remove it from the plugin list. This doesn’t seem to break anything. To do this, just load pluginchief-mobile-site-builder.php and modify the top three lines slightly, from:

/*
Plugin Name: Plugin Chief Mobile Site Builder

to:

exit();
/*
OLDPlugin Name: Plugin Chief Mobile Site Builder

I’m using the Mobile Redirect plugin from InsideOut Solutions. Working well.