• Resolved fabik84

    (@fabik84)


    Hi There!

    I’m new to wordpress and pods. So please indulge me: After creating 6 custom taxonomies I always get an error, when I’m adding the correspondent relationship field for the seventh one. I always get the error message that the correspondent name “is reserved for internal purposes on WordPress or Pods. Please choose a different name”. I get the message in German directly in the modal view.

    I tried several names (8 at least) some of them are just gibberish that are certanily not reserved for any purpose whatsoever. I always get the same error. Could it be that there is a conflict with pods and Astra, the theme I use? Or do I have to change some Astra settings?

    I’m using the pods version 2.9.19 and for Astra I use Astra Pro Version 4.1.5 .

    I can reproduce the error.

    • This topic was modified 1 year, 4 months ago by fabik84.
    • This topic was modified 1 year, 4 months ago by fabik84.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Paul Clark

    (@pdclark)

    Sorry to hear you’re having this issue. Do either of these tools resolve it?

    • Pods Admin > Settings > Pods Settings > Clear Pods Cache
    • Pods Admin > Settings > Pods Tools > Repair Pod, Groups, and Fields

    If those don’t work it out, we would be best at finding a resolution if you could file a bug report on GitHub, including your Pods Package Export from Pods Admin > Components > Import/Export Packages. Once the issue is filed, it’s possible to comment on the issue with a file attachment, such as a .zip, if you’re finding the issue only occurs when using the Pro version of the theme.

    Thread Starter fabik84

    (@fabik84)

    Thank you for your help, Paul! I tried both tools but the issue persists. I will file a bug report on github.

    Thread Starter fabik84

    (@fabik84)

    Here is the correspondent bug report on github > https://github.com/pods-framework/pods/issues/7116

    Plugin Support Paul Clark

    (@pdclark)

    Okay, sorry about that, and thanks for taking the time to file an issue. With any luck, we’ll be able to find a resolution soon.

    This comment might be relevant —?the error message is supposed to appear if a taxonomy name has the same name as a field. I see you are adding taxonomies, but the error shouldn’t appear with a pseudo-random name, as you tested.

    This is the code block that is likely returning the error —?nothing seems out of the ordinary at first glance, but Scott may have more insight. It might also be this code block.

    This is the function that defines reserved keywords — one could hypothetically run an investigative test to remove all reserved keywords with <?php add_filter( 'pods_reserved_keywords', function() { return []; } );

    Plugin Support Paul Clark

    (@pdclark)

    Ah —?it looks like in your detailed steps on GitHub, you noted for the field in step 6: “add a name with the same name of the newly created taxonomy from step one”.

    This is the detail mentioned in the linked comment above: field names must be unique from taxonomy names, otherwise they conflict with each other. So append some unique identifier to the field name, such as _field, _relationship, or _rel if a core taxonomy has a similar name.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Error “Name reserved for internal purposes” shows up for every kind of name’ is closed to new replies.