I am having a dilemma. After getting WordPress installed and working with multi-sites. with site say named as test.com, I could not get to the same site using www.test.com. I realized after digging that www considered as subdomain. I talk to my DNS hosts company and they forwarded www.test.com –> test.com which solved the issue temporary. Now, when I moved to my own DNS server I’m facing the same problem again. I tried to do forwarding from httpd.conf or in .htaccess and I get to www.test.com but its the apache page. I tried to change the site name in the wp_options but once its change .. it goes to www.test.com which is again the apache welcome page. what ever I do I end up at apache page. of course if I leave every thing without www forwarding I can get to my main page fine. I hope one of you have a suggestion as run out of tricks. I do not mind doing forwarding using zone files if that is possible.. I’m using Fedora.

This file doesn’t exist and is generating the 404. If I deactivate the FA plugin, the style call and the error disappear.

Not sure why the plugin would be looking in the uploads folder for FA assets?

Debian/Apache system

We noticed a strange bug when working with WPML that we were able to reproduce in more that 1 sites.

Steps to reproduce:

1. Use W3 Total Cache and WPLM with Language URL format = Language name added as a parameter.
2. The user switches to a different language in the backend (via the adminbar option).
3. User clears the cache via the “Purge All Caches” option of w3tc (again from the abmin bar).

This is creating a wrong RewriteBase in the .htacess rules that are related the the page caching.

...
# BEGIN W3TC Page Cache core
<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase ?lang=el
    RewriteRule ^ - [E=W3TC_QUERY_STRING:%{QUERY_STRING}]
...
...

The RewriteBase line RewriteBase ?lang=el should be RewriteBase /

Thank you

We’ve activated the “Rename Login Page” security setting on our website to prevent access to the default WordPress login page.

However, we’ve noticed that it’s still possible to access the login page via wp-login despite this feature being enabled.

Does anyone know why this might be happening or if there’s an additional configuration step we need to take for this setting to work properly? Specifically, do I need to adjust anything in the .htaccess file to ensure the feature works as intended?

Thanks in advance for your help!

# END Newfold Browser Cache
odule mod_rewrite.c>
	RewriteEngine On
	[... etc.]
</IfModule>

Notice that the <IfModule> is chopped off at the front. This happened while I was editing the WordPress Settings –> Advanced “Page Setup” tab. I had entered a “Cart Page”, saved it, then did it a second time, this time leaving the “Cart page” blank. Boom – web site dead.

Today, there was an extra newline inserted into what should have been a comment, so it looked like this:

# END Newfold Browser Cache
WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.

Obviously the word “WordPress” isn’t a valid .htaccess command. This happened while I was editing settings in the WooCommerce PayPal plugin (sorry, can’t give you the exact sequence).

When .htaccess is corrupted, the nginx server won’t start at all, so not only is my web site down, but the wp-admin doesn’t work either. It’s a major bit of work to fix. I have to ssh to the web site, look through the error logs, and edit the .htaccess file by hand to get the web site back online.

WordPress is supposed to be for non-technical users. This bug (or bugs) is serious.

We are no longer able to display files as we are receiving a 403 error. As soon as we rename the .htaccess file in the dlm_uploads folder, everything works again. Our .htaccess file has always contained the recommended code (https://download-monitor.com/kb/htaccess-code/), we have not made any changes – what is the problem here and how can we fix it?

Best regards
Kay