As far as i know you cannot rename wp-admin. Many themes and plugin uses wp-admin in path. So if you rename it then all your plugins and themes will be broken. If you don’t want your users to access wp-admin then restrict it using .htacess If anyone access your wp-admin url redirect them to other … Read more
Script debugging in WP The constant SCRIPT_DEBUG is used to switch between minified and not minified versions of JavaScript files. But there’s more. $file.js Check if you’re using CONCATENATE_SCRIPTS and COMPRESS_SCRIPTS as well. Both are only used by core admin per default, but I use it in my themes as well to check which bag … Read more
Are you able to see the login screen? When exactly do you get redirected? Try to go to http://yoursite.com/wp-login.php enter your user and password, and see if it works. If it works, the issue could be related to a plug-in.
Basic implementation: Create a page for the frontend (and optionally a template). Then add the following code to your functions.php: function login_redirect_capability() { if ( current_user_can(‘author’) || current_user_can(‘editor’) ){ return ‘url-of your custom page’; } } add_filter(‘login_redirect’, ‘login_redirect_capability’); This will redirect them to the page you created. If you want to recode the dashboard as … Read more
A good idea might be to get a back up your old htaccess file and see if the issue still occurs. If it does, why not add the code from your existing file to the end of the wordpress file?
It could be that you’re missing the the body_class() in your theme: <body <?php body_class(); ?>> It should add the .custom-background as a body class: <body class=” … custom-background … ” >
rule of thumb, never do anything that results in DB write from the front end. Even better if you can create an admin page in which the operation is triggered (even if it just starts an AJAx based process). Your problem here is with hooking on an inappropriate hook. You hooked on init which means … Read more
What you can do is copy live DB, and deploy it to dev. Once you do that, start to disabling plugins one by one to see which one causes an error. If it doesn’t help – check where else you have code injections ( theme or drop-in or must use plugins). If it doesn’t help … Read more
OK, this is possible, but it will be a little bit tricky and I would recommend a lot of testing after deploying this solution. Disclaimer: I use base64_encode and base64_decode as cipher/decipher functions, but of course you can change them to whatever you like. First part (encoding before post is stored in DB) is pretty … Read more
Check for wp-config.php file. Find these two lines to your wp-config.php, and make sure “example.com” is the correct location of your site. define(‘WP_HOME’,’http://example.com’); define(‘WP_SITEURL’,’http://example.com’); Also on the database, check for table wp_options, check these two option_name; siteurl and home.