mantismamita

I seem to have made some progress. I set the domain name to https://www.subsite.com rather than subsite.com (which I would have preferred) and I got the message about enabling cookies.

I added:

define('ADMIN_COOKIE_PATH', '/');
define('COOKIE_DOMAIN', '');
define('COOKIEPATH', '');
define('SITECOOKIEPATH', '');

and then was instructed to comment out define('COOKIE_DOMAIN', ''); which I did. I am now getting the following message:

The domain mapping plugin only works if the site is installed in /. This is a limitation of how virtual servers work and is very difficult to work around.

The good news is that the front end of the site is now visible. So I presume I just need to set the correct path for wp-admin but am having trouble doing so.

Hi Chris, just thought I’d let you know that its fixed. ??

The server support was amazingly unhelpful and told me that I shouldn’t be putting the install in a subdirectory. Also that WordPress code is complicated. The 104 error turned out to be a server timed-out sort of thing.

There are a couple of issues going on with the theme that compounded the problem but there also appears to be some caching done via wp-config (so your idea was a good one.) There is a cache folder in wp_content in addition to a file named advanced-cache.php. So apparently I was wrong when I said there was no cache.

Anyway many thanks again for your help yesterday.

Good idea.
This is out of my league anyway. Thanks a million for your help Chris. I’ll let you know how it all went.

Ah, yes I read that yesterday and tried everything and ended up contacting the hosting provider who told me there were lots of errors to fix. -godaddy ??

I found this though:
This is a PHP-FCGI limit error you’re receiving. You’ll need to adjust either the “PHP_FCGI_MAX_REQUESTS” variable inside the “fcgi-bin/php5.fcgi” file for the domain or “FcgidMaxRequestsPerProcess” variable inside the Apache config file.

104 Connection reset by peer: mod_fcgid: ap_pass_brigade failed in handle_request_ipc function…

Not sure what to do about it though.

Ok
newdirectory

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /newdirectory/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /newdirectory/index.php [L]
</IfModule>

# END WordPress

root

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Confirmed
Yoast activaed = 301
Yoast deactivated = 500

I’m going to go look in the server log and see if I can find the error.

I think the compensation had to do with the checkout flow or something. It was definately there as a fix for something that should have been fixed otherwise.

The errors only affect the homepage and register pages it seems.

Wierd Now I’m getting a 500 error.
After deactivating Yoast.

I have to admit it is a pretty juicy bone ??

I’m wondering if Yoast SEO might have something to do with this? I keep coming across it in my searches for 301 errors.

I appreciate your tenaciousness. I would have given up on me by now ??

Ok done. Still no change ??

It was working fine out of the subdirectory for a long time though. Everything fell apart during the 4.0 update. Although there have been persistant redirection problems which someone attempted to correct using Peter’s login redirect.

Yes, that’s what I had. I didn’t notice the Rewritebase was different in the second.

That it does. And in the newdirectory folder
require( dirname( __FILE__ ) . '/wp-blog-header.php' );

Both .htaccess files have the same thing.

I was thinking of reinstalling 4.0 as that is when the redirect loop troubles started. I think it was when I deleted the redirect urls from the plugin although I still had it installed and activated.

What do you think? Actually i’m ready to try about anything at this point ??

I double checked that everything was done properly and apparently it was. There are still two copies of .htaccess one in the root directory and one in the folder. The index.php in the folder still has the original path. Not the new path.

Could that be the issue?

EDIT: No, that looks likes its supposed to be the case

Ok I see the rewrite rules but I’m not entirely sure how to decipher them :/

Incidentally I didn’t see anything in the rewrite rules concerning the register page

I sent you the link via the contact form on your site.

It is a subdirectory install.
That’s what I’ve been doing to flush the permalinks although I tried changing them to the default as well.

I’ll try the debug this plugin. Does it display anything on the front end?

Thank you very much for your help ??