I have to say, I really like your plugin. Took a few years to find a plugin that smoothly integrates the login into the front-end...
Though, I've figured out two more things:
- I also use the plugin Sabre (anti-bot registration engine). - It works together with TML, but does not include username and e-mail address in its table when new users are registered. The reason is that TML does not use the original form field names (user_login instead of user_login-tml-main and user_email instead of user_email-tml-main). I adopted the code in Sabre to accept the input from these field names. - Do you think there is a chance that you could revert to the original WP field names?
- I use wp_register and wp_loginout in my sidebar (with redirects to the current page). - If I click on Lost Password or Register in the TML div and subsequently use the Log In link in the sidebar, TML will redirect me again to the Lost Password or Register page instead of showing up the Log In page. Only after a second click the registration page opens as intended. - I know, a minor thing, but I also wanted to provide you with feedback in that case.
From a performance/overhead point of view the loading time could also be reduced in case login_head would only be included on the /login/ page. I solved that by commenting out the code in your plugin and calling do_action in my login template. Maybe you could add a condition which restricts the wp_head > login_head calls to the /login/ page or serve it globally if the widget is enabled. An option like the css-include would also be awesome.
The work-around/patch to the XHTML bug I've mentioned before is so far two-folded:
- wp_register() -> use static link (no idea yet why it works with wp_loginout() and not with wp_register()
- class.wp-login.php, function GuessURL() add htmlentities(); so it becomes
$url = htmlentities(add_query_arg($args, $url))
Thanks again for your work! :)
Berny
