30 pointsStarting to get into this DEV thingI'm helpful
mainstreet
Member
—
30th January 2011 (1 year ago)
Hi I just installed marketpress at bearinginstaller.com and I am getting the following error while trying to checkout
Firefox:
The page isn't redirecting properly
Chrome:
This webpage has a redirect loop.
The webpage at http://www.bearinginstaller.com/store/shopping-cart/checkout/ has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
Hi I just installed marketpress at bearinginstaller.com and I am getting the following error while trying to checkout
Firefox:
The page isn't redirecting properly
Chrome:
This webpage has a redirect loop.
The webpage at http://www.bearinginstaller.com/store/shopping-cart/checkout/ has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
I can confirm a similar error. I just tried to activate MarketPress on 3.1RC3 network install, and it brought the whole site down. I had to manually go in via ftp and delete the plugin folder just to get back into my dashboard.
Log files show
Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. referer: http://DOMAIN/wp-admin/
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
30th January 2011 (1 year ago)
#
You're not installing this into a wp/mu install that sits in a subdirectory under root, are you? That's a common error that pops up from time to time when folks try that. WPMU/MS needs to be within the webroot.
No, it's in webroot, and the install is running fine with everything else. The only time the error pops up is when this plugin (along with support system, see my other post) are activated.
The problem didn't exist with previous versions of these two same plugins, so it's likely something to do with updates made for 3.1
It's hind of hard to research this with Google's new indexing assuming that when I write wordpress, it assumes the domain wordpress.com and weighs that more than it did in the past. Wish they would bring back support for -site: *sigh*
I took at look at syslog and this is what I'm seeing when marketplace is enabled:
httpd: PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 8192 bytes) in /var/www/vhosts/DOMAIN/httpdocs/wp-content/plugins/marketpress/marketpress.php on line 648
followed by a whole ton of
httpd: PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 92 bytes) in /var/www/vhosts/DOMAIN/httpdocs/wp-includes/plugin.php on line 160
So whatever's looping, it looks like it just continues to do so until it eats up 65meg of ram then crashes.
Enable it, problem comes back, disable it problem goes away. This plugin and the Support System plugin are the only ones that have generated any kind of errors for me on the install.
When I enabled HTTPS on the Checkout directory via the 'Admin SSL' plugin for Wordpress the redirect/loop went away. Granted I don't have the experience that many of you do but could the looping be a result of the script looking for an HTTPS url and not finding one?
Do any of you guys have authorize.net enabled as a payment method? If so the redirect is probably coming from that trying to force SSL. SSL is required to use that gateway.
There are no redirects showing in the headers. I turned on debug logging with both php and apache, and all I'm seeing is one giant muck of out of memory errors the second Marketpress is activated.
I even went through the database and manually deleted all of its entries and re-activated it thinking (hoping) it was simply something that went amuck there, no such luck.
Ok I just spent an hour and a half trying to debug this, and am beyond frustrated at the moment. I'm gonna go play some Tetris to clear my head, haha. =)
OK so I just tested on IE and while I am still getting HTTPS errors I also noticed that i cannot get to the chechout screen from there if I choose 'checkout' from the shopping cart widget but I can if I click on 'checkout' on the main page.
Does anyone have experience in forcing this plugin effectively to HTTPS? It's still broken in IE and Chrome.
OK I guess I need to know which directory/pages need to be secured through HTTPS in order to successfully display in IE and Chrome. Currently I have the store/shopping-cart/ urls secured but the HTTPS remains broken. The Chrome error screenshot is attached. Any help would be appreciated.
Sorry, I meant Wordpress at all. Just use firebug or chromes dev tools to see all the assets that weren't loaded via https.
Note it's pretty common for SSL sites to have some assets not loaded https, so most users have that error message disabled. You may be able to live with it.
Well I now have HTTPS running unbroken in Chrome and Firefox but I cannot seem to locate the asset that is causing IE to popup the error. It would be helpful to know if anyone had an issue like this for Marketpress as well so that I can rule out Marketpress as a potential cause.
@edihtors, did you have pretty permalinks enabled on that blog?
That function checks your rewrite rules to make sure they've been added correctly and flushes if not. Many users who had poorly coded plugins installed had trouble with rewrites not sticking.
If it's not the permalinks thing, maybe another plugin is messing them up and causing the unending loop.
I'm using a custom structure of: /content/%category%/%postname%
Not sure if that would effect anything or not. I had this problem even with no other plugins enabled on the site, so it couldn't have been a conflict there.
I do have the latest nightly build on the site, so maybe it's an issue as a result of something done post - 3.1RC3?
Responses (26)
Member — 30th January 2011 (1 year ago) #
I can confirm a similar error. I just tried to activate MarketPress on 3.1RC3 network install, and it brought the whole site down. I had to manually go in via ftp and delete the plugin folder just to get back into my dashboard.
Log files show
Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. referer: http://DOMAIN/wp-admin/
Keeper of the Dark Chocolate — 30th January 2011 (1 year ago) #
You're not installing this into a wp/mu install that sits in a subdirectory under root, are you? That's a common error that pops up from time to time when folks try that. WPMU/MS needs to be within the webroot.
Member — 30th January 2011 (1 year ago) #
No, it's in webroot, and the install is running fine with everything else. The only time the error pops up is when this plugin (along with support system, see my other post) are activated.
The problem didn't exist with previous versions of these two same plugins, so it's likely something to do with updates made for 3.1
Sales & Support Lead — 30th January 2011 (1 year ago) #
@mainstreet I just tested a checkout on your site and the checkout page loads correctly for me in firefox
@edihtors, I'm not seeing any conflict on my test install with WP3.1, MarketPress and Support System. Do you see anything in your php error logs?
Thanks!
Keeper of the Dark Chocolate — 30th January 2011 (1 year ago) #
I'm wondering if it's a non discovered 3.1 issue. Only thing I find though is this:
http://wordpress.org/support/topic/edit-tagsphp-redirect-loop
It's hind of hard to research this with Google's new indexing assuming that when I write wordpress, it assumes the domain wordpress.com and weighs that more than it did in the past. Wish they would bring back support for -site: *sigh*
Member — 31st January 2011 (1 year ago) #
I took at look at syslog and this is what I'm seeing when marketplace is enabled:
httpd: PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 8192 bytes) in /var/www/vhosts/DOMAIN/httpdocs/wp-content/plugins/marketpress/marketpress.php on line 648followed by a whole ton of
httpd: PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 92 bytes) in /var/www/vhosts/DOMAIN/httpdocs/wp-includes/plugin.php on line 160So whatever's looping, it looks like it just continues to do so until it eats up 65meg of ram then crashes.
Enable it, problem comes back, disable it problem goes away. This plugin and the Support System plugin are the only ones that have generated any kind of errors for me on the install.
Member — 31st January 2011 (1 year ago) #
When I enabled HTTPS on the Checkout directory via the 'Admin SSL' plugin for Wordpress the redirect/loop went away. Granted I don't have the experience that many of you do but could the looping be a result of the script looking for an HTTPS url and not finding one?
Member — 31st January 2011 (1 year ago) #
Update: Now the HTTPS is broken on Chrome, fine on Firefox. Argh!
Lead Developer — 31st January 2011 (1 year ago) #
Do any of you guys have authorize.net enabled as a payment method? If so the redirect is probably coming from that trying to force SSL. SSL is required to use that gateway.
Member — 31st January 2011 (1 year ago) #
Unfortunately no, I only had PayPal Chained Payments enabled.
Member — 31st January 2011 (1 year ago) #
Yeah mine is Authorize.net
I think the broken HTTPS is a result of external links on the same page. Interesting that Firefox didn't pick that up.
Lead Developer — 31st January 2011 (1 year ago) #
Can you use firebug to watch the headers and see what the redirects are trying to go to?
Member — 1st February 2011 (1 year ago) #
There are no redirects showing in the headers. I turned on debug logging with both php and apache, and all I'm seeing is one giant muck of out of memory errors the second Marketpress is activated.
I even went through the database and manually deleted all of its entries and re-activated it thinking (hoping) it was simply something that went amuck there, no such luck.
Ok I just spent an hour and a half trying to debug this, and am beyond frustrated at the moment. I'm gonna go play some Tetris to clear my head, haha. =)
Member — 1st February 2011 (1 year ago) #
OK so I just tested on IE and while I am still getting HTTPS errors I also noticed that i cannot get to the chechout screen from there if I choose 'checkout' from the shopping cart widget but I can if I click on 'checkout' on the main page.
Does anyone have experience in forcing this plugin effectively to HTTPS? It's still broken in IE and Chrome.
Member — 1st February 2011 (1 year ago) #
OK I guess I need to know which directory/pages need to be secured through HTTPS in order to successfully display in IE and Chrome. Currently I have the store/shopping-cart/ urls secured but the HTTPS remains broken. The Chrome error screenshot is attached. Any help would be appreciated.
Lead Developer — 1st February 2011 (1 year ago) #
That's normal trying to get https working for multisite. It's a pain because so many themes and plugins have hardcoded http:// links to assets.
Lead Developer — 1st February 2011 (1 year ago) #
Are you sure you have rewrites and pretty permalinks enabled in your WP install?
If so another thing to try is commenting out this line
//add_action( 'option_rewrite_rules', array(&$this, 'check_rewrite_rules') );Member — 1st February 2011 (1 year ago) #
Aaron,
Thats what's strange, this is a single site! I've gone through the plugins and page code and cant find any more hardcoded links.
Lead Developer — 1st February 2011 (1 year ago) #
Sorry, I meant Wordpress at all. Just use firebug or chromes dev tools to see all the assets that weren't loaded via https.
Note it's pretty common for SSL sites to have some assets not loaded https, so most users have that error message disabled. You may be able to live with it.
Member — 2nd February 2011 (1 year ago) #
oh....my.....goodness!
//add_action( 'option_rewrite_rules', array(&$this, 'check_rewrite_rules') );
did the trick! FINALLY! Excuse my exuberance, but this was holding up a pretty large project on our end. Thanks much!
what the heck was the problem exactly? and is this due to a configuration on our end or will others potentially have problems due to this?
Member — 3rd February 2011 (1 year ago) #
Well I now have HTTPS running unbroken in Chrome and Firefox but I cannot seem to locate the asset that is causing IE to popup the error. It would be helpful to know if anyone had an issue like this for Marketpress as well so that I can rule out Marketpress as a potential cause.
Lead Developer — 3rd February 2011 (1 year ago) #
@edihtors, did you have pretty permalinks enabled on that blog?
That function checks your rewrite rules to make sure they've been added correctly and flushes if not. Many users who had poorly coded plugins installed had trouble with rewrites not sticking.
If it's not the permalinks thing, maybe another plugin is messing them up and causing the unending loop.
Member — 3rd February 2011 (1 year ago) #
@Aaron yes I had pretty permlinks enabled.
I'm using a custom structure of: /content/%category%/%postname%
Not sure if that would effect anything or not. I had this problem even with no other plugins enabled on the site, so it couldn't have been a conflict there.
I do have the latest nightly build on the site, so maybe it's an issue as a result of something done post - 3.1RC3?
Lead Developer — 4th February 2011 (1 year ago) #
Probably your custom structure. I'll have to figure out a way to prevent the infinite loop.
Member — 23rd March 2011 (1 year ago) #
Hi Aaron
I am not sure if this is related to my issue...
//add_action( 'option_rewrite_rules', array(&$this, 'check_rewrite_rules') );
I am running marketpress on nginx.
I have a 2GB server.
My avail mem went to under 40mb the other day and crashed everything.
Running WPMU + BP + marketpress + classifieds
Should I start a new thread or is this the problem?
Where is the above code ?
Cheers
John
Lead Developer — 23rd March 2011 (1 year ago) #
If that was your problem you wouldn't be able to get any pages to load on your site, so I doubt it.
Become a member