Multisite/Network Clarity

in your wp-config.php you would have to
define('WP_ALLOW_MULTISITE', true);

and try following these steps

https://codex.www.ads-software.com/Create_A_Network

Thanks mate – Are you implying that in the second site I want to add to my network, its config file needs to have the rules applied your suggesting? If not, I have done these steps already when I set up the network on my main domain.

Currently in site.com/help I have uploaded all the wordpress files for a new install. Do I need to do this and if so do I need to edit the config file with my database files so I would be good to go?

No. You never need to install WP more than once for a Multisite.

Multisite, once configured on site.com, will make virtual folders. If you set up a network there, delete the /help folder and (if you made one) the /wiki folder ??

Multisite, once configured on site.com, will make virtual folders. If you set up a network there, delete the /help folder and (if you made one) the /wiki folder ??

Thanks, I’ll give that a go!

In addition I have created the blog.dir file and given it writable permissions as well, is all this folder is a folder I create and name blog.dir as that is what i have done. If there is more to it, please let me know.

Also, yesterday you answered a question (https://www.ads-software.com/support/topic/linking-search-results?replies=2) I had about setting up so that both domain and subfolder could have search results/capabilities would be linked. Do I still need to add the plugin you suggested or should this now be taken care of through the network?

The blogs.dir folder holds the * media* files for the extra sites in the network. None of the actual blogs live there. As isptenu says – they are virtual. They will not show up on your server. They exist only in the database.

The blogs.dir folder holds the * media* files for the extra sites in the network. None of the actual blogs live there. As isptenu says – they are virtual. They will not show up on your server. They exist only in the database.

Great, thank you.

I have currently set up type.is & type.is/knowledge as the domains I’d like to use together, however type.is/knowledge looks funny, have I done something awry and will I be able to give type.is/knowledge a different theme from type.is’s?

Separate sites/blogs on multi-site can all have different themes, plugins and configurations. I’m not sure what you mean by “something awry” but if your root domain is “type.is” and you set up multi-site and create a site with the name “knowledge”, it is behaving exactly as planned. If you create another site with the name “awesomeness” it will appear as “type.is/awesomeness”.

You can use plugins to map domains and sites if you wish to have multiple sites with unique domains within the same multi-site install.

Thanks for the reply.

The issue I am encountering is when I click on ‘dashboard’ for type.is/knowledge in the backend, I get a redirect error: https://i.imgur.com/kjEj6.png – Any ideas?

Also, fwiw, here is currently what my htaccess file looks like:

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

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

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

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*)  [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$  [L]
RewriteRule . index.php [L]

RewriteEngine On
RewriteCond %{HTTP_HOST} ^www\.type\.is$ [NC]
RewriteRule ^(.*)$ https://type.is/ [L,R=301]

#Protect the .htaccess File
<files .htaccess="">
order allow,deny
deny from all
</files>

# disable directory browsing
Options All -Indexes

<IfModule mod_deflate.c>
<FilesMatch "\.(js|css|php|html|js^|css^)$">
SetOutputFilter DEFLATE
</FilesMatch>
</IfModule>

At first glance it seems like you have file permission problems. When you go to type.is/knowledge do you see the content but in very 1996-like Web formatting? That means it cannot read your CSS.

Can you verify the ownership and permissions for wp-admin, wp-content, and wp-includes?

The /knowledge domain does look very 1996

Can you verify the ownership and permissions for wp-admin, wp-content, and wp-includes?

wp-admin looks like -rwxr-xr-x

wp-content looks like -rwxrwxrwx

wp-includes looks like -rwxr-xr-x

It’s worth noting that I do have rewrite rules currently still in my htaccess file in addition to the rewrite rules I added when setting up the network if for any reason these may be causing conflict.

Oops, my mistake, I somehow had it in my head that you were getting 404 errors, not too many redirects.

Just to make sure we aren’t dealing with any plugin incompatibility, have you disabled ALL plugins and switched theme to 2010/2011?

Yowch. First let’s fix up your .htaccess eh?

#Protect the .htaccess File
<files .htaccess="">
order allow,deny
deny from all
</files>

# disable directory browsing
Options All -Indexes

<IfModule mod_deflate.c>
<FilesMatch "\.(js|css|php|html|js^|css^)$">
SetOutputFilter DEFLATE
</FilesMatch>
</IfModule>

# Force non-www
RewriteEngine On
RewriteCond %{HTTP_HOST} ^www\.type\.is$ [NC]
RewriteRule ^(.*)$ https://type.is/ [L,R=301]

# BEGIN WordPress
RewriteEngine On
RewriteBase /
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

Rule 1) Always put the WordPress block at the bottom. ??

Just to make sure we aren’t dealing with any plugin incompatibility, have you disabled ALL plugins and switched theme to 2010/2011?

I don’t have any plugins installed as this is a fresh install. Also, the only theme available and that’s currently being used is 2011.

Yowch. First let’s fix up your .htaccess eh?

That did it! Looks sorted now. Thank you to everyone for their help and promptness! Much obliged.

I was just mentioning it as a matter of course for doing support. There are a few plugins that cause redirect conflicts. But Ipstenu is MUCH more fluent in .htaccess matters than I. ??

I was just mentioning it as a matter of course for doing support

Regardless, I appreciate the help and effort as I agree it helps get to the bottom of things by ruling specifics out. The assistance provided has been exceptional. Again, thank you to all.