In our use case scenario we are thinking about the possibility of making the Container (store) field editable through the Security → User detail blade seen below:
As I am currently working on investigating the possibilities for this:
What are the reasons behind keeping this field uneditable through the Virto Platform UI?
In case there are no major concerns, are there any recommended paths to try in how to achieve making this field editable? (Ideally by creating/extending a Module, not by modifying Virto’s code base)
Appreciate any insights shared on this.
I checked and found no reason that this field uneditable through the Virto Platform UI,
because it’s editable via API.
As workaround, you can edit via API
Use Store > Links (Linked Stores) to allow sign-in to other store.
Create Fork, fix and sumbit PR to us
I added this request to backlog and dev team will try to fix it in following sprints.
Thank you for your answer.
Would you mind sharing with me any guidelines to create a PR in the Virto code base?
I found this: How to Contribute I Virto Commerce and I am looking for additional information and taking some of the current repository work as reference, but any additional information to guarantee a bit more of success will be highly appreciated.
Sure, How contribute to Virto Commerce open source project
- Fork Virto Commerce repository into your own GitHub
- Clone the repository to your local machine
- Create a new branch for your changes
- Make some changes and commit them with useful messages
- Push the changes to your repository
- Create a Pull Request from your repository back to the original one