After experiencing issues with new registrants not receiving the custom welcome email I created via TML, I decided to give your latest dev version a spin to see if it would remedy the issue. Unfortunately, it didn’t seem to really function at all. Here’s the breakdown of my experience:
– Modules being used: Custom E-Mail, Custom Passwords, Custom Redirection, Custom User Links, Enabled Themed Profiles
– After installing and activating the plugin, I received this message: “The plugin generated 1 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.”
– All the new pages generated by the plugin—Log In, Log Out, etc.—came back as 404 error pages. None of them returned or displayed anything.
– In addition, the shortcodes and output codes no longer functioned.
In short, I didn’t have the best experience and have reverted back to version 6.3.2 for now. I love the new interface, it’s much cleaner and super user friendly, and can’t wait until this new version is up and running!
In the meantime, any ideas as to why the default WordPress new user email is going out instead of the custom TML one?
I’ve made a revision to it. Can you re-download and try again?
Also, which version of PHP are you on?
I was getting these errors on both the frontend and backend of the site after upgrading to 6.2.3:
Warning: reset() expects parameter 1 to be array, null given in /<path>/wp-content/plugins/theme-my-login/modules/themed-profiles/themed-profiles.php on line 230
Fatal error: Call to a member function get_page_permastruct() on a non-object in /<path>/wp-content/plugins/theme-my-login/includes/class-theme-my-login.php on line 491
Upgraded to 6.3.3 and the errors are gone and so far looks to be functioning as expected. Login/logout work. I’m also using Ultimate Branding by WPMUDev.org and all seems okay.
Aha!
I now have 6.3.3 working.
The problem was that it didn’t like my theme_my_login_custom.php file, which worked perfectly before. Commenting out the php in there makes everything suddenly work.
I had:
<?php
function tml_template_redirect() {
global $theme_my_login;
if ( $theme_my_login->is_login_page() ) {
if ( is_user_logged_in() && 'logout' != $theme_my_login->request_action ) {
$redirect_to = home_url();
wp_redirect( $redirect_to );
exit;
}
}
}
add_action( 'template_redirect', 'tml_template_redirect' );
?>
The 6.3 equivalent would be:
<?php
function tml_template_redirect() {
$theme_my_login = Theme_My_Login::get_object();
if ( $theme_my_login->is_tml_page() ) {
if ( is_user_logged_in() && 'logout' != $theme_my_login->request_action ) {
$redirect_to = home_url();
wp_redirect( $redirect_to );
exit;
}
}
}
add_action( 'template_redirect', 'tml_template_redirect' );
?>
Thanks for the fast response Jeff.
Now using 6.3.4 and everything is working perfectly – the new code in custom.php still doesn’t work, nothing crashes, but it just does not let you log out at all.
Will delete it for now, and have another look later.
Why not just use the Custom Redirection module for that anyway?
The updated version worked! For the most part anyway; the output codes still aren’t working but they’re not entirely necessary for this site.
My client is using version 3.3.10.4 of PHP, by the way.
Thanks again for all your help and hard work!
I hope you’re mistaken about that PHP version as that is a dinosaur.
Ha! I was mistaken. They’re using 5.2.17. I somehow grabbed the phpMyAdmin version instead.
Why not just use the Custom Redirection module for that anyway?
Good question, I don’t remember now, but there was definitely a reason when I set it up – will go with the custom redirection now.
I put the translations files (.po .mo) inside the plugins/theme-my-login/language folder but doesn’t work. Instead of that it display some of the wordpress translations in forms.
I am doing something wrong?
@eartboard: This is because it uses WP’s translations where avaialble.
Can i change this to use only the theme my login translations files?
In earlier versions it uses only the theme my login translations files.
Is it possible to have the same function in the latest version?
Thank you…
It is – by editing core plugin files and adding the “theme-my-login” domain to each gettext call.
