Angela

I’m doing a subdomain installation, there is no subsite blog “named” blog, but one of the subdomains is called blog. Why are you ooooh-ing? I’ve had this setup for over 2 years, and this week is first time this happened….

Just tried that, waited for 2 days, hoping it would be caching problem, but that code is not really responsible for this weird situation. Any other ideas how this happened?

Got it, thanks

ah, I see

ohoh, guess I shouldn’t use the next time.

Really, that’s interesting… I’ve had to setup/destroy a few testing accounts in my WP installation and all of those went well (as in the number changed correctly). Where could’ve the bug be originating from?

Unfortunately, I only have backup for a week. Nor does my hosting company keep backup for very long either.

Sorry for the late reply, I haven’t had time to do it. I just optimized the tables now, but the invisible admin is still there…. So what now?

Found it, Easy Nivo. Although not exactly what I’m expecting (somewhat inflexible in choosing what image to display), but it’ll suffice.

Just thought I should update the information. Somehow, I went back to change all https://www.example.com back to example.com and now it works fine. Most of it anyway, but still having trouble with that blog farm thing. So thanks for all the inputs, they have been very helpful.

optimize? what does that imply exactly?

yes

Edit: come to think about it, i recently did lost some random data (like plugin suddenly reset itself, like a post lost, stuff).

Hi,

I tried the set of rules you gave me, Ipstenu, but it caused a 310 redirect (right back to the beginning of the whole thing). It got me thinking, there must be some sort of redirect in the first place, no?
Redirect errors are caused by loops, that I know. So basically one rule is trying to direct https://www.domain.com to domain.com (server alias) while the other is redirecting domain.com to https://www.domain.com (your rules). Perhaps should I just remove that server alias, and try to add an htaccess rule to allow typing in of https://www.domain.com (and try to point it to domain.com)?

Another possible culprit that has come to mind is the W3 total cache. I’m using the plugin and it generates a huge amount of htaccess rules that was previously placed before the #wordpress section of htaccess. I moved it to the bottom, but nothing changes.

Now the really weird thing is that, even though I disabled blog farms AND user signup. Somehow my WordPress installation is offering it? How did it override that logic?

Angela

Edit: in addition, I’ve also tried your method Backups, to create mu-plugins and insert custom.php. Unfortunately, it still redirects to wp-signup.php?new=domain.com.
PS: if someone needs to access the back end and take a look, feel free to give me a holler at [email protected] (swap y for i).

Ah, sorry for the confusion. I just found out that someone rename my htaccess, causing all of these problems. Darn it, the hosting company modified the file without even asking me…

Do you mean a permission problem?