Hi smmarketie,
I understand your concern about the website asking users for a login despite being set to public and not password-protected. It’s great that you’ve taken proactive steps like clearing the cache and updating pages.
Considering your situation, it’s advisable to check the .htaccess file for any rules that might inadvertently be affecting access. Follow these steps to address this.
- Review the content and remove suspicious code in .htaccess
- Before making any changes, create a backup of your current
.htaccessfile to ensure you can revert to the original state if needed. - Open the
.htaccessfile and look for any lines of code that might be restricting access. Focus on sections related to authentication or custom rules that could cause the login prompt. - If you find any suspicious code, comment it out or remove it. Commenting is safer for reference. For example:apache
# Example of commented-out line # RewriteRule ^restricted-page$ - [L] - Save the changes to the
.htaccessfile. - After editing the
.htaccessfile, clear your browser cache and any caching plugins or services you use. - Visit your website and check if the issue with prompting for login credentials is resolved.
If, after these steps, the problem persists or if you have any concerns, please let me know. I’m here to assist further.
Best regards,
Alexander
did you recently migrate your site from a development or staging environment?
have you contacted your webhosting vendor?
do you have any plugins that might be interfering?
Hi Lisa (@contentiskey). No I haven’t migrated the site. It’s new. I haven’t contacted the host company yet. How would I know a plugin is causing the issue?
Hi @smmarketie,
If you’re experiencing issues with your new site and suspect that a plugin might be causing the problem, here’s a quick way to identify the culprit:
- Use the Browser Console
- Open your website in a web browser.
- Right-click on the page and select “Inspect” or “Inspect Element” to open the browser’s developer tools.
- Go to the “Console” tab.
- Look for any error messages or warnings. A misbehaving plugin might trigger error messages in the console, helping you identify the issue.
- In your WordPress dashboard, go to the “Plugins” section.
- Deactivate all plugins at once.
- Check if the issue is resolved. If it is, reactivate each plugin one by one until the problem reoccurs. This way, you can identify the specific plugin causing the issue.
By using these methods, you can pinpoint if a plugin is causing the issue and take appropriate action, whether it’s reaching out to the plugin developer for support, finding an alternative plugin, or troubleshooting further.
If the problem persists or if you need more assistance, feel free to reach out.
Kind regards,
Alexander
Hi Alexander (@alextonio22), this is what it looks like. what do I fix?
- # SGS XMLRPC Disable Service
- <Files xmlrpc.php>
- order deny,allow
- deny from all
- </Files>
- # SGS XMLRPC Disable Service END
- # BEGIN WordPress
- # The directives (lines) between “BEGIN 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.
- <IfModule mod_rewrite.c>
- RewriteEngine On
- RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
- RewriteBase /
- RewriteRule ^index\.php$ – [L]
- RewriteCond %{REQUEST_FILENAME} !-f
- RewriteCond %{REQUEST_FILENAME} !-d
- RewriteRule . /index.php [L]
- </IfModule>
- # END WordPress
- # SGO Unset Vary
- Header unset Vary
- # SGO Unset Vary END
Alexander (@alextonio22) and lisa (@contentiskey)
I can’t check the plugins via the browsers because it is blocked from loading from the sign in pop-up.
check plugins using webhosting file manager area – not web browser.
have you been able to contact your webhosting support team?
