[Plugin: Networks for WordPress] Any problem if I remove these directives?

Update
I forgot to say one thing…I have used a similar plugin by john . I have used it without changing the default configuration.

BTW…I have a suggestion. I have checked the both the plugins to compare.But if you make a comparison chart between these two plugins would be useful to us. Both the plugins are almost similar

Thanks!

Hi, asshu.

Thanks for your interest in the plugin! Others have reported that things work fine with those directives in place, so if they are working for you, just leave them there.

That being said, if you run into any issues, I’ll ask that you remove them before I can help troubleshoot things.

It looks like the WP Multi Network plugin you linked is a copy of my original Multi-Site Manager plugin from the WPMU days, updated with the new “Sites” for blogs and “Networks” for sites naming scheme. So, the plugins will be similar since they come from the same source. ??

Networks for WordPress has been updated with support for WP 3.1 and better use of the “Network” name feature, along with some better documentation.

David ,

Thanks a lot for your response !

David Dean,
This is again regarding to :

DOMAIN_CURRENT_SITE, PATH_CURRENT_SITE, and SITE_ID_CURRENT_SITE

I can see that there are some issues if I remove these.
1)If I use a dedicated IP. The page shows up an error message

No site defined on this host. If you are the owner of this site, please check Debugging a WordPress Network for help.

Of-course , It is not a big problem as it works normal with domain. But need your advise

2)I cannot able to map an alternate domain to main site

There are not the big problems . But just bringing them to your notice

Thanks !

Hi! I’ll try to answer these as best I can:

1) If you wish to use the IP address, you would need to create a site with the IP address as the “domain name”. To be honest, I’m not even sure that would work, but it definitely won’t work without such an entry.

2) I’m not sure what you mean by “map an alternate domain to main site” – if you want the main network’s domain to be different, you can change that from the Networks –> Edit option.

But I get the feeling that isn’t what you mean. Can you clarify?

@asshu
We had the same issue that the ip address returns an error message when accessed directly.

The problem with that is that the error also includes an error-500 header which in turn creates problems. We had a Plesk watchdog checking if the server is working fine (apache service check) and this was done via ip address. Therefore this always returned an error on each check and the apache server got restarted automatically every 5 minutes.

We left the directives active, fixed the problem. Trying to figure out now if there are any downsides to that…

@david

any new clues if the mentioned directives can safely stay enabled or if this will cause problems with the multi-network setup?
We use your plugin and the domain mapping, it seems to work even with the directives left inside the wp-config.