Support » Plugin: Beautiful taxonomy filters » Plugin crashed my website upon assigning it to a CPT

  • Resolved tydrain

    (@tydrain)


    Hi Dev,

    I was trying out some plugins and stumbled upon this one. I am using CPT UI + Beaver Builder and Beaver Builder Themer activated on my CPT page.

    I tried assigning the plugin to the custom post type, upon loading the page every CSS/HTML structure was gone and it loaded an archive page.

    Maybe something to look into in the future.

    Good luck!

    Max

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Jonathandejong

    (@jonathandejong)

    Hi @tydrain

    Unfortunately this is far too little information to be helpful 🙂
    Most likely the issue would be an incompatibility with beaver builder themer but I have no idea what.. BTF has a _Very_ minimal impact on the frontend or any logic really so how it could be the cause of something like that is beyond my guessing.

    In any case, thanks for the feedback. Should you want me to look into it properly I need more info 🙂

    Best of luck with your project!

    Hi,
    I noticed this post and have a similar issue.

    I installed the plugin and assigned it to a CPT (called FAQ, for frequently asked questions). Now when I go to my FAQs page, it shows the *archive* and not the actual page.

    Similarly, with other CPTs on the system for which I have *not* activated this plugin but if I click on any of the links to view the CPT it shows a 404 page instead.

    I’ve tried clearing permalinks, etc.. but that has had no effect. Archive pages and 404s are everywhere now.

    Any ideas how I can remove the effects that this plugin has had on my project?

    Plugin Author Jonathandejong

    (@jonathandejong)

    Hi @anthonyfletchers

    I believe your issue is not with BTF but rather that you’ve created pages with the same slug as your CPT slugs. That will cause random 404 issues!

    I want to make it superclear that the only thing BTF does is that it adds rewrite rules which extends the /cpt-slug permalink endpoint *only*. It does not do anything else at all to other operations etc.

    But to answer your question more clearly: make sure you do not have pages with the same slugs as your CPTs. Then refresh your permalinks and try again 🙂

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.