WordPress.org

Ready to get started?Download WordPress

Forums

Custom Content Type Manager
[resolved] Since update to WP3.5 archive.php isn't used anymore (6 posts)

  1. ToTac
    Member
    Posted 1 year ago #

    Hey, just wanted to tell you this.

    Since I auto-updated WordPress to version 3.5 the archive.php seems to be ignored by my WordPress. Instead the content is displayed on the archive-CUSTOM-POST-TYPE1.php of a custom post type (which I created with CCTM of course).

    When I deactivate CCTM, WP uses the archive.php like usual.

    In short:

    CCTM is activated

    • WP uses archive-CUSTOM-POST-TYPE1.php for all posts, tags, categories, etc. that don't have an own archive-template.
    • Custom Post Type 2 is wrongly displayed on archive-CUSTOM-POST-TYPE1.php
    • Tag 1 is wrongly displayed on archive-CUSTOM-POST-TYPE1.php
    • BUT
      Category 1 is still correctly displayed on category-category1.php

    CCTM is deactivated

    • WP uses archive.php like usual

    Before the update things seemed to work fine.
    Any ideas what could be the problem or should I just wait for the next update of CCTM ? :)

    http://wordpress.org/extend/plugins/custom-content-type-manager/

  2. fireproofsocks
    Member
    Plugin Author

    Posted 1 year ago #

    Thanks for the note. I'm not sure if this is just WP's crazy and inefficient template system or if it something that needs to be addressed in the next release of the CCTM

    Can you clarify what you mean by "Custom Post Type 2 is wrongly displayed on archive-CUSTOM-POST-TYPE1.php" ? I don't follow you -- if you can write steps to reproduce the issue in the bug-tracker, then I can look at it. I'm not clear on what the problem is based on your description (sorry).

  3. ToTac
    Member
    Posted 1 year ago #

    Hey, first of all I want to thank you for your reply :)

    I think I will have to correct myself here.

    It seems I can not reproduce the problem by using a fresh WP installation (either 3.5 from beginning OR update from 3.4.2 to 3.5) and a WP standard theme.

    So I assume it has something to do with my custom built theme (which is a rig rag indeed). I cant say it more accurately right now but I will inform you when I have found a solution.

    In case somebody can help me with this by chance I will describe it again ->
    - - - - - - - - - - - -

    • I have a fresh WP 3.5 installation or updated from 3.4.2 to 3.5
    • I am using my own self made theme
    • I install the most recent version of CCTM
    • I create a Custom Post Type "Fruits" (+ archive-fruits.php) and enable nearly all options (including "Enable Archives")
    • I create a Category "Pagenews" (WITHOUT a special category-pagenews.php)

    When I call "www.mypage.com/fruits/" (for example) the fruits-posts are being displayed using archive-fruits.php.

    So far so good.

    But when I call "www.mypage.com/category/pagenews/" the posts of the pagenews-category are being displayed using "archive-fruits.php" as well and not using the "archive.php" (or category.php if there was one).

    Basicly this is my problem.

    I have tried the following:

    • deleting all archive-templates except archive.php results in a normal behaviour (archive.php is used for displaying categories, tags, custom-post-types, etc.)
    • changing my self-made theme to a standard WP theme results in a normal behaviour
    • playing around with various options of CCTM doesn't help

    Thanks a lot for any suggestion.

  4. fireproofsocks
    Member
    Plugin Author

    Posted 1 year ago #

    Yikes... that sounds like a pain. This is why I lobby against WP's template system: it takes a lot of patience and knowhow to figure out which files are used to render any given request. I'm not sure I can offer much guidance other than to look at the WP Template Hierarchy diagram (link?) and watch your .htaccess files and any plugins or themes that offer to customize URLs or links.

  5. ToTac
    Member
    Posted 1 year ago #

    Hey, just wanted to throw this in..

    Since I updated WordPress to the new version 3.5.1, this issue seems to have resolved itself, so I guess this behaviour was a WordPress bug all along and not a bug of CCTM.

    This seems to be the related bugticket.

    I am very glad this is over now :)

  6. ToTac
    Member
    Posted 1 year ago #

    Oh and -> RESOLVED

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic