sdoss

I can’t say it’s dedicated to the web, as it’s in-house development as well. But not entirely local, as we have several websites either set up as development or served from this machine. Not a pc, though, and if you need more info, I can get you that.

The domain we’ve set up is ca-wp.com.

I haven’t attempted mapping yet, as I want to get the apache thing worked out. The other websites’ pages are not affected, just the pages coming from wordpress. So, again, I’m thinking something in my apache setup, either the ‘*’ host or the ca-wp.com host.

Also, as we’re new to this and quite excited to be exploring wordpress, we’ve attempted a couple of our own themes, and I’m going down the path of picking them apart (as the internal redirects were the result of things in the functions.php files that shouldn’t have been there)

So…if you have suggestions as to what I can look at, it would be greatly appreciated. As you can tell, I’m not ‘literate’ in these things as I probably should be. Have learned alot since starting this, tho ??

resolving a thread does not close it. only mods can close threads

ok. I’ll figure out the forum eventually.

turn off your plugins to start

don’t have any plug-ins activated

and what host are you on

on a debian machine, apache2, php 5.2.5(?) and mysql

Tried to close this post; shows resolved, but I can still post. Tried to open new thread on different subject; shows unresolved, but can’t post. Having issues with Apache/browser/time it takes to load a page, even through wp-admin.

I resolved an issue where my apache error.log was reporting a loop, in that going to the domain of my wordpress site exceeded the limit of 10 internal redirects.

But my page(s), including wp-admin, are taking an average 1-5 minutes to load!

Have verified .htaccess; in fact, recreated with it’s original rules. Have verified no .htaccess files in parent directory, even though mine is in document-root. Have attempted adding rules to catch loops, and have since removed them as there was no change. Any suggestions as to where I can look next?

And, I did open this problem under a new thread, but it defaulted (apparently) to resolved and won’t let me post to it.

Thanks

ok

Well, put the widgets on. Haven’t mapped yet. Now have an issue with Apache, throwing out the message

Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInt
ernalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace., referer: https://www.mywordpresssite.com/

causing the pages to take forever to load. Do see a missing image error, as well, then a ‘graceful restart’ message. Will research (and ultimately, learn my lesson) this, fix it, THEN on to mapping.

Andrea, and Ipstenu, thanks for your patience and help in this. Next issue, I promise not to be so stubborn ??

It’s amazing how over complicated we humans tend to make things :/

So…I’ve redone my network based on domain name rather than ip. Should have done this in the first place.

Had to replace all occurrences of ip in the database with domain name. Seems to have worked, except I’ve lost widgets on the one page that was altered before I did this. Clues on how to get the widgets back? Or where they went?

On to the next….

I can see all sites from with Super Admin. I can edit, view, go the backend – all seems good, and now I think is the time to map domains.

Yes? Will post back momentarily…

Bless you ?? Will post back when (NOT if) I get it working.

At the very least, we’re good for telling you what it’s not. ??

Andrea – isn’t that the best way to teach?

What’re my chances of seeing the directives you have for your default and wordpress virtual hosts? Name your price ??

Now we’re getting somewhere. ??

Ok…..After ensuring that I’ve got Allow Override All in my Apache’s virtual host for *, I’ve got my dashboards back, and my page(s) in my subdirectory site….and I can see the pages in my main site ?? ?? ??

Making progress here.

Apache, on my server, is configured with the default virtual server, a virtual host designated as ‘*’, multiple virtual hosts for non-WordPress websites, and a virtual host for WordPress.

The non-WordPress sites are in sub-directories of the document-root directory.

WordPress is in the document-root directory.

My problem is, the default server has the following directive

RedirectMatch ^/$ /apache2-default/

that I believe I’m hitting when I attempt to access my WordPress via the virtual host url: I get the Apache directory structure of /apache2-default :/

So, I remove the redirectmatch directive from *, go to the browser, type in https://www.mywordpresssite.com, and get the home page of my main site. I type in https://www.mywordpresssite.com/wp-admin, and get the home page of my main site. I type in https://www.mywordpresssite.com/wp-login.php, and get the home page of my main site.

I believe my problem is one of two things…either, my Apache configuration for my virtual host of https://www.mywordpresssite.com is jacked, or, I have a problem with the apache default server and wordpress operating out of the same document-root.

Any suggestions?

btw, in spite of the frustration, I’m having a blast with this ??

Ok. I’ve recopied all files/directories etc once again to my document-root directory. The .htaccess file was changed as I noted above. I went through each and every entry in the database, removing references to the sub-directory where I previously installed wordpress. I think I got them all, but have someone currently double checking that.

I can hit my Admin screen by typing in <server ip>/wp-login.php. In the Admin, I can still see the two sites I’ve created (using the sub-directory process in the network) when I open the Sites option from the Super admin menu.

I can get to the dashboard for the main site, but cannot view any of the pages.
Back on the admin page, under ‘Sites’, when I mouse over the additional site name, I can ‘edit’ the site. But, I cannot get to the ‘backend’ or ‘visit’. I get the ‘page not found’.

So, given that I’ve changed the .htaccess file correctly, and gotten all files/directories copied, and gotten all references in the database changed to be appropriate, what else can I look for?

I’m gonna get this, eventually. Thanks in advance for any suggestions you may have.

Holy cow.

So the only thing I missed on my first attempt is the database changes??

The best way to move Multisite is to move the files, edit the .htaccess (if the folder name containing Multisite changed), and then manually edit the database.

Is the .htaccess file the ONLY external file that needs to change? Or do I edit the wp-config.php file as noted above?

Ok. Went back to step 1. Removed everything I copied into root; went back to original install. Per step 2 in ‘Moving WordPress’ documentation (codex.www.ads-software.com/Moving_WordPress) logged into wp-admin, went to Administration>Settings>General panel.

I can see no box for WordPress address (URI).
I can see no box for Blog address (URI).

Any suggestions?

Got that. As I hang my head in shame, am going to re-do the move. Maybe this time, if I follow instructions appropriately, it’ll work.

There’s a reason for instructions, right ?? Will post back as soon as it’s up.

Thanks for your patience.

Got the go-ahead to move my wordpress installation up to the document root.

First question: I’ve copied (not moved) my original installation and all sub-directories thereof up to where they need to be.

I’ve changed the .htaccess file to start in root (RewriteBase /)

I’ve changed wp-config.php to start in root ($base = ‘/”) and changed the current-site path (the main site in the network) to also start in root (define ( ‘PATH_CURRENT_SITE’, ‘/’ );

I didn’t see anything in wp-settings.php that should change, nor in index.php

wp-config still points to multisite turned on

Apache config for https://www.mywordpress.com was changed to point to root

So, I must be missing something, as I can attempt via a browser https://www.mywordpress.com/wp-admin, and I get the Apache default (It works!).
Same as when I try /wp-login.php.

I’m thinking something in my old network setup is still pointing to the original; i.e., my main site path points to the subdirectory where I had originally installed WordPress. I believe this has to now change to have a path of just ‘/’, and my other defined sites’ paths need to change as well.

Any guidance will be greatly appreciated…..

OK, so…if I want to keep the url ‘sacred’, then the domain must be mapped to the site in WordPress. And WordPress must be in document-root.

If I choose to leave it where it is (in a directory under document-root), then I have to live with the url reflecting the re-direction.

Ok, so to make sure I understand the whole url/mapping thang….

IF I keep sub-directories and IF I map domains:

https://www.site1.com has a dns record pointing to myserver.
Apache on myserver is configured to go to WordPress when receiving a request for https://www.site1.com
WordPress recognizes that https://www.site1.com is mapped to WordPress/site1 and somehow serves pages from this site.

If I don’t map domains, and keep subdirectories, then the visible url would change from https://www.site1.com to https://www.mywordpress.com/site1

Correct?

And, btw,

Actually, the domain mapping plugin will not let you map domains if the install itself is in a folder. ??

If you’ve changed wp-config.php to set sunrise=on, and wordpress is in a directory, you can’t even get to the admin page…instead, there’s a lovely warning about virtual servers

Thanks so much for your quick responses.