If /seba-online-form-fill-up-2018.html is an actual WordPress URL then this is relatively trivial to do in .htaccess. For example, the following one-liner using mod_rewrite could be used. This should be placed before the existing WordPress directives in .htaccess: RewriteRule ^\d{4}/\d{1,2}/(.+\.html)$ /$1 [R=302,L] This redirects a URL of the form /NNNN/NN/<anything>.html to /<anything>.html. Where N is a … Read more
Well localized the problem (without understanding it so far) It was not the .htaccess file. It was not plugins or themes (which I deactivated all to see what happens) But my little php app had their own session handling and modified the header. Just simple textbook stuff (login etc..) which works flawless outside WP. I … Read more
There are some things you can try: Check the wp-options table in your staging site database and look for site URL in 2 places. Change it to the correct staging address if already not. Refresh the permalinks of the staging site. I am guessing this should fix your problem. If not, please share your website … Read more
TL:DR: The slug of the home page and a folder at the root had the same name There was a folder that I was using for home page assets, the address was “example.net/home/” and the original WP development was “example.net/wordpress/”. When I moved the wordpress files out to the root, the home page had a … Read more
Providing you’ve already updated the internal links and that example.jp points to the same place on the filesystem as example.com (via CNAME and appropriate server config changes) then you don’t necessarily need to rewrite to example.com, since example.jp accesses the same files. Trying to rewrite to a different domain will implicitly trigger an external redirect … Read more
Forcing www to non-www is simple at the primary domain level. It’s actually the same for the subdomain (depending on how you’ve written the directives in the first place). If the hostname (main domain or subdmomain) starts with www. then remove it. (Forcing non-www to www for subdomains and main domains is a little more … Read more
RedirectMatch 301 ^/watermeloncakes/ //www.clienturl.com/watermelon-cakes-1/ (I assuming www.clienturl.com is the hostname for this site.) Well, here’s the thing… this would never have worked on any version of Apache!? Because protocol-relative URLs are not supported by mod_alias RedirectMatch (or Redirect) or mod_rewrite for that matter. From the Apache docs: The new URL may be either an absolute … Read more
RewriteCond %{HTTP_HOST} ^xxxz.com.qa [NC,OR] RewriteCond %{HTTP_HOST} ^www.xxxz.com.qa [NC] RewriteRule ^(.*)$ https://www.xxxz.com.qa/$1 [L,R=301,NC] This will result in a redirect loop as it will repeatedly redirect https://www.xxxz.com.qa/<url> to https://www.xxxz.com.qa/<url> again and again… If you want to redirect from HTTP then you need to check that the request was for HTTP before redirecting to HTTPS. For example: RewriteCond … Read more
I’ve had this issue on a small number of sites (out of around 60 that I help manage), and I’m wondering if the issue is caused by caching (by a plugin or theme). If you have a caching plugin, or a theme that does caching, there should be a tool in the Dashboard for emptying/clearing/deleting … Read more
After trying a million of ways, I contacted the super admin and asked for permission to log into WP Engine, our host. I found there is a Multisite setting too. So I clicked “convert to multisite”, and, bang! the error is resolved. Subsites can work properly now.