Can't change custom fields after upgrade?

I just read Igor's blog that you can't change custom fields after the upgrade!  Is that for everybody?  That seems rather major to me - to say the least.   How are people dealing with this?  It almost seems like they should "pull" the the upgrade for something like this.

Rob

I did not have any custom fields, so i can't test this. But i can add new fields, and no problem editing existing dolphin fields. So i don't know.

But it's to late to pull the upgrade. But they do need to get a fix out ASAP.

I think most people do have at least some custom fields.  This seems extremely major to me.   I waited a week this time just in case something like this happened, and was shocked to see that blog post this morning.  My upgrades are on hold until I know what is going on with this.

I tested with the update - 7.0.0 to 7.0.1 - and with a new installation of 7.0.1

change custom fields - and - add a new subcategory- it does not work

and many other bug - update - 7.0.0 to 7.0.1 - and - new installation of 7.0.1

add a new subcategory -  planned for version D.7.0.2

http://www.boonex.com/trac/dolphin/ticket/1997

change custom fields  -  nothing planned yet-

for me too - very important - I can not do anything without this function

I probably have to bite my tongue on this one, but this seems absolutely insane. People here will be upgrading to a non-working system.  The advice given on the blog announcing this that you should "make you profile field changes before you upgrade" is just absurd.   People are already asking if we will be able to upgrade from 7.0.0 directly to 7.0.2  - I would like to know that also.

I have quite a few custom fields, the fields transferred over okay, but the language keys did not (there are other missing standard language keys too).

Have not read the blog, but have now just tested to find that I cannot save the field if I modify it (complains of a duplicate).

Guess I can live with this for the time being as I don't really think that I need to change anything.

/DM

Now's the time to read "Database Management for Dummies."

Anton just showed me where the fix was in the trunk. Works perfectly to solve the custom field save ('duplicate error')

http://www.boonex.com/trac/dolphin/changeset/13972

Thanks again Anton!

i just happened to notice this problem yesterday when i tried to change a few custom fields, and they wouldn't save. i did a search in the forums and found the thread where someone said to add 0 to min value to field in advanced. that didn't work either. i just ended up deleting custom fields and added them again, making sure to put 0 in min value field to fix the mandatory issue. works fine now.

@Magnisoft - who was that "database for dummies" comment meant for-  Boonex or the people dealing with this bug?  Even before this, D7 was missing some important database functions, and now by upgrading you will essentially be breaking your system.  At the least, Boonex should update the D7.01 upgrade instructions to include applying that change set.  There are other fairly serious bugs though - things that worked in D7.0.0 that no longer work as people have identified here.   Because of the way this was done, many of us have a big messy job now.