[SOLVED] Deleting, Editing, Removing "Values" from Fields

I have my Site set up so that people can enter tools of trade, e.g. Final Cut, Lightworks or Blender.

I found this here after a search of the forum.

www.joomlapolis.com/forum/7-community-builder-article-discussions/116935-removing-values-from-multivalued-field

Please advise if the following assumptions are correct?



Deleting:

Deleting "Values" from fields in the CB back end does not seem possible? Am I correct?



Editing:

I am guessing that if I change "LightWorks" to "Lightworks" any one who has selected "LightWorks" as a skill will no longer be searchable using the new value"Lightworks"

At some point I change the Value "Da Vinci" to the value "Resolve"
I still have people with "Da Vinci" on their profiles this is leading me to think that the above "LightWorks/Lightworks" e.g. will be the same!

Do I have to do all this kind of stuff in the phpAdmin interface?


Last but by no means least...

Removing:

What happens if I want to remove a "Value" from the selection process but want to leave it in the Users Profile.

e.g. a program is EOL and I do not want new Users entering it.

On the other hand I do not want to remove it from existing users profiles!!!

thanks

Paul

I found this here after a search of the forum.

www.joomlapolis.com/forum/7-community-bu...om-multivalued-field

I highly suggest ignoring any topic that's more than say 8 months old. Especially 3 year old topics. Our searching doesn't even search that far back by default.

Deleting "Values" from fields in the CB back end does not seem possible? Am I correct?

Not correct, edit the field in CB > Field Management and empty the value you want to remove then save your field.

I am guessing that if I change "LightWorks" to "Lightworks" any one who has selected "LightWorks" as a skill will no longer be searchable using the new value"Lightworks"

Correct, the value is the value and the label. We really need to separate value and label. I'm working on the next CB 1.x release and will see if I can get it implemented.

forge.joomlapolis.com/issues/4176

At some point I change the Value "Da Vinci" to the value "Resolve"
I still have people with "Da Vinci" on their profiles this is leading me to think that the above "LightWorks/Lightworks" e.g. will be the same!

Removing or changing a value does not remove or change the value stored to a users row. This is why we suggest using language strings so the value and the name display are pretty well separated. Example of this usage.

define( '_UE_MYFIELD_VAL1', 'This is value 1' );

In database it will store as "_UE_MYFIELD_VAL1", but on display it will show as "This is value 1".

Do I have to do all this kind of stuff in the phpAdmin interface?

To update user rows with the new values, yes unfortunately as you did not begin with using language strings.

What happens if I want to remove a "Value" from the selection process but want to leave it in the Users Profile.

e.g. a program is EOL and I do not want new Users entering it.

On the other hand I do not want to remove it from existing users profiles!!!

You basically can't. If you remove it, they save their profile, the value will be lost. It would be horribly bad design to keep values that do not exist on save as that'd cause a vulnerability.

"I highly suggest ignoring any topic that's more than say 8 months old. Especially 3 year old topics. Our searching doesn't even search that far back by default."

OK will do.

I tried this before posting but am getting the same result as before.










"Correct, the value is the value and the label. We really need to separate value and label. I'm working on the next CB 1.x release and will see if I can get it implemented."

Wow that is a serious limitation. My "Pro" subscription runs out in a couple of weeks I really hope that I can have access to this feature even if I do not update my subscription immediately. It would seem to me to be a "Must have rather than a "Nice to have."

"Removing or changing a value does not remove or change the value stored to a users row. This is why we suggest using language strings so the value and the name display are pretty well separated. Example of this usage.

define( '_UE_MYFIELD_VAL1', 'This is value 1' );

In database it will store as "_UE_MYFIELD_VAL1", but on display it will show as "This is value 1"."

Again Latin for me but what you are talking about is mentioned time and time again in the User manual so I will have to get my head around it sooner or later!!!

"To update user rows with the new values, yes unfortunately as you did not begin with using language strings."

So if I changed "LightWorks" to "Lightworks" using the phpAdmin interface that would ripple seamlessly through to the CB front End Profiles?

"You basically can't. If you remove it, they save their profile, the value will be lost. It would be horribly bad design to keep values that do not exist on save as that'd cause a vulnerability."

So worst case scenario I could remove values from the Data base and then from the selection process?

If I did every thing 1 on 1 it would be OK and nothing should break.

I remember I had one issue before where I somehow managed to save a profile with an empty filed where the field was actually required! And it screwed up the whole data base!!! the only way to repair it was to remove the Profile from the data base. That was fun. :woohoo:

Do you happen to have a link for me where I can learn more about "language strings"?

Resistance seems to be futile

Does it make sense to try to implement this for me what is Latin after the "Event"? i.e. " "language strings."???

I tried this before posting but am getting the same result as before.

You removed the first value. Move something up so it becomes the new first value. It only validates the first value to ensure at least 1 value is supplied.

Wow that is a serious limitation. My "Pro" subscription runs out in a couple of weeks I really hope that I can have access to this feature even if I do not update my subscription immediately. It would seem to me to be a "Must have rather than a "Nice to have."

Subscriptions have nothing to do with CB releases. CB releases have and will continue to be free for everyone as long as they're registered.

So if I changed "LightWorks" to "Lightworks" using the phpAdmin interface that would ripple seamlessly through to the CB front End Profiles?

Assuming you update each users database row, yes.

Do you happen to have a link for me where I can learn more about "language strings"?

Please see your CB documentation, which you can download from the Advanced downloads section. We also have some information on language usage below.

www.joomlapolis.com/cb-solutions/languages

Does it make sense to try to implement this for me what is Latin after the "Event"? i.e. " "language strings."???

Well if you do it now you're going to lose all your users field values as they won't match anymore unless you update every users database row with the correct values, which won't be easy as multi-selects store as Value1|*|Value2, etc.. so would require a little more complex SQL to update all the rows with the new values. I guess the alternative is leave it alone for now and wait for next release where hopefully I can get separation of Value and Label implemented.

You removed the first value. Move something up so it becomes the new first value. It only validates the first value to ensure at least 1 value is supplied.

Have done as instructed and it still does not work!













Have tried both "Save" and "Apply"

Even tried moving Adobe Premiere up to the Top as I know for a fact that the "Value" "Augmented reality is empty! i.e. no user entered Augmented Reality!

I was trying to remove the field "Abelton"

Subscriptions have nothing to do with CB releases. CB releases have and will continue to be free for everyone as long as they're registered.

Well I have been registered for 7 years now, so I will not be going any where fast

So if I changed "LightWorks" to "Lightworks" using the phpAdmin interface that would ripple seamlessly through to the CB front End Profiles?

Assuming you update each users database row, yes.

So I would have to update the "Value" in the database and then go to each users profiles and update the value again. In this case "LightWorks" becomes "Lightworks." It would not be a huge deal as I probabyl only have 10 people who use "Lightworks"

I believe that you mentioned in antohter of my threads that you wanted to address this issue in CB 1.9.1

I found this here:

forge.joomlapolis.com/versions/566

Any idea what might be a realistic release date. Like we are talking 2013 and not 2014? Just asking!

Please see your CB documentation, which you can download from the Advanced downloads section. We also have some information on language usage below.

thanks

Well if you do it now you're going to lose all your users field values as they won't match anymore unless you update every users database row with the correct values, which won't be easy as multi-selects store as Value1|*|Value2, etc.. so would require a little more complex SQL to update all the rows with the new values. I guess the alternative is leave it alone for now and wait for next release where hopefully I can get separation of Value and Label implemented.

I will probably take my chances and wait before doing hard Core myPHP Gymnastics.

From my innocent perspective this seems to be one of the more difficult aspects of CB :blink:

You need to move the value, edit out the value, then save. It should be working fine and I can't duplicate your issue otherwise.

So I would have to update the "Value" in the database and then go to each users profiles and update the value again. In this case "LightWorks" becomes "Lightworks." It would not be a huge deal as I probabyl only have 10 people who use "Lightworks"

Unfortunately, yes.

Any idea what might be a realistic release date. Like we are talking 2013 and not 2014? Just asking!

I don't use the time tracking on our forge so I've no idea why it even says 4 months late. I just started working on CB 1.9.1 like 2 weeks ago (now renamed CB 1.10.0). Should be done by end of next month and probably starting testing phases sooner than that.

From my innocent perspective this seems to be one of the more difficult aspects of CB

Issue will basically be gone entirely with next CB release as you'll be able to specify separate Value and Label. Below is how I have it implemented, and working, as is for next release.



Please when quoting my responses use quotes as it makes it very hard to read your posts.