Skip Navigation

[Resolved] Taxonomies Not Displaying, Still in Database

This support ticket is created 3 years, 4 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 8 replies, has 3 voices.

Last updated by nadineH 3 years, 3 months ago.

Assisted by: Waqar.

Author
Posts
#2480171

We had custom taxonomies on our site that are no longer displaying in the backend and the frontend page urls are showing 404 errors. The taxonomies are still in the database and I cannot recreate them because the system says they already exist.

#2480475

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

That is really strange. Can you please specify what taxonomy you created and it was attached to what post type?

Have you performed any actions or installed any new plugins?

I will require admin access details and problem URL to review your current setup and check whats going wrong with your setup.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

#2483821

Hi,

Thank you for sharing the admin access details.

Minesh is on vacation so I'll be following up on this ticket.

While I can see the issue on your website, I couldn't reproduce this on my test website. On my test website, I deleted an existing taxonomy and then registered it again without any difficulty. The existing terms were recognized correctly, too.

This suggests that something specific to your website is involved. Do I have your permission to download a clone/snapshot of your website? This will help in investigating this on a different server, in more depth.

regards,
Waqar

#2483987

Yes you can download a snapshot, the website you have access to is also a staging site not the live version.

#2484577

Thank you for the permission and I've downloaded the website's clone.

I'll be performing some tests on this clone and will share the findings, as soon as this testing completes.

Thank you for your patience.

#2486575

Just wanted to let you know that I'm still working on this and will share the findings, as soon as I can.

#2487909

Thank you for checking into this further, have you found the cause of the issue or do you need any further questions answered?

#2488827

Thank you for waiting, while performed some troubleshooting on your website's clone.

By default Toolset Types stores the information about the custom taxonomies in the options table with the key 'wpcf-custom-taxonomies'.

But, on your website, the record of this option wasn't saved correctly. I was able to fix this on your website's clone using the following steps, which you can also use on your actual website:

1. Please add the following code in the active theme's "functions.php" file, to delete that record for the 'wpcf-custom-taxonomies' option:


delete_option( 'wpcf-custom-taxonomies' );

2. Next, visit the website's homepage a couple of times (so that the code gets executed). After that, remove the code added in step 1.

3. Now, register the custom taxonomy with the slug "procedure" again and it will be added and the existing terms for this taxonomy will also be restored.
( screenshot: hidden link )

I hope this helps and please let me know if you need any further assistance with this.

#2488879

My issue is resolved now. Thank you!