You can read this article and then get the po an mo files your need to translate wordpress in your language. You can put these files /wp-content/languages/. This should translate your login page too. EDIT: if you’re stuck with your issue you can hook some styles on login page and add some display none to … Read more
As said above modifying the core files is a bad idea, by doing so you are opening up security holes and on top of all this you loose the changes made on up-gradation. To do the above you can try the wp_login hook, put the codes in your active theme’s functions.php function after_login() { $current_user … Read more
Well actually I am not sure if it’s the best way to go, but you could just combine what you are already doing into two steps. Have the form submit without the _parent target so that it stays in fancybox. But if login is a success, then use that auto-closing behavior that you mentioned by … Read more
You could use authenticate filter for that. Below you can see how it’s called: $user = apply_filters(‘authenticate’, null, $username, $password); So if you write your own filter which will select user only based on login/username, then it should work (maybe some other minor tweaks would be necessary). PS. But I don’t think you should do … Read more
Try the Jetpack Comments system, included in the Jetpack plugin. http://jetpack.me/support/comments/
Just wanted to add my own experience to this thread. I’ve tried many different configurations of WordPress cookie constants in wp-config without any luck. I’m setup in the same way as described by the OP using custom_user_table and meta_table. I’ve found the session information does actually translate across different pages if you use COOKIE_DOMAIN as … Read more
It is possible that the home url for your site is being overridden in your wp-config.php file, I would make sure the missing colon isn’t originating from there.
There’s a “Membership” setting under Settings > General. By disabling “Anyone can register” the public-facing registration page will be effectively removed, along with the ‘register’ button. The API, however, will still be usable (e.g. wp_create_user().) On a side note, you mention NOTE: I’m working in a plugin already, so I cannot just use another plugin … Read more
I would approach the situation like: Create an user with subscriber role. Add a meta field to the user profile. This will be the password like field you will verify the user against. Use AJAX to verify the password(meta value) entered by the visitor and display product specification accordingly. You do not have to worry … Read more
You can edit and run the below SQL query in your database. Make sure there are no users with the existing ID you specify. If there are change all instances in all 3 tables, currently set to 4 to another number that does not yet exist. INSERT INTO `databasename`.`wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, … Read more