You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under these circumstances it is not possible to save the input field, but it is still displayed. If you enable 'custom-fields' on the WP CPT (Custom Post Type) and change the value manually it'll work like a charm.
The problem itself lies within the camel case CPT ID, WordPress itself sanitizes the post type name before registering it.
Surely, I can sanitize the name on my own and therefor it's not directly a bug. Would love to hear your thoughts about it being a bug or maybe an enhancement.
Cheers,
Daniel
P.S.: Sorry for the title, but with it I'll try to make sure that someone's going to find help if he's trying to fix this in his project.
The text was updated successfully, but these errors were encountered:
Hey everyone,
first of all, great work you did with the Plugin! Even though I found some possible bug / enhancement. Consider this:
Under these circumstances it is not possible to save the input field, but it is still displayed. If you enable 'custom-fields' on the WP CPT (Custom Post Type) and change the value manually it'll work like a charm.
The problem itself lies within the camel case CPT ID, WordPress itself sanitizes the post type name before registering it.
Surely, I can sanitize the name on my own and therefor it's not directly a bug. Would love to hear your thoughts about it being a bug or maybe an enhancement.
Cheers,
Daniel
P.S.: Sorry for the title, but with it I'll try to make sure that someone's going to find help if he's trying to fix this in his project.
The text was updated successfully, but these errors were encountered: