So I've upgrade one of our website to v4.7.1 and created an embedded content datatype. Problem is; it's not saving the Show in title and Required properties. I looked at another embedded content datatype and noticed the difference:
Wrong ||id:1|Name: Titel| Alias: title| Type: Textstring| Description: | Show in title? checked| Required? checked| Validation:||showLabel:1;maxCount:0;showType=1,showDescription=0,showTitle=0,showRequired=1,showValidation=0
Correct: ||id:1|Name: Title| Alias: Title| Type: Textstring| Description: | Show in title? true| Required? true| Validation: ||showLabel:1;maxCount:0;showType=1,showDescription=0,showTitle=0,showRequired=1,showValidation=0
So it's saving "checked" instead of "true". Tested in Firefox 7.0.1 and Chrome 14.0.835.202 m
Hi, could someone please elaborate more fully on what is involved in the "solution" of "editing the db table cmsDataTypePrevalues" in order to do this?
We made the mistake of falling in love with this plugin on a 4.7.0 development installation (before 4.7.1 was released), then when it came time to do a production client site installation (using 4.7.1) this week, we find it no longer works and now have to scramble at the last minute for a solution to this.
Is editing the database directly something we would need to do everytime we touch the ContentType? Is there a fix or better solution in the works? I am fine with temporary workarounds, just would like to know what exactly is involved and/or hoping a new release is coming out soon to fix this.
Thank you! (And P.S. I really do like this project, seems like it should be built-in to the Umbraco core when you want simple things and not necessarily tons of child nodes which can sometimes get confusing for a client...)
Sorry, I re-read my comment after I posted it and don't want to sound snarky or ungrateful or anything; we really do appreciate the hard work and finesse that went into this plugin, my frustration perhaps was more in how something in the core from 4.7.0 to 4.7.1 broke an existing plugin that we weren't able to figure out by looking at the Umbraco changelog and trying to patch ourself, but I know these things do always work themselves out... Thank you again!
You only have to do this when you want to change the embedded content datatype's prevalues/settings. Like adding, updating or removing a field. Open the table 'cmsDataTypePreValues' in edit mode and filter on id = <your datatype id>. The value column should look something like this:
||id:1|Name: Titel| Alias: title| Type: Textstring| Description: | Show in title? undefined| Required? checked| Validation:||showLabel:1;maxCount:0;showType=1,showDescription=0,showTitle=0,showRequired=1,showValidation=0
Notice the 'undefined' and 'checked' values for 'Show in title?' and 'Required?'. 'undefined' should be changed to 'false' and 'checked' should be changed to 'true'. That's it.
Show in title and Required not working
So I've upgrade one of our website to v4.7.1 and created an embedded content datatype.
Problem is; it's not saving the Show in title and Required properties.
I looked at another embedded content datatype and noticed the difference:
Wrong
||id:1|Name: Titel| Alias: title| Type: Textstring| Description: | Show in title? checked| Required? checked| Validation:||showLabel:1;maxCount:0;showType=1,showDescription=0,showTitle=0,showRequired=1,showValidation=0
Correct:
||id:1|Name: Title| Alias: Title| Type: Textstring| Description: | Show in title? true| Required? true| Validation: ||showLabel:1;maxCount:0;showType=1,showDescription=0,showTitle=0,showRequired=1,showValidation=0
So it's saving "checked" instead of "true". Tested in Firefox 7.0.1 and Chrome 14.0.835.202 m
I've also encountered the same issue. I would add that if required is not checked, then it's saved as undefined.
I have the same problem on 4.7.1. Is there a fix for this?
Jeroen
Only "solution" is editing the db table cmsDataTypePrevalues
Thanks that's good enough for now :)
Hi, could someone please elaborate more fully on what is involved in the "solution" of "editing the db table cmsDataTypePrevalues" in order to do this?
We made the mistake of falling in love with this plugin on a 4.7.0 development installation (before 4.7.1 was released), then when it came time to do a production client site installation (using 4.7.1) this week, we find it no longer works and now have to scramble at the last minute for a solution to this.
Is editing the database directly something we would need to do everytime we touch the ContentType? Is there a fix or better solution in the works? I am fine with temporary workarounds, just would like to know what exactly is involved and/or hoping a new release is coming out soon to fix this.
Thank you! (And P.S. I really do like this project, seems like it should be built-in to the Umbraco core when you want simple things and not necessarily tons of child nodes which can sometimes get confusing for a client...)
Sorry, I re-read my comment after I posted it and don't want to sound snarky or ungrateful or anything; we really do appreciate the hard work and finesse that went into this plugin, my frustration perhaps was more in how something in the core from 4.7.0 to 4.7.1 broke an existing plugin that we weren't able to figure out by looking at the Umbraco changelog and trying to patch ourself, but I know these things do always work themselves out... Thank you again!
No problem, I'll explain.
You only have to do this when you want to change the embedded content datatype's prevalues/settings. Like adding, updating or removing a field.
Open the table 'cmsDataTypePreValues' in edit mode and filter on id = <your datatype id>.
The value column should look something like this:
Notice the 'undefined' and 'checked' values for 'Show in title?' and 'Required?'.
'undefined' should be changed to 'false' and 'checked' should be changed to 'true'. That's it.
Thank you, I was able to manually modify the database row as you indicated and see that this is working again. Thank you!
I confirm this error exists in umbraco v4.7.1. I hope the developer can update this great package.
You can find a fix for it here: http://our.umbraco.org/projects/backoffice-extensions/embedded-content/bugs/25927-Using-it-for-1-minute,-already-2-bugs?p=2#comment96673.
Jeroen
is working on a reply...