Nice package. I have it on a usercontrol that sets member profile properties.
Should I be able to use this in the back office - or is there a way to create a back office control from the same data set so it behaves in the same way? Essentially I want the admins to be able to change the member's contry if they need to.
you can look at the razor code that creates the dropdown in the source code, and easily create something similar to that in your user control: a drop down that loop through dictionary items of countries names.
after you install my package, you can look at the new installed file here
\YourSite\macroScripts\CountriesDropdown.cshtml
also, make sure to take a loot at uComponents datatype callled "country picker".
Hey Eran thanks.. I would vote but cannot until I have 70 karma I'm afraid :-(
Hey I installed uComponents, created a datatype and set up a doctype property - but I go a "Culture not SUpported Exception" (site is using english and greek languages). Have you installed your package alongside uComponents OK? I am a bit stumped..
I posted the bug here but thought I would let you know in case you had anything similar happen:
OK Cheers. Just to be clear - are you useing the uComponents country picker with multiple languages? I read a post which suggested that uComponents does not support dictionary items as yet. That said, it would not bother me if it was only in English as I am only using the country picker datatype in the back office.
as a matter of fact i used uComponents country picker not on multi-language site, so i can tell you if its working with dictionaries. i think that its not.
but you know what - this is great feature to suggest them - to add multi-language by using dictionaries instead of hard coded country list. they can even take the dictionaries from my package!
Not sure what is causing the issue you're getting with uComponents Country Picker ... tried to reproduce it, but no luck.
uComponents Country Picker isn't using hard-coded values, nor dictionary items, the country list is generated from .NET's System.Globalization classes - which isn't the best, as it actually misses off some countries (e.g. Sudan). But still the list it comprehensive for most needs.
I do like the idea of a DictionaryItem DropDownList data-type ... surely it's been done before?! If not, it's absolutely a candidate for uComponents. Fancy developing it?
Had a look to see if there was an existing Dictionary data-type out there... then I found the Dictionary Picker that comes with Umbraco. It's not set-up as a data-type, but it's in the dropdown list of other render-controls.
As far as I can tell, if you enter the dictionary's key in the PrevalueEditor, then it "should" render out a CheckBoxList of all the child-dictionary items. But I couldn't get this to work properly... but it's a start!
Anyway, my offer is still open for uComponents - if you wanna develop one, we'll include it! :-)
@Lee I have got something basic going as a custom datatype (via the usercontrolwrapper) - but it works!
I could do with a pointer on how to create config/settings part though - i.e. when a user creates their datatype based on Dictionary Picker, they should get a dropdown to select the dictionary item to bind to.
Just to let anyone else know, this was not to do with the RV or uComponents packages in any way - a sample bit of code that loops through all the available cultures turned up an invalid culture on my system {tl-PH-Nokia} that seemed to have been installed with the Nokia PC Suite.
Finally tracked the bugger down in C:\Windows\Globalization\tl-PH-Nokia.nlp
After much uninstalling, registry hacking and hair-pulling, simply deleting this file fixed the issue. It may help someone else one day. Anyway thanks Lee for helping out - you rock!
Backoffic integration
Nice package. I have it on a usercontrol that sets member profile properties.
Should I be able to use this in the back office - or is there a way to create a back office control from the same data set so it behaves in the same way? Essentially I want the admins to be able to change the member's contry if they need to.
you can look at the razor code that creates the dropdown in the source code, and easily create something similar to that in your user control: a drop down that loop through dictionary items of countries names.
after you install my package, you can look at the new installed file here
\YourSite\macroScripts\CountriesDropdown.cshtml
also, make sure to take a loot at uComponents datatype callled "country picker".
http://our.umbraco.org/projects/backoffice-extensions/ucomponents
if you like the package please vote!
thanks,
Eran.
Hey Eran thanks.. I would vote but cannot until I have 70 karma I'm afraid :-(
Hey I installed uComponents, created a datatype and set up a doctype property - but I go a "Culture not SUpported Exception" (site is using english and greek languages). Have you installed your package alongside uComponents OK? I am a bit stumped..
I posted the bug here but thought I would let you know in case you had anything similar happen:
http://ucomponents.codeplex.com/discussions/263318
hi,
my package is not related to uComponents country picker in any way. anyway, i'm using my package along side with uComponents without any problem.
i didnt know this error that you are taking about. the best is to ask about it in uComponents forum:
http://our.umbraco.org/projects/backoffice-extensions/ucomponents/questionssuggestions
thanks,
Eran.
OK Cheers. Just to be clear - are you useing the uComponents country picker with multiple languages? I read a post which suggested that uComponents does not support dictionary items as yet. That said, it would not bother me if it was only in English as I am only using the country picker datatype in the back office.
as a matter of fact i used uComponents country picker not on multi-language site, so i can tell you if its working with dictionaries. i think that its not.
but you know what - this is great feature to suggest them - to add multi-language by using dictionaries instead of hard coded country list. they can even take the dictionaries from my package!
Yes indeed. Thanks Eran. I will suggest it, in the meantime I will make my own datatype for the backoffice based on your control.
Hi Barry,
Not sure what is causing the issue you're getting with uComponents Country Picker ... tried to reproduce it, but no luck.
uComponents Country Picker isn't using hard-coded values, nor dictionary items, the country list is generated from .NET's System.Globalization classes - which isn't the best, as it actually misses off some countries (e.g. Sudan). But still the list it comprehensive for most needs.
I do like the idea of a DictionaryItem DropDownList data-type ... surely it's been done before?! If not, it's absolutely a candidate for uComponents. Fancy developing it?
Cheers, Lee.
Had a look to see if there was an existing Dictionary data-type out there... then I found the Dictionary Picker that comes with Umbraco. It's not set-up as a data-type, but it's in the dropdown list of other render-controls.
As far as I can tell, if you enter the dictionary's key in the PrevalueEditor, then it "should" render out a CheckBoxList of all the child-dictionary items. But I couldn't get this to work properly... but it's a start!
Anyway, my offer is still open for uComponents - if you wanna develop one, we'll include it! :-)
Cheers, Lee.
Absolutely! I'm on it.
@Lee I have got something basic going as a custom datatype (via the usercontrolwrapper) - but it works!
I could do with a pointer on how to create config/settings part though - i.e. when a user creates their datatype based on Dictionary Picker, they should get a dropdown to select the dictionary item to bind to.
Just to let anyone else know, this was not to do with the RV or uComponents packages in any way - a sample bit of code that loops through all the available cultures turned up an invalid culture on my system {tl-PH-Nokia} that seemed to have been installed with the Nokia PC Suite.
Finally tracked the bugger down in C:\Windows\Globalization\tl-PH-Nokia.nlp
After much uninstalling, registry hacking and hair-pulling, simply deleting this file fixed the issue. It may help someone else one day. Anyway thanks Lee for helping out - you rock!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.