When one edit a default field on a custom content type, they are all treated as if they were date fields #87

Closed
peroyomas opened this Issue Jan 3, 2012 · 6 comments

Comments

Projects
None yet
2 participants
@peroyomas

When one edit any of the default fields on a custom content type, they are all treated (in the UI at least) as if they were 'date / time' fields, when is clear that some are text and author fields.

@ghost ghost assigned sc0ttkclark Jan 3, 2012

@sc0ttkclark

This comment has been minimized.

Show comment
Hide comment
@sc0ttkclark

sc0ttkclark Jan 3, 2012

Member

Which part of the UI? Can you provide a screenhot?

Member

sc0ttkclark commented Jan 3, 2012

Which part of the UI? Can you provide a screenhot?

@peroyomas

This comment has been minimized.

Show comment
Hide comment
@peroyomas

peroyomas Jan 3, 2012

@sc0ttkclark

This comment has been minimized.

Show comment
Hide comment
@sc0ttkclark

sc0ttkclark Jan 4, 2012

Member

Fixed in Alpha 4

Member

sc0ttkclark commented Jan 4, 2012

Fixed in Alpha 4

sc0ttkclark added a commit that referenced this issue Jan 4, 2012

@sc0ttkclark sc0ttkclark closed this Jan 4, 2012

@peroyomas

This comment has been minimized.

Show comment
Hide comment
@peroyomas

peroyomas Jan 4, 2012

Now, with new content types, the 2 default actual "date" fields are missing and the author field still displays as a "date" field. Even though the title and permalink fields display correctly, they displays as "date" fields again if one toggles the different "edit" buttons for a while.

Now, with new content types, the 2 default actual "date" fields are missing and the author field still displays as a "date" field. Even though the title and permalink fields display correctly, they displays as "date" fields again if one toggles the different "edit" buttons for a while.

@sc0ttkclark

This comment has been minimized.

Show comment
Hide comment
@sc0ttkclark

sc0ttkclark Jan 4, 2012

Member

You'll need to drop that pod from wp_pods and re-add it

Member

sc0ttkclark commented Jan 4, 2012

You'll need to drop that pod from wp_pods and re-add it

@peroyomas

This comment has been minimized.

Show comment
Hide comment
@peroyomas

peroyomas Jan 8, 2012

In the 5 alpha, the original bug appears again with newly created pods.

In the 5 alpha, the original bug appears again with newly created pods.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment