Sound like some configuration in your browser that keeps cookies only for a session specifically for you site. To make sure the problem is not on Wordress side, deactivate all your plugins and try again.
The problem is that you are enqueue the CSS file of your theme outside any of the recommended actions. If you want it to be added only in frontend, you should use wp_enqueue_scripts action: add_action( ‘wp_enqueue_scripts’, function() { wp_register_style( ‘mainstyle’, get_stylesheet_uri()); wp_enqueue_style( ‘mainstyle’, get_stylesheet_uri()); });
I solved the issue. If anyone else has this issue here is the solution. – It ended up being a Creative Cloud problem. – Open up the creative cloud click assests and navigate to fonts. – From there you can enable and disable fonts. – Disabled the Open Sans and it fixed all my dashboards.
This removes the ‘quick edit’ button from the page edit dashboard for all users who cannot edit theme options (usually admins). So, quick edit is no longer available for common editors, assuming there has been no messing with default capabilities. The two added filters are the same. One of them is probably meant to apply … Read more
Replace your code with as mentioned below: public function admin_body_class($classes) { global $wpdb, $post; $screen = get_current_screen(); $status=”parent-“; if( isset( $post->post_parent ) && $post->post_parent > 0 ) { $status=”child-“; } $classes .= ‘ ‘ . $status . $screen->post_type; return $classes; }
Even if you disable registration, if the server has WP-CLI installed and if someone has ssh access then an admin user can easily be created using following command: wp user create bob [email protected] –role=administrator Thus, that admin user can login and remove other user account easily. Check this to know about all the possibilities through … Read more
I do have the same problem when I am using Cloudflare SSL.Just make redirection to https for all pages using CloudFlare dashboard and then install Really Simple SSL and check only “Auto Replace mixed content”. Hope this may solve your problem. If else try deleting .htaccess file.
As stated in the announcement post: A few account security enhancements have gone into WordPress 4.9. The intention is to make it more difficult for an attacker to take over a user account or a site by changing the email address associated with the user or the site, and also to reduce the chance of … Read more
The /wp-admin/ajax.php file should not be locked – it is used to power all AJAX functionality on the site. Your robots.txt file specifically instructs search engine spiders (like Google) to allow access to /wp-admin/ajax.php: User-agent: * Disallow: /wp-admin/ Allow: /wp-admin/admin-ajax.php Sitemap: http://example.com/sitemap.xml Either remove the Allow: /wp-admin/admin-ajax.php and keep /wp-admin/ locked (effectively disabling all AJAX … Read more
Yes, lots of themes and plugins make use of the wp-admin/admin-ajax.php file, and some use wp-admin/admin-post.php. But beyond that there’s little to no reason to access wp-admin. Perhaps a search engine trying to determine if I’m running wordpress? Search engines don’t care so much if you are or aren’t using WordPress, you would be able … Read more