Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    I would reach out to Enfold theme support, since it is their product that got updated and would be having the most forward facing effect on these pages. We don’t personally integrate into theme output at all with CPTUI, we simply make sure that the post types and taxonomies are registered so that they’re ready to be integrated.

    If I had to guess on actual issue, it’d probably be on some mangled HTML output with this new version of Enfold, somehow.

    Thread Starter alauer

    (@alauer)

    Hello Michael
    yes, i already posted something in their forum.

    Would you mind help me to understand so i can search on my own?
    “mangled HTML”….you mean something connected with merged files and comprimation?

    What makes me wonder is that the issue only happens on pages that are created with CPT and if i copy the code and use it on a “normal” page or post it doesnt.
    Can you at least give an estimation how that could be so that i can understand how thats connected?

    We had some years ago an issue where we could not create any new posts with the custom taxanomy and you helped us by checking into WP-Admin and providing this code for our child themes functions.php:

    remove_action( 'init', 'cptui_create_custom_post_types', 10 );
    add_action( 'init', 'cptui_create_custom_post_types', 11 );

    Can this be a part of the problem?

    Thanks for helping
    Kind regards

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    What I meant by mangled HTML is that I was visiting the page in question and used the view-source functionality from Firefox to see the html markup. There were some spots that were highlighted in red, which means invalid markup in some way.

    Regarding the estimation part, it really depends on Enfold much more than CPTUI itself. We literally do not do anything in CPTUI’s code that would directly affect theme output.

    Regarding the code snippet above from the child functions.php, it’s worth removing temporarily just to see if it helps, but really all that’s doing as is, is making the post type register slightly later than it would be by default.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘CPT-pages crashed after Theme-Update’ is closed to new replies.