Support » Plugin: Change wp-admin login » Assistance with incorrect page name
Assistance with incorrect page name
-
One of my employees had installed the wp-admin change plugin and made the change, only thing is what he stated was the new page doesnt work, he thinks he may have mispelled it.
Is there anyway to fix this or remove the plugin without access to wordpress admin?
I obviously have full access to phpmyadmin and the file structure via CP file manager.
Thanks
-
ahh I see you bypassed the wp-admin
ok I am in. Thanks
Please leave a review on my plugin – the problem was not with my plugin was the extra code you had wrongly in your .htaccess
Now something is not right… when I login I get fed the
This page isn’t working
connectit.net redirected you too many times.
Try clearing your cookies.
ERR_TOO_MANY_REDIRECTSI am not blaming your plugin, I blame wordpress, as in all honestly nothing was done today with wordpress but your plugin added. so I guess I am screwed and will have to restore from an old backup.
Please clean your browser cache or use incognito from google
cleaned cache on Chrome, Firefox and Brave and tried tor …. also have tried incognito
something is wrongcan you past the .htaccess here again ?
site works fine.. I just cant get admin access
# BEGIN WordPress
# The directives (lines) betweenBEGIN WordPress
andEND 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
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule># END WordPress
# php — BEGIN cPanel-generated handler, do not edit
# Set the “ea-php72” package as the default “PHP” programming language.
<IfModule mime_module>
AddHandler application/x-httpd-ea-php72 .php .php7 .phtml
</IfModule>
# php — END cPanel-generated handler, do not editits breaking after loging in and being sent to /wp-admin/
The first thing I noticed is your using PHP version no longer supported (7.2) I strongly recommend your ask your hosting company to upgrade to 7.4 ASAP.
Your site was hacked via the WordPress File Manager plugin
WordPress File Manager plugin hacked:
https://www.wordfence.com/blog/2020/09/millions-of-sites-targeted-in-file-manager-vulnerability-attacks/The site is fixed and malware cleaned – wordfence plugin still scanning the website for more issues.
My plugin is installed. The login details are below.
https://connectit.net/site-
This reply was modified 4 months ago by
Nuno Sarmento.
The issue is now fixed. The problem was with WordPress File Manager plugin. The site was hacked. The user has restore an early backup.
I’ve deleted your offer to login to your user’s site. While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
- Ask the user to install the Health Check plugin and get the data that way.
- Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
- Ask the user to create and post a link to their
phpinfo();
output. - Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
- Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
- Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
-
This reply was modified 4 months ago by
- You must be logged in to reply to this topic.