rjp92

I submit a mail on the support page, only I dont know what you exactly need for information. So you can answer that on the mail I just send

Hoi Cookieyes team,

I know that if I have to place some code in the wp-config file. But even then my website dont work if I do that. So I dont know what happens.

Before installing the older version I also know that the piece of code needs to be removed and I did that. So that should be not the problem

Gr Ron

Na geen reactie hier, mijn website helaas nu door Google lager is gerankt, de snelheid niet goed was en gekke teksten door elkaar op mijn website, ben ik weer terug naar de cookiebanner die ik hiervoor had. Want die gaf al deze problemen niet ondanks dat ik met die oude cookiebanner ook niet helemaal tevreden mee ben omdat je geen settingsknop hebt.

Well, I should have found the problem and the solution.

As I wrote above in my first reply, there are many rules in my htaccess file. Now I take them all off and put them per group back again in the file till I got the error again. The result were these rules:
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# WP REWRITE LOOP END

As you can see, they mess up with the rules we need for the WordPress multisite. How they came in it, I don't know.
Why I didn't find them earlier is because a put some other rewrite rules in the htaccess file that I think even caused the problem when I did the same as I mentioned above (take all oud and put the rules back by group again, till the error arise)

Still thanks to the people who helped me!

For now on to the next problem solving that arose now 
> bulletproof-security 
> google webmaster tool reconnextion to multisite

Thanks for the response Leasedlayer,

I know that link too. First, I did not move from local server to webserver, a year ago I install WordPress fresh on the webserver and build from there.

I checked already my site urls by WordPress as by PHPMyAdmin. I only came then to the solution that my ssl certification was not totally installed (http instead of https) but is know okey only to google not, but that should be no problem for my dashboard.

Browser caching, I already empty many times. As well open in a new web browser doesn’t give any result.

I know I have no problem with the network dashboard:
https//test.com/wp-admin is okay
https//test.com/wp-admin/network is okay

Only when I make a new submap site:
https//test.com/test/wp-admin doesn’t work

My site urls and home are both the same:
https//test.com/test

I tried to put the https// in wp-config file in the follow rule:
define('DOMAIN_CURRENT_SITE', 'https//test.com');
it only not works, then the whole site get an error because you get 2 times https// in the address

Thanks for your fast response t-p

I know that link, I already try out the possibilities on that websites. I only can say, that when I try to make a new htacces file it does not work by how it’s saying. There is coming no new htacces file on my server.