IMPORTANT! A security vulnerability was discovered in older versions of TML that could allow users with posting privileges to exploit your site/server. This could possibly include exposing system and/or sensitive files such as /etc/passwd or /etc/shadow. If you run a single user blog, you’re okay. If you run a multi-user blog and you trust all of your authors/contributors/etc, you’re probably okay. However, if you run a multi-user blog with random authors/contributors/etc, you may have reason to be concerned.
Theme My Login 6.3.10 has been released to address this issue. That is, in fact, this release’s only purpose – and it is a very important one! So, upgrade immediately!
Theme My Login 6.3.10
- Fix potential local file include vulnerability in templating system
Theme My Login 6.3.9 fixes a few remaining outstanding issues in the 6.3 branch. First, a strict standards error when certain modules are active has been squashed. Also, a few deprecated functions have been replaced where necessary. Last but not least, it has officially been tested on WordPress 3.8.
Theme My Login 6.3.9
- Fix strict standards errors
- Replace deprecated functions
Theme My Login 6.3.8 addresses one simple issue — regular pages could potentially redirect to a user’s profile page with Themed Profiles active.
Theme My Login 6.3.8
- Fix issue where pages would redirect to profile page with Themed Profiles active
The biggest complaint with the 6.3 branch of Theme My Login was the change to the use of a custom post type for TML’s actions. This release reverts back to using WP’s native pages. A few other outstanding bugs are resolved in this release as well, including reCAPTCHA not working on multisite, user links not being able to be deleted and more.
Theme My Login 6.3.7
- Revert tml_page post type back to default WP pages
- Fix issue where SSL warnings were displayed in reCAPTCHA module
- Fix issue where a blank page resulted when 404.php didn’t exist in a theme
- Fix issue where User Links couldn’t be deleted
- Fix issue where “Are you sure?” would display when attempting to log out
- Fix issue where strings weren’t being translated on Profile page
Theme My Login 6.3.6 resolves more outstanding issues in the 6.3 branch. The main issues resolved in this revision are module settings all being on once activated, template tag not being output, installation failing during new blog creation on multisite and duplicate error messages on login pages.
Theme My Login 6.3.6
- Fix issue where all module options were set once activated
- Fix issue where template tag was not being output
- Fix issue where install failed during new blog creation on multisite
- Fix issue where error messages were duplicated on login pages
Theme My Login 6.3.5 fixes yet more issues uncovered with the under-tested 6.3 branch. Issues resolved include blank pages when a page.php template doesn’t exist, 404 errors on profile page when Themed Profiles is active, options being deleted upon upgrade and AJAX module not working properly in Internet Explorer.
- Fix issue with blank pages where page.php didn’t exists in a theme
- Fix issue where activating Themed Profiles resulted in a 404 for profile page
- Fix issue where options were being deleted upon upgrade
- Fix issue with AJAX module not working properly in Internet Explorer
Theme My Login 6.3.4 fixes one single issue with TML pages giving 404 errors. It simply adds a rewrite rule for each TML page.
Theme My Login 6.3.4
- Use verbose rewrite rules for TML pages
After correcting multiple issues from the 6.3 release, I firmly believe that 6.3.3 is ready to go! This bugfix release should resolve all of the issues encountered when previously upgrading to the 6.3 branch.
Theme My Login 6.3.3
- Fix issue where actions weren’t being appended to page links
- Fix issue where modules weren’t being installed on upgrade
- Fix fatal error in Custom E-mail module where old function name wasn’t replaced
- Fix private constructor issue for PHP versions less than 5.3
Another major issue has surfaced in the release of Theme My Login 6.3. Somehow, I just learned that plugin activation hooks are no longer called when plugins are upgraded. Therefore, none of the new settings or pages were being generated for users who were upgrading from previous versions. Version 6.3.2 fixes this issue.
Theme My Login 6.3.2
- Fix issue where pages weren’t created when upgrading from previous versions
Immediately after the upgrade to TML 6.3, I noticed a 404 error on multisite installs. I tracked the problem down to the use of “Post Name” as a permalink structure. Version 6.3.1 fixes this issue.
Theme My Login 6.3.1
- Fix multisite 404 error when using Post Name permalink structure
- Fix multisite redirect to main site for register