I'm working on a marketplace website. The idea is to allow for suppliers to login, add their products, view orders, generate reports etc.
I'm using Spree Commerce, and I see everyone suggesting to use spree-drop-ship extension to achieve all/part of above.(it's not really clear from the documentation, all the features that spree-drop-ship is supposed to add)
I've followed 'demo' instructions from https://github.com/spree-contrib/spree_drop_ship and successfully installed spree with the dropship extension, I can see 'suppliers' tab in /admin page. BUT I don't understand how the suppliers are supposed to login. They don't appear to be special user(actually I can't see in Users any supplier), and also when creating new supplier there is no way to set a password.
So my question is, how are supplier supposed to login, i.e. how they/I create supplier user and set password.
Thank you in advance,
- Jack
Note:
I know there is also 'marketplace' extension, which is not maintained anymore by #JDutil, but from what I understand it was solving payment issues to the dropshipper.
I think this is still in progress, Please see the following steps.
Register a normal User
From Admin, Add a new supplier. Add the user created above in the user field in new supplier form.
Login as a normal user, using the user from step 1.
It logs in as a normal user.
Now, goto /admin and it will show you supplier admin panel. But, Not able to add a product from here. It shows "Authorization error" when we click on "Add new" link.
Any help would be great.
For this you just need to signup as normal user then from admin panel, from suppliers tab admin can assign a user as supplier. Hope it is helpful for you.
Related
While working with Google Action Console OAuth, it was rejected for the following reasons.
please, Help me.
Based on the line, "We couldn't find account creation/linking prompt", I'm guessing your OAuth page didn't have a "Create an account" link.
If you're telling them you want users to use your website to create accounts, users need to be made aware how to do that.
If you already have that, add "users can create an account on our OAuth page by clicking [Create an account]" (or however you say it) to your Testing Instructions and resubmit.
I'm not very used to Apostrophe and currently checking out that CMS.
What I want to do is implementing a user login at the frontend.
I tried using the apostrophe-user module but users that were created using that module are able to login to the backend and I don't want them to be able to do this.
Is it somehow possible to achieve what I want to do?
Thank you very much in advance!
Edit: I'm also using apostrophe-headless
You can use apostrophe-groups to create a sub group of users with specific permissions and then check those permissions in various places (like templates) to show or not show certain admin experiences.
https://apostrophecms.org/docs/tutorials/intermediate/permissions.html
You could further customize the login experience of these users by tapping in to the apostrophe-login, redirecting them to a special part of the website, etc https://apostrophecms.org/docs/modules/apostrophe-login/index.html
I'm trying to create a new account and I can login but I get to the page that asks my account name, region, company name and role.
I've input in all fields and accepted the terms and conditions but run into an error that says tenant must have a name. I'm not sure what tenant refers to and how I should fill out the form to proceed.
This seems to be a problem on Auth0's side. I'm experiencing it too. I've opened a bug report on their forum here: https://ask.auth0.com/t/signup-flow-causes-tenant-must-have-a-name/2495.
I just updated to GitLab version 6.0, and I don't see any option to remove a user from a group once they have been added.
To be clear, let's say you have two GitLab user accounts with the first name "Steve". So you're trying to add "Steve J." to a particular group, but you accidentally added "Steve R." instead. Steve R. shouldn't have access to this group.
So how do you get Steve R. out of the group?
I've tried everything I can think of short of going directly to the database and modifying it.
As of version 6.0.2 there's a panel for removing and modifying a user's group permission:
Enter a group's dashboard, in the superior menu there's a "Members" link. That should be it.
URL is like http://{gitlab-host}/groups/{group-name}/members
In general, the issue 5277 talks about:
They couldn't do it in the Admin Area.
They couldn't do it in the Members area of the Group.
Said admin must go to "My Account", click on Groups, and then "Leave Group".
May be you can apply that for user, going the user account page.
The OP C Overton confirms in the comments:
I checked and this only works for removing myself from a group. I still can't remove another user from a group, even though I'm an admin.
The alternative is to contact the user and ask them to remove themselves from the group, but this isn't really practical.
That should complete the requirements for isse 5277.
I need to allow a quick registration in a Prestashop web to our visitors in a trade fair, and I've made a registration form outside the Prestashop framework with just a few fields (1st name, surname, email, postal code/zip, newsletter checkbox and conditions/privacy agreement). It must be a clean screen with just the logo and the form. When the visitors send it, a process must store their data.
What I'm not sure of is which table fields should the process fill in in order to have them enabled as new users when they sign in.
I suppose it's necessary to fill in the "not null" fields without defaults in "ps_customer", and in "ps_address". Is any additional table necessary? How's the password generation algorithm? The process will create it and send it to the new user.
Maybe someone of you needed to do this previously, or maybe you simply know the intrincacies of Prestashop's registration process. I haven't had enough time to delve into it yet.
You can do this with the prestashop web api:
http://doc.prestashop.com/display/PS15/Using+the+PrestaShop+Web+Service
The docs actually include an example of this exact scenario