taxonomy not saving

  • Resolved SRD75

    (@srd75)


    2 years, 10 months ago

    Hi. We’ve created a custom post type and an associated taxonomy.

    When editing a post in the CPT, we see the custom taxonomy. We can type in one of the taxonomy category names, but when we save the post, the taxonomy is not saved.

    We’re using a Beaver Builder theme.

    Help appreciated.

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

    (@tw2113)

    The BenchPresser

    Do you know how to access your browser’s developer tools? I’m curious if by chance there are javascript errors occurring that are preventing the taxonomy term from being saved to the post.

    Are you using the standard term metabox that WordPress core ships with? Or by chance is this a custom spot to add terms with, provided by Beaver Builder?

    Example of the standard term metabox that I’m referring to:

    https://cloudup.com/cd6nWjUw3ZQ

    Thread Starter SRD75

    (@srd75)

    I do see console errors on the block editor screen before any edits are made:

    View post on imgur.com

    Then when I add the taxonomy and press Enter, I see new console errors:
    (sorry about the large amount of code)

    VM612:1 GET https://attributestage.wpengine.com/wp-json/wp/v2/Integration%20Types?per_page=20&orderby=count&order=desc&_fields=id%2Cname%2Ccount&search=CRM&_locale=user 404
(anonymous) @ VM612:1
_ @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
f @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
b @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
a @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
b.method.r @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
a @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
t @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
y @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
P @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
fetchTerms @ editor.min.js?ver=208cadf8632b62c7ccdf2f2feb2398e2:7
searchTerms @ editor.min.js?ver=208cadf8632b62c7ccdf2f2feb2398e2:7
e @ lodash.min.js?ver=4.17.19:87
c @ lodash.min.js?ver=4.17.19:88
f @ lodash.min.js?ver=4.17.19:88
setTimeout (async)
Ws @ lodash.min.js?ver=4.17.19:116
f @ lodash.min.js?ver=4.17.19:88
setTimeout (async)
Ws @ lodash.min.js?ver=4.17.19:116
u @ lodash.min.js?ver=4.17.19:87
s @ lodash.min.js?ver=4.17.19:88
onInputChange @ components.min.js?ver=413e179f8a99bd28091ba5cc6f72c9f3:10
onChange @ components.min.js?ver=413e179f8a99bd28091ba5cc6f72c9f3:10
ki @ react-dom.min.js?ver=16.13.1:176
ji @ react-dom.min.js?ver=16.13.1:13
mi @ react-dom.min.js?ver=16.13.1:13
lf @ react-dom.min.js?ver=16.13.1:13
wi @ react-dom.min.js?ver=16.13.1:187
Kd @ react-dom.min.js?ver=16.13.1:32
pc @ react-dom.min.js?ver=16.13.1:32
Wf @ react-dom.min.js?ver=16.13.1:34
(anonymous) @ react-dom.min.js?ver=16.13.1:236
uf @ react-dom.min.js?ver=16.13.1:15
Qd @ react-dom.min.js?ver=16.13.1:42
sc @ react-dom.min.js?ver=16.13.1:41
unstable_runWithPriority @ react.min.js?ver=16.13.1:25
Da @ react-dom.min.js?ver=16.13.1:60
mk.Events.current @ react-dom.min.js?ver=16.13.1:236
Ei @ react-dom.min.js?ver=16.13.1:41
post.php:1 Uncaught (in promise) {code: 'rest_no_route', message: 'No route was found matching the URL and request method.', data: {…}}
Promise.then (async)
fetchTerms @ editor.min.js?ver=208cadf8632b62c7ccdf2f2feb2398e2:7
searchTerms @ editor.min.js?ver=208cadf8632b62c7ccdf2f2feb2398e2:7
e @ lodash.min.js?ver=4.17.19:87
c @ lodash.min.js?ver=4.17.19:88
f @ lodash.min.js?ver=4.17.19:88
setTimeout (async)
Ws @ lodash.min.js?ver=4.17.19:116
f @ lodash.min.js?ver=4.17.19:88
setTimeout (async)
Ws @ lodash.min.js?ver=4.17.19:116
u @ lodash.min.js?ver=4.17.19:87
s @ lodash.min.js?ver=4.17.19:88
onInputChange @ components.min.js?ver=413e179f8a99bd28091ba5cc6f72c9f3:10
onChange @ components.min.js?ver=413e179f8a99bd28091ba5cc6f72c9f3:10
ki @ react-dom.min.js?ver=16.13.1:176
ji @ react-dom.min.js?ver=16.13.1:13
mi @ react-dom.min.js?ver=16.13.1:13
lf @ react-dom.min.js?ver=16.13.1:13
wi @ react-dom.min.js?ver=16.13.1:187
Kd @ react-dom.min.js?ver=16.13.1:32
pc @ react-dom.min.js?ver=16.13.1:32
Wf @ react-dom.min.js?ver=16.13.1:34
(anonymous) @ react-dom.min.js?ver=16.13.1:236
uf @ react-dom.min.js?ver=16.13.1:15
Qd @ react-dom.min.js?ver=16.13.1:42
sc @ react-dom.min.js?ver=16.13.1:41
unstable_runWithPriority @ react.min.js?ver=16.13.1:25
Da @ react-dom.min.js?ver=16.13.1:60
mk.Events.current @ react-dom.min.js?ver=16.13.1:236
Ei @ react-dom.min.js?ver=16.13.1:41
VM612:1 POST https://attributestage.wpengine.com/wp-json/wp/v2/Integration%20Types?_locale=user 404
(anonymous) @ VM612:1
_ @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
f @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
b @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
a @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
b.method.r @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
a @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
t @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
y @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
(anonymous) @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
P @ api-fetch.min.js?ver=134e23b5f88ba06a093f9f92520a98df:2
findOrCreateTerm @ editor.min.js?ver=208cadf8632b62c7ccdf2f2feb2398e2:7
onChange @ editor.min.js?ver=208cadf8632b62c7ccdf2f2feb2398e2:7
addNewTokens @ components.min.js?ver=413e179f8a99bd28091ba5cc6f72c9f3:10
addNewToken @ components.min.js?ver=413e179f8a99bd28091ba5cc6f72c9f3:10
addCurrentToken @ components.min.js?ver=413e179f8a99bd28091ba5cc6f72c9f3:10
onKeyDown @ components.min.js?ver=413e179f8a99bd28091ba5cc6f72c9f3:10
ki @ react-dom.min.js?ver=16.13.1:176
ji @ react-dom.min.js?ver=16.13.1:13
mi @ react-dom.min.js?ver=16.13.1:13
lf @ react-dom.min.js?ver=16.13.1:13
wi @ react-dom.min.js?ver=16.13.1:187
Kd @ react-dom.min.js?ver=16.13.1:32
pc @ react-dom.min.js?ver=16.13.1:32
Wf @ react-dom.min.js?ver=16.13.1:34
(anonymous) @ react-dom.min.js?ver=16.13.1:236
uf @ react-dom.min.js?ver=16.13.1:15
Qd @ react-dom.min.js?ver=16.13.1:42
sc @ react-dom.min.js?ver=16.13.1:41
unstable_runWithPriority @ react.min.js?ver=16.13.1:25
Da @ react-dom.min.js?ver=16.13.1:60
mk.Events.current @ react-dom.min.js?ver=16.13.1:236
Ei @ react-dom.min.js?ver=16.13.1:41
Show 13 more frames
post.php:1 Uncaught (in promise) {code: 'rest_no_route', message: 'No route was found matching the URL and request method.', data: {…}}
    Thread Starter SRD75

    (@srd75)

    The CPT UI plugin is still active.

    What could be wrong, please?

    I have a similar problem… when I try to add a new Taxonomy entry in the taxonomy page (the equivalent to Posts –> Categories), it says “Sorry, you are not allowed to do that.”

    When I try to add a new Taxonomy entry in the custom post type, nothing happens when I create a new entry. It’s like the button does nothing.
    =======================
    Nevermind… found the problem. Although I had associated the custom taxonomy with the post type, you also have to edit the custom post type and select the supported taxonomy at the bottom. This made the custom taxonomy workable.

    • This reply was modified 2 years, 10 months ago by veedot2.
    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Looks like I missed your reply on this thread as well @srd75

    Just in case it helps, have you tried what @veedot2 found?

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    @veedot2 @srd75 either of you get this figured out in the end?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘taxonomy not saving’ is closed to new replies.