• Resolved gpeery

    (@gpeery)


    I created a pod, and then went to add fields. When I go to save the pod after adding fields, I get this message:

    Error: name is reserved for internal WordPress or Pods usage, please try a different name. Also consider what WordPress and Pods provide you built-in

    I have tried this several times. The individual fields seem to create just fine – just when trying to save at the end.

    Thanks for your anticipated advice.

    Gordon Peery

    https://www.ads-software.com/extend/plugins/pods/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Having the same exact issue. I do not have the “Also consider what WordPress and Pods provide you built-in” in my error message, but the rest is the same: “Error: role is reserved for internal WordPress or Pods usage, please try a different name”

    I have checked the database and all of the existing Pods for name conflicts and found none. Then, I tried with a bunch of ridiculous names with the same result.

    Used the extend post types for posts to add fields, and it disappears after clicking save.

    Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    There are certain fields that WordPress builds in, and some are available within Pods as specially mapped to their associated parts, like ‘thumbnail’, etc.

    Have you tried a different field name than ‘role’?

    I didn’t get that error btw. Think the problem is it’s not saving period.

    Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    @stacy I saw you posted on GitHub, I’ll reply there so I can ask you more specific questions about your issue, I’m not entirely sure it’s related to the original poster’s problem.

    https://github.com/pods-framework/pods/issues/1540

    Plugin Contributor Scott Kingsley Clark

    (@sc0ttkclark)

    @gpeery / @thomas: There’s a list of fields built into the WordPress objects that we restrict from adding directly into Pods itself here in the code:

    https://github.com/pods-framework/pods/blob/2.x/classes/PodsAPI.php#L624

    Further, you’ll find that there’s an ‘alias’ for some fields, so that you can access ‘post_title’ with ‘title’, etc. Any taxonomies you’ve got associated to the post type, like ‘category’, will also be added to the list of restricted field names.

    Let me know if you have any further questions.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Not able to save Fields’ is closed to new replies.