-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEBLOD Importer - 2 BUGs: solutions #29
Comments
I would say both are feature requests, not bugs. |
Hi Klas, 0 - Have you been able to replicate the issues ? If the answer is yes, then: 1 - SEBLOD by default come with its standards User Fields stored into #_cck_store_item_users (Padlock opened), Am I right ?
2 - When the User doesn't exist, it is created and a Registration email with Username and Password is sent. But the email is always sent in the Backend language. Thanks to all Seblod Team for the attention |
Hi guys,
PHP 7.1.9 + Joomla 3.8.0 + Seblod 3.14.1 + SEBLOD Importer 1.9.4:
Trying to populate some default Seblod User fields, not all, only the ones I have datas.
So, I prepared the .csv file as described here - I'm sure the column_name are rights (only 10 columns in the test) + I put the column order as the Admin form.
I found 2 BUGs and respective reasons / solutions. Well, what's happen? :
1 - All the Seblod User fields are Padlock opened, so stored into the _#cck_store_item_users,
So, I set Object as: "User" + "Standard" (practically the way to choose if "Padlock opened" or "Padlock closed" fields).
But the Import process doesn't care of it and always Imports fields as Padlock closed creating the fields table _#cck_store_form_user !
Neither it doesn't care if the column_name coincides.
2 - When the User doesn't exist, it is created and a Registration email with Username and Password is sent. But the email is always sent in the Backend language, while should always follow the Frontend language, the language of the site.
For example I used to work with an English Backend, while the Site Frontend is the customer language.
The text was updated successfully, but these errors were encountered: