WordPress.org

Ready to get started?Download WordPress

Forums

Theme My Login
[resolved] 6.3.2 Upgrade, login page all messed up now (30 posts)

  1. AC
    Member
    Posted 1 year ago #

    Hello,
    I just upgraded to version 6.3.2 and my login page (which was previously working fine) now has a bunch of unwanted extras on it. You can check it out here:

    http://hellocuteness.com/login/

    Basically, it's trying to pull content in as if it was a single-post page ... like the date tab, categories and the related posts content that is only shown on a single post page. Why is this happening?

    -AC

    http://wordpress.org/extend/plugins/theme-my-login/

  2. Fla0
    Member
    Posted 1 year ago #

    My guess the reason that is happening is there are no settings for the new default TML pages.

  3. AC
    Member
    Posted 1 year ago #

    Well... I reverted back to the older version and that actually BROKE my site. I had this error showing at the top of everything admin page:

    Warning: Invalid argument supplied for foreach() in /home/hellocut/public_html/wp-includes/post.php on line 3601

    Warning: Invalid argument supplied for foreach() in /home/hellocut/public_html/wp-includes/post.php on line 3601

    Yes, it showed twice. The entire admin interface was hosed. Everything was out of alignment, discolored, etc.

    On the front end, the "login" or "logout" links just took me to the root of my domain. http://hellocuteness.com.

    I had to deactivate.

  4. Jeff Farthing
    Member
    Plugin Author

    Posted 1 year ago #

    TML now has it's own post type, tml_page, which by default would use the single.php template. However, it is coded that they should still use the page template hierarchy.

    You can try copying your page.php template to single-tml_page.php.

  5. AC
    Member
    Posted 1 year ago #

    Hmm. So I guess I'm confused. None of my other "pages" show the date, categories or related posts content. How can I prevent this from showing on the TML login page? I'm using a custom Genesis child theme.

  6. AC
    Member
    Posted 1 year ago #

    Ah ok, I will try that! :p

  7. AC
    Member
    Posted 1 year ago #

    I copied the Genesis page.php into a new file and named it single-tml_page.php. I first uploaded this into my theme's default folder. No change. Then I tried to upload it into the plugin's templates folder. Still no change. From the TML tab in the dashboard, I now see a "pages" area, however, when you go to edit a TML page - there are no "Page Attributes", so no way to assign that template to the login page.

  8. Fla0
    Member
    Posted 1 year ago #

    Who is your host?

  9. AC
    Member
    Posted 1 year ago #

    My webhost? It's Hosting Matters, Inc.

    How is this related to my webhost? To me it appears that the missing functionality to assign a page template in the new custom post type that TML is using in this new version, is the issue.

    Am I thinking on the right track?

  10. Fla0
    Member
    Posted 1 year ago #

    Right. I only ask the question because most hosting control panels will allow you to revert your site to a previous date and restore TML with no issues.

  11. AC
    Member
    Posted 1 year ago #

    Oh :) I see. Yes, I can just upload my old copy of 6.2.3 for now. Right? However, this is probably going to be an issue for others too, the fact that others wouldn't want the content from single.php showing up on a login page! (Seriously, not trying to be a jerk - but why would you want the post date, categories and whatnot on a login PAGE?). Maybe the new custom post type can be coded to use page.php by default instead of single.php?

  12. Fla0
    Member
    Posted 1 year ago #

    You may have to delete the plugin altogether directly from the hosting panel, before you upload the old copy.

  13. AC
    Member
    Posted 1 year ago #

    Wow, this is strange! I deleted the entire TML plugin folder via FTP. However, I'm now trying to delete it from my own computer and it won't allow me to! User Account Control on my computer says I don't have permission to delete it and it's trying to access a Windows registry!

  14. nagad
    Member
    Posted 1 year ago #

    lol try to reboot

  15. Fla0
    Member
    Posted 1 year ago #

    Are you trying to delete the file from the FTP program? If so try deleting it right from the folder in your Hard Drive. Like in my case I use Dreamweaver but I can also delete directly from the folder in my c:drive.

  16. Jeff Farthing
    Member
    Plugin Author

    Posted 1 year ago #

    When you install a plugin via the WP admin panel, the files will be owned by the webserver. You'll need to change the permissions to manually delete them.

    Also, as I said above, it is coded to still use the page template hierarchy.

  17. Fla0
    Member
    Posted 1 year ago #

    I read her post to mean she could not delete from the computer itself. I delete plugins all the time with Dreamweaver that were installed directly from wp-admin without having to change permissions.

  18. AC
    Member
    Posted 1 year ago #

    Yes, I was trying to delete directly from the c:drive folder.

    I ran ccleaner and rebooted. I was able to delete it from my computer.

    Next, I reinstalled the old version 6.2.3. It gives the following error on all admin pages (with jacked up alignment, etc. - as stated before):

    Warning: Invalid argument supplied for foreach() in /home/hellocut/public_html/wp-includes/post.php on line 3601

    Jeff - I did what you said. I dropped the contents of page.php into single-tml_page.php. It did not work.

    What piece am I missing? Am I uploading the single-tml_page.php to the wrong area? Am I incorrect that there should be a way to assign the page template to the login page from the TML area in the dashboard?

    As it stands right now. I either have a broken 6.2.3 or a 6.3.2 that has post content on my login page.

  19. Jeff Farthing
    Member
    Plugin Author

    Posted 1 year ago #

    It should be using, in the most basic sense, page.php. Maybe your page template actually has all that stuff in it? Take a look.

  20. Fla0
    Member
    Posted 1 year ago #

    If you work with code at all check out this thread.

    http://stackoverflow.com/questions/2630013/invalid-argument-supplied-for-foreach

  21. AC
    Member
    Posted 1 year ago #

    Jeff, it's a Genesis theme. page.php calls the genesis function. But I know the page template does NOT have all of that stuff in it because I have plenty of other pages on my site that use the default page.php and they don't have post content. I also have quite a few custom pages, called the same way - no post content.

    Just created this page :) http://hellocuteness.com/a-page-for-jeff/

    It uses the default page template. No post content.

  22. Jeff Farthing
    Member
    Plugin Author

    Posted 1 year ago #

    Can you reactivate TML 6.3.2 so I can see?

  23. AC
    Member
    Posted 1 year ago #

    Ok, installed and activated - http://hellocuteness.com/login/

    BTW, I'm also using Mult-site.

    And coincidentally, I'm not sure how that login page knows to use the shop sidebar (vs. the default sidebar), because I now also don't see options to assign different sidebars to the TML login pages with this upgrade.

  24. Jeff Farthing
    Member
    Plugin Author

    Posted 1 year ago #

    Perhaps it's something with the theme you're using... Activate the default theme and see if the page template is used.

  25. AC
    Member
    Posted 1 year ago #

    I activated Twenty Twelve on a test site (didn't want to risk messing up my main site). This is the test site: http://mbc.hellocuteness.com/login/

    Ok... here's my findings:

    -- With the custom Genesis child theme - post content was there
    -- With just the default Genesis framework -- post content was NOT there
    -- With Twenty Twelve -- post content was NOT there

    So I realized that the 3 post items that are showing up on the login page when the custom child theme is activated (post date tab, post meta and related posts) are all called in through code that is in functions.php.

    My guess is, those 3 functions are missing something that isn't accounting for custom post types.

    Here's an example of one of the functions (this is for the post meta):

    '// CUSTOMIZE THE POST META FUNCTION
    add_filter( 'genesis_post_meta', 'post_meta_filter' );
    function post_meta_filter($post_meta) {if (!is_page()) {
    $post_meta = '[post_categories sep=", " before="→ Categories: "] [post_tags sep=", " before="| Tags: "]';
    return $post_meta;}
    }'

  26. Jeff Farthing
    Member
    Plugin Author

    Posted 1 year ago #

    And ! is_page() is true, since TML pages now have their own post type. So, change it to:

    if ( ! is_page() && ! is_singular( 'tml_page' ) )
  27. AC
    Member
    Posted 1 year ago #

    Thank you for that explanation! I was able to add the conditional statement to the related posts code & the date tab code in functions.php.

    I couldn't figure out the post meta though. I tried to add a conditional statement (to the code I listed above), but while it did remove the actual meta info, it left behind the CSS styled dotted border on the actual div output.

    So I added this function to remove the post meta from custom post types:

    // REMOVE THE POST META ON CUSTOM POST TYPES
    add_action('genesis_before', 'remove_cpt_meta');
    function remove_cpt_meta() {
     $post_type = get_query_var('post_type');
     if( !empty( $post_type ) && ( $post_type != 'post' ) ) {
     remove_action('genesis_after_post_content', 'genesis_post_meta');
     }
     }

    Not a pretty snippet, but it worked!

  28. AC
    Member
    Posted 1 year ago #

    Ugh. Login page looks great, but after all that... I go to login and I get the following error:

    Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

  29. Jeff Farthing
    Member
    Plugin Author

    Posted 1 year ago #

    If you haven't, try deactivating and reactivating the plugin. Otherwise, downgrade to 6.2.3.

  30. AC
    Member
    Posted 1 year ago #

    Good morning Jeff! Yes, I did downgrade. I had to delete the theme_my_login key from wp_options in phpMyAdmin. But at least I will be ready for the next version, when the custom post type comes! Thank you for your time spent helping me troubleshoot the original issue.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.