Timezone Country and preferred locale - Data Springs Inc. - DotNetNuke Modules - DotNetNuke Module Product Forums - Product Discussion - DotNetNuke Modules

Timezone Country and preferred locale

Last Post 12-07-2008 02:32 PM by Chad Nash. 9 Replies.

Author

Messages

Marnix Bouwman User is Offline

river guide
Posts:82
Avatar

12-01-2008 11:08 PM
When exporting users from 1 portal, and trying to import them on another,it seems the module has problems with importing timezone, country and preferred locale. What can I do about this?

Marnix Bouwman User is Offline

river guide
Posts:82
Avatar

12-01-2008 11:12 PM
Also, when I look through this forum, I see a lot of point that still need to be improved if you are really serious about using this module.... And a lot of mentioning "we will add it to the next release", "we will consider it for the next release".... So release a new version then....

Marnix Bouwman User is Offline

river guide
Posts:82
Avatar

12-01-2008 11:14 PM
I'm not meaning to be rude or anything, I think the module has a lot of potential, and looks nice. But it misses some very important functions that are really, really necessary in a module like this.

Marnix Bouwman User is Offline

river guide
Posts:82
Avatar

12-01-2008 11:18 PM
I see now. when I look at the export something goes wrong, so this maybe a bug. The export looks like this: Username#Password#First Name#Last Name#DisplayName#e-mail#Country#TimeZone#PreferredLocale# But when you look at a row for a user it looks like this: usename#password#firstname#lastname#displayname#email###country#timezone#preferedlocale# So you see between email and country it adds two to many #'s

Marnix Bouwman User is Offline

river guide
Posts:82
Avatar

12-01-2008 11:24 PM
Right I did a replace on the output file (### to #) and tried to import again. Now it worked...

Marnix Bouwman User is Offline

river guide
Posts:82
Avatar

12-01-2008 11:27 PM
By the way, in step 1 you must enter a name for the import definition. I think it would be better if there would be a check so you can define a definition with the same name, or perhaps it should then overwrite the existing one. Now I've got two definitions with the same name, and there is no telling which is which.

Marnix Bouwman User is Offline

river guide
Posts:82
Avatar

12-01-2008 11:31 PM
Right now the only option is to add an import job to the scheduler. Perhaps you can add more control: - execute import now, or add to scheduler. - rollback of import - remove import from scheduler

Chad Nash

Posts:5260

12-03-2008 10:33 AM
These are a lot of threads in a 20 minute period! Ill check on the extra delimiter within the file, this is the first report that we have of this. This would happen if there were empty values for fields that were exported. If the field 'phone' was blank it would simply report it as ## instead of #555.1234# etc... Not sure if this is whats happening or not. Within the module menu you can go in and delete import definitions etc... You should also be able to delete pending scheduled imports there. Have you already reviewed this section? -Chad

Marnix Bouwman User is Offline

river guide
Posts:82
Avatar

12-04-2008 11:57 PM
Ok, didn't see the option in the menu module, thanks, that helps... Perhaps you can also make the import definitions editable in a future version.

Chad Nash

Posts:5260

12-07-2008 02:32 PM
Hi. Well actually they are something you can edit. You can check the box and select the import definition from the existing dropdownlist instead of creating a new import definition. -Chad