Hello,
I had to install the module for a customer and I did not read the installation documentation properly.
I did not notice the information about the use of the Dashboard to connect my Magento to Lengow
=> I went to Stores > Configuration | Lengow > Global settings
I filled the accountID/API credentials...etc => No error but no connection was found in the Lengow catalog creation process...
It took me some times and some exchange with the support to understand that the fact that I filled those fields directly was the error.
I think that it could have been avoided by adding information in the configuration view to redirect user to the Dashboard view.
Maybe some comments on those fields should specify that they MUST NOT be filled directly and the wizard should be used ?
Maybe those fields must be read only as they should not be filled if a CMS connection is used ?
Maybe the configuration fields must appear only after the wizard was executed (Using a flag configuration) ?
I would not do the PR as I don't know what UX you prefer (assuming I'm not the only one thinking that configuration tab is made for configuration and Dashboard tab is made for information once the module is configured).
Kind Regards,
Baptiste
Hello,
I had to install the module for a customer and I did not read the installation documentation properly.
I did not notice the information about the use of the Dashboard to connect my Magento to Lengow
=> I went to Stores > Configuration | Lengow > Global settings
I filled the accountID/API credentials...etc => No error but no connection was found in the Lengow catalog creation process...
It took me some times and some exchange with the support to understand that the fact that I filled those fields directly was the error.
I think that it could have been avoided by adding information in the configuration view to redirect user to the Dashboard view.
Maybe some comments on those fields should specify that they MUST NOT be filled directly and the wizard should be used ?
Maybe those fields must be read only as they should not be filled if a CMS connection is used ?
Maybe the configuration fields must appear only after the wizard was executed (Using a flag configuration) ?
I would not do the PR as I don't know what UX you prefer (assuming I'm not the only one thinking that configuration tab is made for configuration and Dashboard tab is made for information once the module is configured).
Kind Regards,
Baptiste