Skip to content
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

Open
joomleb opened this issue Sep 21, 2017 · 2 comments
Open

SEBLOD Importer - 2 BUGs: solutions #29

joomleb opened this issue Sep 21, 2017 · 2 comments

Comments

@joomleb
Copy link

joomleb commented Sep 21, 2017

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.

@joomleb joomleb changed the title SEBLOD Importer - 2 BUGs: soultions SEBLOD Importer - 2 BUGs: solutions Sep 25, 2017
@klas
Copy link
Contributor

klas commented Sep 28, 2017

I would say both are feature requests, not bugs.

@joomleb
Copy link
Author

joomleb commented Sep 29, 2017

Hi Klas,
thanks for reply. but it seems to me an approximate and not useful answer, and knowing your wonderful work on the Forum I'm a little bit surprised.
I like to follow the logic and the simplest way, and I like to be carefully and accurate on my reports, so, Please:

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 ?
If I'm right, then, SEBLOD Importer should works importing datas into that table. Right ?
Infact, the first option to select into that Add-on is:
Object: Article / Category / User" + Standard / Custom
What do they mean ? Into the SEBLDO Importer documentation you wrote: "The first 2 options are relatively self explanatory and are interconnected". As far as I understand

  • "Standard" mean "Padlock opened" = should store into #_cck_store_item_users table
  • "Custom" mean "Padlock closed" = should store into #_cck_store_form_user table
    Am I right ? If is so, this is a BUG beacuse with Standard and / or Custom option selected it always import datas into the #_cck_store_form_user table, considering always fields like"Padlock closed" = cannot import data into the Seblod standard user fields.

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.
It's a logic issue: a User is a Frontend question not a Backend = a user should always receive notifications / messages / emails in the Frontend language, the language of the site.
If the logic is not an opinion, this "is a BUG"

Thanks to all Seblod Team for the attention

@sebastienheraud sebastienheraud transferred this issue from Octopoos/SEBLOD Mar 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants