wijngaarde

Thanks Neighbor! It seems that another plugin caused the issue.. which reveiled itself after deactivating autoptimize..

Vriendelijke groeten uit Nederland,
Steven

Thanks Mark. I didn’t know if you were going to reply so I’ve created a work around (sticky header without using the plugin). So it actually works now on the mentioned website ??

But I’m still interested if you recognize this issue and what the solution might be.

Thanks!

Would be great to get a reply..

Hello Janneke,

I still don’t know why it suddenly stoped working (since I only updated your plugin and not the maintenance plugin or other plugins).

But anyway, I found a bypass. I added an exception for my new login page to the code of the maintenance plugin, so it doesn’t bug anymore.

Without this exception it still didn’t work in 2.2.

But for me this is resolved since I can bypass it.

Thanks!!

Kind regards,
Steven

Hi Janneke,

I tried to access wp-login.php with the plugin enabled and it had the same result. Just can’t login to WordPress anymore. Not with /login not with /sitemanager and not with wp-login.php.

The only fix is to go to FTP and rename the your plugin or “Anticipate” or “Prevision”.

Thanks!

And let me know when you update I’ll be happy to test.

Kind regards,
Steven

Hi Janneke,
It’s not my theme and it was in the list under the name prevision. Its a premium plugin found on code canyon. Before i used this one, i used anticipate. So i bought a new one but your plugin has the same effect on the new plugin as on anticipate.. but only since 2.1.1 as I said before.

By the way I now tried “better wp security” and its functionality to do the same as your plugin. And that worked fine. Just like your plugin did before 2.1.1. Perhaps this helps.

Great! Thank you!

Besides the fact that it resets (that doesn’t bug me), remains the fact that when using a maintenance plugin it will somehow redirect all traffic to any URL on the site to the maintenance page.

Perhaps somthing goes wrong there.

This didn’t cause any problems in version 1.9 of your plugin (I must say I didn’t test version 2.0.) but the problems with these kind of plugins started since 2.1.1.

And since I know for sure that one of the maintenence plugins didn’t update since january last year, this is caused by some change in the rename wp-login.php plugin somewhere between 1.9 en 2.1.1.

Maybe this helps to help me..

Hi Janneke,

Thank you for looking in to this! These are the plugins:

[edit]

Thanks!
Steve

Thanks Esmi!

Thanks Ipstenu!

Per accident I discovered the solution myself!

My webhost is running PHP 5.2 and this is giving me various permission errors recently on my website. Especially when making use of auto-updates such as updates of themes or core-updates.

But when I pasted this code in my .htaccess file:

<FilesMatch "\.php$">

AddHandler x-httpd-php53 .php

</FilesMatch>

I basically told my server to use PHP 5.3 instead of 5.2. This solved all right related issues I was facing. Also the issue mentioned in this post.

So this was my solution!

Okay, step one: Did all the files get set with the right permissions? ??

Well, I didn’t change anything myself.. just copied the files. Is there a specific guideline that I could follow to check if the permissions are set correct on the new server?

?? The guidelines you gave somebody else in another blog post.. (thanks by the way!) but I can’t find the blogpost I used anymore..

Anyway, what I did:

* Copied all files to the other server
* Backed up the database and imported the database into a new database on the new server.
* Turned on Wildcard DNS on the new server
* Since the domainname also changed, I used the program you refered to from https://interconnectit.com/ to do a serialized find and replace.

Everything works fine on the main website of the wordpress network, even the pictures.

But as mentioned not on the subdomains..

I realy hope you can help me..

Ipstenu thanks!

Thanks Ipstenu so far!

But what I really want to know is if privacy settings from subdomains effect the SEO of my mainwebsite.

For example:

My main website is: https://www.domain.com
And I have a networksite: https://theme1.domain.com

So I want https://theme1.domain.com not to be indexed by search engines and therefore set the privacy settings on “do not index”.

But on the main website https://www.domain.com I set the privacy settings on “index this website” because I will do all my SEO efforts on this site.

Will the fact that I’ve set the privacysettings on https://theme1.domain.com on “do not index”, influence my SEO negativly with for example google on the main website https://www.domain.com?

Hope you understand what I mean, if not let me know!

Thanks in advance!!