shadowshiftcom

Mika, Ok works for me, I’ll just stop worrying about what nonsense search engine robots come up with… Thanks! You Rock!

Thanks Mika, I really appreciate your views on this ??

It does not exist, its just an example of something that does not exist. Its not the most important thing in the world for sure ?? I have been ignoring it a long time but for any never existing, non existing or previously existing but no longer existing .php file it just seems like the stock .htaccess does not handle it elegantly as it does for other file types or as I would imagine designed. Or I’m being blind, missing a dot or a t cross somewhere…

Mostly it became more of a focus of my error_log obsession when I switched the primary domain from shadowshift.com to hashbang.xyz and more search engine links were incorrect, going to generic error pages, not pointing back to a screen users could just click on home or whatever to start again… Both my 3.9.1 MultiSites and my one 4.0 Alpha MultiSite exhibit this behavior.

I haven’t really taken the time yet to understand the RewriteRule programming and I haven’t noticed ill effects of commenting the line out (yet!) so I’m hoping someone can point me in right direction first.

# RewriteRule ^(.*\.php)$ $1 [L]

That is were I got it. Somehow I missed a \ in the line above in my original posts here but the \ is in my .htaccess, here is where I got it:

https://hashbang.xyz/wp-content/uploads/2014/06/settings.png

Hi, what settings?

Just to be clearer, it is with any non-existent php file base domain, subdomains and mapped domains. This is what I would expect to happen:

https://www.ads-software.com/support/forum/non-existent.php

This is what happens with recommended .htaccess:

https://dev.hashbang.xyz/support/forum/non-existent.php

This is what happens with line commented out # RewriteRule ^(.*\.php)$ $1 [L]

https://hashbang.xyz/support/forum/non-existent.php

Not really sure why the php files need a RewriteRule? Or what the disadvantage of commenting it out would be. Seems like it must be there for some reason ??

Never mind, turned out the plugin was not installed on an update I did…

RC4 fixed it up perfect! Thanks Jose – You Rock!

RC4 fixed it up perfect! Thanks Jose – You Rock!

Jose,
Pinpointed it a little more, installed RC2 and its broken there. RC1 working, RC2 & RC3 not working.
Thanks!

Jose,
As per email, all things equal, upgrading from RC1 to RC3 broke it. I’m guessing that some change after RC1 is the culprit. I’m you want access to the VM let me know in email. I’m rather partial to the combination of WangGuard and Login Security solution compared to WordFence and you are the greatest so I’ll be happy to help any way I can.
Thanks!

Jose,
That’s not it, it’s uninstalled for now but I have a development and test VM woohoo.shadowshift.com which has RC1 on it and Login Security Solution and it works fine interestingly enough. Thinking I will upgrade it to RC3 and see if that breaks it. I can also give you access if that would help diagnose it.
Thanks!

FYI removing Login Security Solution didn’t change the situation, the questions still don’t show and [email protected] doesn’t block (I changed the previous entries in MySQL so you can reuse the email…) Dang, WangGuard is my #1 favorite plugin too ??

I did start using Login Security Solution a few weeks ago, originally I was thinking that would affect the Login page and WangGuard would affect the registration page, faulty thinking huh?

FYI the cron job seems to clean the sploggers out fine, I started running that frequently; they just manage to get in which surprised me because they never did that before…

Aha! Can I drop that table then? Or any other tables? shadowshift.com

Ok José fixed me up, I needed to install php-mbstring.x86_64 and it is working now. Seriously great plug-in and extraordinary support (and I work for a software developer support team, I do not say that lightly)

Thanks José You Rock!