Skip Navigation

[Resolved] Custom Taxonomy functionality not working

This thread is resolved. Here is a description of the problem and solution.

Problem:

The issue here is that the user is unable to edit his custom taxonomy created in Types.

Solution:

Normally issues like these are caused by either a plugin/theme conflict or the server is using an outdated version of PHP.

First I would recommend that you temporarily disable all the non-toolset plugins and try again.

If that doesn't work please ensure that your server is running at least php 7

This support ticket is created 6 years, 8 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 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 6 replies, has 2 voices.

Last updated by Tim Elliott 6 years, 8 months ago.

Assisted by: Shane.

Author
Posts
#624907
taxonomy problem timehosting.jpg
taxonomy problem.jpg

I am trying to: Add a custom taxonomy

Link to a page where the issue can be seen: hidden link

I expected to see: It working normally

Instead, I got: The 2 boxes "Labels" and "Post types to be used with this Taxonomy" don't have anything in them (see screenshot taxonomy problem.jpg)
Even if I go to the Post type and try to add the taxonomy via the "Taxonomies to be used with CPT"

I have tried:
Deleting and reinstalling Types plugin.
Updating to the Beta version
I have replicated the problem on a different WP install on the same server.

I have tried to replicate the problem on a different server but the problem was NOT present when I tested on hidden link (see taxonomy problem timehosting.jpg)

I then tried using "All in one wp migration" to copy the ewf.timehosting.co.uk version over the dev-ewf-web.ambrosefox.com version. The Taxonomy was copied, along with it's relationship to the post type, but the problem still persists when you edit the taxonomy or add a new one.

I also saw this thread https://toolset.com/forums/topic/taxonomy-functionality-doesnt-work/ which seems similar. It was resolved by changing PHP version to 5.6 - but that is the version on the site where it doesn't work.

I can't give you FTP access at the moment as you're not whitelisted on the server. You can use the "WP File Manager" plugin to view files though.

I assume this is something server related - can you see what the problem is?

#624983

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Tim,

Thank you for contacting our support forum.

There might be something in the php logs that could point us to the exact issue.

Would you mind checking the logs and let me know.

Thanks,
Shane

#624984

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Activated private fields by accident, no need to provide credentials again.

#625366
#625679

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Tim,

This is definitely a server issue as you explained.

Could you update this server to php 7 and see if that helps.

Also Are there any differences in the servers that you are using such as php version, enabled php module etc.

Please let me know.
Thanks,
Shane

#626584

Hi Shane and thanks for your help.

The server is not mine, I'm using to build a site for a client so it's a little difficult for me to make the required changes. I'm working on it so if you can leave the ticket open for a little longer I'll see if I can make any progress.

#626664

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Tim,

This ticket will remain open.

If there are any issues please let me know.
Thanks,
Shane

#629064

Haven't fixed the problem but it's not a major problem right now. I think it's a server problem but can't identify it. I'll submit another ticket with more information if I feel like you can shed some light on it.