creating network/multi-site = not working and can't view original blog!

Resolved janeenurs
(@janeenurs)

12 years, 11 months ago
Hello – I hope that someone can help me with this please.. it is quite a lenghthy description which hopefully has a simple solution!

I am trying to create a network/multi-site so that I can have two sites/blog’s. I am creating my WP site locally on a Mac, using MAMP. Have followed instructions to enable the Network on the WP Dashboard under Tools – have tried making suggested changes to the Wp-config.php file – changes suggseted are as below:
```
define( 'MULTISITE', true );
      define( 'SUBDOMAIN_INSTALL', false );
      $base = '/';
      define( 'DOMAIN_CURRENT_SITE', 'localhost:80' );
      define( 'PATH_CURRENT_SITE', '/' );
      define( 'SITE_ID_CURRENT_SITE', 1 );
      define( 'BLOG_ID_CURRENT_SITE', 1 );
```
Incidentally, in the file already is a line saying:
```
define( 'WP_ALLOW_MULTISITE', true );
```
I have tried several times to add the suggested text to the WP-config.php file and to then log-in again, as instructed – but each time I do I get an error page telling me I cannot log-in. When I remove the text from the config page I can log-in again – but no sign of the Network Admin link supposed to be now on my dashboard. However when I go to modify/look at Network via Tools again there is a message saying ‘An existing WP Network was detected’ – so evidently I’ve gone some way to creating it.. just not all the way..!

Also, as instructed in the Enabling instructions under Create a Network/Tools – I’ve tried to modify .htaccess file – or as I later read in WordPress help page instructions, create one. As I couldn’t find and .htaccess file in the HTDOCS – despite looking for system files etc. So I have created one with the relevant text in it. Though each time I search for it again I cannot view it…

I am so close to having a network up and running, or at least I thought I was! Any help would be much appreciated on this, thank you. When I search for the .htaccess file a seletion of other files comes up, but never that one, despite enabling system files in the search.

Many thanks in advance.

P.S – As an update I have just tried to preview my current blog that I’ve already started to work on – though it isn’t on a host server yet – and I am now getting an error message saying it is ‘not found on the server’ or when I click on it in the dashboard an error message saying ‘Firefox has detected that the server is redirecting the request for this address in a way that will never complete.’

I’m guessing that in starting to set up the Network (and giving it a name..?) that this has somehow altered the URL/permalinks for my current blogs/future network??

P.P.S – I have also just upgraded from 3.1 to 3.1.2, backed up data-base before hand..

Oh dear… a bit of a tangled up mess it seems, hopefully a kindly soul will be able to help me untangle it.. please!
Thanks.

Viewing 10 replies - 1 through 10 (of 10 total)

Moderator Ipstenu (Mika Epstein)
(@ipstenu)

🏳️‍🌈 Advisor and Activist

12 years, 11 months ago

define( 'DOMAIN_CURRENT_SITE', 'localhost:80' );

I believe that’s the problem right there. MultiSite doesn’t like colons in the URL.

Thread Starter janeenurs
(@janeenurs)

12 years, 11 months ago

As another afterthought – and after reading more forum entries about this and checking back with the WP Create a Network page
I wonder if the reason this isn’t working for me is because of extracts copied at bottom of page from WP guidelines for installing a Network: namely that 1. my current wordpress URL is a localhost one and 2. my current wordpress blog is more than a month old (therefore encountering permalink problems)???

I look forward to hearing any comments please! And, if this is the case, is there a way to un-install the Network at this stage, so I can revert to the single site option for my blog – which was working fine (locally) before I tried to create a network.

Thank you.

# You cannot create a network in the following cases:

* “WordPress address (URL)” is different from “Site address (URL)”.
* “WordPress address (URL)” uses a port number other than ‘:80’, ‘:443’.

# You cannot choose Sub-domain Install in the following cases:

* WordPress install is in a directory (not in document root).
* “WordPress address (URL)” is localhost.
* “WordPress address (URL)” is IP address such as 127.0.0.1.

# You cannot choose Sub-directory Install in the following cases:

* If your existing WordPress installation has been set up for more than a month, due to issues with existing permalinks. (This problem will be fixed in a future version. See Switching between subdomains and subfolders for more information.)

Thread Starter janeenurs
(@janeenurs)

12 years, 11 months ago

Hi, thanks Ipstenu – is it ok to lose the colon then? And did you see my latest post re: 1. and 2. possible reasons why everything’s gone caput?
If so do you think I’m way off mark or could there be some sense in this?

Moderator Ipstenu (Mika Epstein)
(@ipstenu)

🏳️‍🌈 Advisor and Activist

12 years, 11 months ago

1. my current wordpress URL is a localhost one

This isn’t a problem. MultiSite knows how to cope with localhost, but NOT localhost:80 (so if you CAN drop the 80, that’d be good).

2. my current wordpress blog is more than a month old (therefore encountering permalink problems)

Kind of yes but putting in define( 'SUBDOMAIN_INSTALL', false ); will override it, so it shouldn’t be an issue.

Thread Starter janeenurs
(@janeenurs)

12 years, 11 months ago

Thanks – I’m not sure how to lose the 80 – any advice would be appreciated. Aggh – it all seems to be grinding to a halt, I’m now not able to start Mamp up at all on my Mac – when I try to start the Mamp servers the MYSQUL server comes on automaticaly, but not the Apache – then I click start servers and the MYSQUL server light goes red too…

Unsure why this has happened since last night when all were still working ok. Although this a.m have tried fiddling a bit with the installation as per another guy’s instructions to see if I can get Network working, but undid all his suggestions after I couldn’t start MAMP anyway.

Have since tried typing:
killall -9 mysqld into the Terminal – this has worked in the past when MAMP has been tempremental… but no luck this time. Instead now get this error message in Terminal.

No matching processes belonging to you were found

Any comments/pointers much appreciated – thank you.

Incidentally these are my error logs from Apache as per yesterday when not able to view my blog….

[Wed May 04 14:39:08 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/wp-content/themes/sample/images, referer: http://localhost/wp-content/themes/sample/style.css
[Wed May 04 14:39:08 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/wp-content/themes/sample/images, referer: http://localhost/wp-content/themes/sample/style.css
[Wed May 04 14:39:08 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/wp-content/themes/sample/images, referer: http://localhost/wp-content/themes/sample/style.css
[Wed May 04 14:39:08 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/wp-content/themes/sample/images, referer: http://localhost/wp-content/themes/sample/style.css
[Wed May 04 14:39:08 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/wp-content/themes/sample/images, referer: http://localhost/wp-content/themes/sample/style.css
[Wed May 04 16:45:00 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/blog, referer: http://localhost/wp-admin/post.php?post=19&action=edit
[Wed May 04 16:45:44 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/blog, referer: http://localhost/wp-admin/post.php?post=4&action=edit
[Wed May 04 16:46:50 2011] [notice] caught SIGTERM, shutting down
[Wed May 04 16:46:51 2011] [notice] Digest: generating secret for digest authentication …
[Wed May 04 16:46:51 2011] [notice] Digest: done
[Wed May 04 16:46:51 2011] [notice] Apache/2.0.64 (Unix) PHP/5.3.5 DAV/2 configured — resuming normal operations
[Wed May 04 17:03:19 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/blog, referer: http://localhost/wp-admin/post.php?post=19&action=edit
[Wed May 04 18:25:39 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/blog, referer: http://localhost/wp-admin/post.php?post=19&action=edit
[Wed May 04 20:04:06 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/blog, referer: http://localhost/wp-admin/post.php?post=19&action=edit
[Wed May 04 20:56:53 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/;80, referer: http://localhost/wp-admin/options-general.php
[Wed May 04 20:57:24 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/;80, referer: http://localhost/wp-admin/options-general.php
[Wed May 04 20:57:25 2011] [error] [client ::1] File does not exist: /Applications/MAMP/htdocs/;80, referer: http://localhost/wp-admin/options-general.php
[Wed May 04 21:04:53 2011] [notice] caught SIGTERM, shutting down

paulrowe51
(@paulrowe51)

12 years, 11 months ago

Since :80 is the HTTP default port, browsers will do the same thing with it or without it. Can’t you just drop it?

If it’s gotten into site domain or URL settings, you might need to take it out.

I naively tried to set up a devel copy of a web site that has both single and multi-user WP, and tried to put it on an alternate port of the server (which is serving another main purpose), and ran into the message out of WP initializations: “Multisite only works without the port number in the URL.”
pratikmhta
(@pratikmhta)

12 years, 9 months ago
Hello Ipstenu ,
I am having a problem for wordpress multisite , I have just installed a new wordpress 3.2 on my server which runs Ubuntu , and did exactly what is specified in the Network Setup part
Using
1. define('WP_ALLOW_MULTISITE',true);
Then setting up network .
2.
```
define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', false );
$base = '/path/to/wordpress/';
define( 'DOMAIN_CURRENT_SITE', 'mydomain.com' );
define( 'PATH_CURRENT_SITE', '/path/to/wordpress/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );
```
3.Created blogs.dir
Created .htaccess file in /path/to/wordpress/ with following contents
4.
```
# BEGIN WordPress
RewriteEngine On
RewriteBase /path/to/wordpress/
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
# END WordPress
```
After this when i create a site it gives 404 not found error .
dgilmour
(@dgilmour)

12 years, 9 months ago

@pratikmhta Can you confirm that “/path/to/wordpress” in line 3 has been replaced with the path to your installation?

pratikmhta
(@pratikmhta)

12 years, 9 months ago

Yes dgilmour ,
I can confirm that it is /path/to/wordpress/ you missed the forward slash at the end , and wordpress is in my /var/www/path/to/wordpress/ , but in the network setup it tells to give RewriteBase as above , so i have the same . and i think wordpress will map it to /var/www/ . or should i give relative path. like path/to/wordpress/

Moderator Ipstenu (Mika Epstein)
(@ipstenu)

🏳️‍🌈 Advisor and Activist

12 years, 9 months ago

pratikmhta

PLEASE make a NEW topic for yourself. You are NOT having the same problem as the OP (that was clearly a ‘you can’t use port numbers in your URL with MultiSite’), and I should have flagged this resolved months ago. Secondly, this topic is over 2 months old. No need to restart unless you have the EXACT same issue 🙂

Where should you start? 404 not found implies your server is NOT reading the htaccess codes. Go check in your httpd.conf file and ensure AllowOverride is set to all. If it’s not, make that new topic and please tell us if you can get pretty permalinks to work on your MAIN site with MultiSite turned off.

(And if you’re trying to store WordPress in a subfolder but have it run as if it was in the root of your domain, that will never work.)