Turns out I wasn’t as thorough as I thought in removing vestiges of the hack. Found some more obfuscated PHP in template files, along with some .php files I didn’t have permissions for that shouldn’t have been there. Removed all that, and admin functionality is back to normal.
Have you installed a firewall plugin? Your IP seems to be blocked. I suggest you to turn your modem off and on again to obtain new IP and try login WordPress again.
Ok, found it. Not really WordPress related but might be helpful to someone anyway. It was my browser ad blocker plugin. Apparently it adds CSS to pages upon loading. The CSS showed as “inline” in the dev tools inspector but didn’t show at all when viewing page source code. When checking the CSS of the … Read more
Instead of this: return array( ‘index.php’, // Dashboard ‘separator1’, // –Space– ‘edit.php?post_type=page’, // Pages ‘edit.php’, // Posts ‘edit.php?post_type=portfolio’, // Portfolio ‘admin.php?page=wpcf7’, // Contact Form 7 ‘upload.php’, // Media ‘edit-comments.php’, // Comments ); try this: return array( ‘index.php’, // Dashboard ‘separator1’, // –Space– ‘edit.php?post_type=page’, // Pages ‘edit.php’, // Posts ‘portfolio’, // Portfolio ‘wpcf7’, // Contact Form … Read more
HTTP ERROR 500 either with your apache server or there’s something wrong with your php codes. My guess is a wordpress plugin or two is not compatible with the upgrades. Making one or more incompatibility is bad news to php. Do this: Go access your site’s files via SFTP. It could be file zilla or … Read more
So you do not know the url what you changed? If so, then follow these steps Go to the phpmyadmin go to the options table search for this option_name siteurl then you can know what you changed then using that url you can login then change it back
It should be add_action not do_action. And if it still doesn’t work, that means, your form processing code is being triggered after WP fires admin_notices hook.
to answer your question yes without the user table no one will be able to login because the database holds no login information. you may of been better off securing your /wp-login from brute fore attacks in a different way https://wordpress.org/support/article/brute-force-attacks/ i.e limiting the ip access to the login area
You can handle the wp_taxonomies object during init action. Then you can change the default labels for the categories and posts tags. function wpse292282_rename_default_taxonomies() { global $wp_taxonomies; // Update datas for Category $labels = &$wp_taxonomies[‘category’]->labels; $labels->name=”Sector”; $labels->singular_name=”Sector”; $labels->add_new = ‘Add Sector’; $labels->add_new_item = ‘Add Sector’; $labels->edit_item = ‘Edit Sector’; $labels->new_item = ‘Sector’; $labels->view_item = ‘View … Read more
You can simply check each of user meta details to see if they are blank or not. The code below is yours with with a check for first and last name. function wpse_user_welcome_notice() { // Make sure that the user is assigned to the subscriber role, specifically. $user = wp_get_current_user(); if ( !in_array( ‘subscriber’, $user->roles … Read more