Roswitha Gerhart

Hi Dieter,

The only solution I found and which works to get a final German MU-installation, is to install the English source code, not start with the German one. Then you will have the choice to chose language and can completely install the German language.
Starting the installation from the German source code of WordPress instead does not work correctly for me. I tried it several times and could not bring it to work, while the English source code worked on the first try and the in the German version not included language swap at the beginning of the installation process was very comfortable to use.
As the English version offers the complete language swap to a complete German installation, the end result was exactly what I wanted to get anyway and is hopefully what you need as well.

I hope this helps. Good luck and best regards,
Roswitha

P.S.: I think the error lies somewhere in the sign recognition of the MU-code, as the error detection already reports the error for the first line of code, before any significant information can be given. So it is a fundamental error, erasing all possibility to find the faulty code part manually.

Thank you, Ipstenu, for your help with the problems.

The wp-config.php file started with the right signs and also downloading and newly installing the German version of WP 4.1.1 with a new databas again did not help with getting the site to run after switching it completely to the Multiuser version. The site did run as long as it was a single WP site or only had the enabled MultiUser code in the wp-config.php. As soon as I put the additional code part for the MultiUser platform into .htaccess and wp-config.php, the site and backend were no longer accessible.

I even thought, some of the server requirements could have caused the problem, so I searched extensively and even contacted my provider, before I finally put another website into the new account and started a separate installation of the English WP 4.1.1 code.
When this installation went through fine, I then tried the English code on the other so far not working domain as well and this code worked fine here too.

So finally, after an extensive search, my conclusion is that the German WP 4.1.1 code causes the problems in the MU-Installation, as with the English code everything works fine.

Where can I report this issue with the German WP 4.1.1?

Thank you very much for taking the time and helping me in my search for a solution !
With best regards,
Roswitha

Hello ssr64,
the website is: https://creative-historical.de

Hello Ipstenu,
The error message I get with turning WP_DEBUG on is:
“Warning: Cannot modify header information – headers already sent by (output started at /usr/www/users/creatisp/bmt/wp-config.php:1) in /usr/www/users/creatisp/bmt/wp-includes/pluggable.php on line 1178”

I already tried to spare you time and checked the message with hotline responses online, but still just don’t know what to do with this message, because no individual plugin or theme is installed yet. So far it is just a blank new WP installation on an absolutely blank and fresh account.

Thank you very much for both your fast responses and help!
With best regards,
Roswitha

Thank you very much, Ipstenu and Andrea_r, for helping me with my problem.
I fear, that leaves only the option to rethink the page concept and throw the current installation out and make it a single WordPress installation.
I am not really happy with that, but think that is the only option left open now.
Thank you very much for your kind help !

Thank you very much, Ipstenu.
The parking of the domain already re-locates the abc.com domain to the a-b-c.com domain. The server settings in that regard are already in place and are counterchecked by my server provider, so really should be as they should. And the entry of the abc.com URL does already start the a-b-c.com URL.
The remaining problem is, that the WordPress installation now treats the incoming second domain abc.com as a newly to register blog and not the identical start for the main a-b-c.com.

Is that something I can get the WordPress installation to handle as intended? I think, the WordPress installation somehow needs to get the message to treat the abc.com domain like the a-b-c.com domain.

a-b-c.com is an Add-on domain. (I have other installations and domains in that account as well and this domain is a separate Add-on domain in that account space.) abc.com would be the parked domain, which should go on top of the a-b-c.com installation and should not appear as separate entity.

I hope that information helps.
Thank you very much, Ipstenu!

Sorry for making it so complicated and unclear. I am not sure the terminology of my server provider is the same as how you use it.

The abc.com [URL1] domain should normally just start the a-b-c.com [URL2] and this already works for other installations I have on that server, not running with WordPress. So this setting should be equivalent to what you call ‘parked’.
The whole WordPress installation for a-b-c.com is situated in an add on, but here I am not certain that my server provider uses it in the way you do.

I hope that makes it a bit clearer what settings I made for the WP-Network.
Thank you for your patience and help, Ipstenu!

I am not sure how I can do the parking of the domain and get it to work correctly.
I am currently not using domain mapping plugins.
The abc.com domain is already set to start the root directory of the a-b-c.com installation. There it does start the WordPress-installation, just is not recognized as a parallel entry point to the a-b-c.com website, but instead is treated as a new blog.

I already contacted my server provider and got the answer,that all settings regarding the server are o.k. and correctly set. The remaining settings would need to be adjusted in WordPress.

So here I am and trying that.
Thank you for your kind help, Ipstenu!

Sorry for the used unclear terminology (I translate here).
I need to redirect the whole domain abc.com to the main WordPress installation on the domain a-b-c.com.
abc.com is no separate installation or should not appear with separate content at all, but only should redirect the user, who enters this writing variation, to a-b-c.com.

a-b-c.com is the main installation, already running as it should as a WordPress MultiSite network, where the registration of new blogs is blocked.

Thank you for your help, Ipstenu!

Thank you very much for your tip. I will ask in the MultiSite forum.
Best wishes, RGerhart

I tried this rewrite code, as I have the same constellation of websites and want to redirect one page (abc.com) to the WordPress installation on the other domain (a-b-c.com).
The domains both are rooted to the same directory and when I start the second domain, WordPress (with activated MultiSite) treats it as if I try to register a new blog and leads to the following URL:
https://a-b-c.com/wp-signup.php?new=abc.com
Is it possible to completely treat the WordPress start as if I had started the a-b-c.com ULR when entering abc.com?

The Rewrite-Code does not change the start of the website in my installation. The website is treated in the same way with or without the rewrite condition.
Thank you for your kind help!
RGerhart