Viewing 14 replies - 16 through 29 (of 29 total)
  • 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.

    Thread Starter AC

    (@pixelmommy)

    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.

    Plugin Author Jeff Farthing

    (@jfarthing84)

    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.

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

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

    Thread Starter AC

    (@pixelmommy)

    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 ?? https://hellocuteness.com/a-page-for-jeff/

    It uses the default page template. No post content.

    Plugin Author Jeff Farthing

    (@jfarthing84)

    Can you reactivate TML 6.3.2 so I can see?

    Thread Starter AC

    (@pixelmommy)

    Ok, installed and activated – https://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.

    Plugin Author Jeff Farthing

    (@jfarthing84)

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

    Thread Starter AC

    (@pixelmommy)

    I activated Twenty Twelve on a test site (didn’t want to risk messing up my main site). This is the test site: https://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;}
    }’

    Plugin Author Jeff Farthing

    (@jfarthing84)

    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' ) )
    Thread Starter AC

    (@pixelmommy)

    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!

    Thread Starter AC

    (@pixelmommy)

    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.

    Plugin Author Jeff Farthing

    (@jfarthing84)

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

    Thread Starter AC

    (@pixelmommy)

    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.

Viewing 14 replies - 16 through 29 (of 29 total)
  • The topic ‘6.3.2 Upgrade, login page all messed up now’ is closed to new replies.