set up

Hi,
The message “cannot be written to your .htaccess” indicates that the plugin was unable to successfully write to the .htaccess file and verify that the rewrite rules were deployed and functioning correctly. If this message appears occasionally, yet the code is eventually written to the system, it may be due to your server’s configuration. Specifically, the server might use a core cache, which delays the processing of Apache rewrites by a few seconds. In that case you just have to hit again the interface Save button.

Regarding the login URL, if another code fails to work with the custom login, it might be relying on a hard-coded default (wp-admin) instead of dynamically retrieving the URL through a WordPress filter (e.g., admin_url). In such cases, there’s little that can be done from this side. You could try disabling the block on the default wp-admin temporarily or disabling the option until the other code is configured correctly.

When you mention “I set the response header,” are you referring to security headers? If so, these require a thorough understanding of each option, as well as the site’s structure and the services it uses. Automating this process is nearly impossible because misconfigured security headers can easily disrupt functionality. Instead, you can manually configure them by testing different options. Ensure you thoroughly check the front end to confirm everything continues to work as expected. Misconfigured headers can easily break the site.

Thanks

Hi,
I’m not sure i can follow what you meant “When setting the response header, there will be a htaccess prompt. After refreshing, there is no such prompt.”.
Changing the default plugins slugs is part of the hiding process. So use that along with the other plugin options.

Thanks