I created a single-line text custom field for assets, which I expected would appear in the "Edit Asset" page, but it's not there. Where is it? Unless I'm missing something... is this a bug?
I created it within a website, and as I couldn't see it, I created another one for the whole system and, still, nothing.
I use MT Pro 5.12.
Reported on Movable Type 5
Hi,
It looks like this is a bug!
You may like to file a bug report for it from:
http://bugs.movabletype.org/
If you don't have time for it, let me know and I will do it on your behalf.
Kind Regards,
Mihai Bocsaru
----------------------------------
Daily Movable Type Consultant
Web Development
Movable Type Consulting
Six Apart Partner
http://www.pro-it-service.com/
----------------------------------
Movable Type Demo
http://www.movabletypedemo.org/
Hi, Mihai.
I see you already submitted a bug report. Thanks for that, and for the fast response. Let's hope this is a quick fix.
Hello to you,
You're welcome!
I've finally creating it, thinking that you might be busy.
Will keep you posted on this!
Thanks,
Mihai
Android and Mihai:
Anytime you are dealing with Custom Fields or anything that has to do with metadata in Movable Type, it might be helpful to for the development team to know if the problem is occurring in a brand new Movable Type instance or if the database being used has been upgraded from previous versions of Movable Type.
It also might be helpful to know if you created and deleted Custom Fields within the Movable Type database and subsequently created other Custom Fields.
There were problems with the integrity of metadata in these situations in Movable Type 4.3x. See the following pages of documentation:
http://www.movabletype.org/documentation/appendices/release-notes/432.html#102303-deleted-customfield-prevents-other-cf-from-being-saved
https://movabletype.fogbugz.com/default.asp?102303
I saw two forum entries that may be related to these problems today alone.
--Dave Aiello
Hi Dave,
I'm always aware of that!
This issue is a bug on movable type v5.12 and I've been able to reproduce it on a fresh installation running v5.12 pro.
Kind Regards,
Mihai Bocsaru
I see the problem now (an answer from the bug report). 'Asset' does not refer to all asset types. I failed to understand this, though I hope this clears any future misunderstandings.
Thanks, and sorry!
You're welcome!
So my conclusion is that they've started to brake the assets by type, that's why we could see there images, audio, video and for any other file types "assets".
We didn't see that custom field because we were looking for a type of asset that is now handled individually (image, audio, video).