I need to find a CMS like, set of modules/module which does the following:
give users different logins and access to add their own products.
other users cannot see products which are not added by themselves.
so user A can enter his login and add a set of 5 products. user B can enter his login and add 2 products. user A can never see the 2 products added by B and vice versa.
Any suggestion in already existing modules?
both free and with a price
You can do this with Forms and Lists. Setup the fields you want to collect and then you can use it to only render the logged in users results to them. Also could use XMLdb module or even reports module to query the data out of the database after saved with forms and lists
So no one can see each others products? They are just going to buy from themselves? ;)
Tricky part about users adding their own products is payment. That's why this is not a common store feature. If you allow people to add products, you usually need to allow them to setup their own payment provider to collect the money. And in some cases you (the site owner) would want to take a percentage. Which makes it even more complicated.
I'm not aware of any GOOD DotNetNuke e-commerce module that can do this.
It's very possible Catalook has some feature to do this. They have somehow tried to add every feature ever imagined into their product. But, overall I find it terrible to work with. That is your best bet for trying to get something like that out of the box.
Or try and get one of the open source solutions like NBstore and modify it.
Related
How hard would it be to create a website that lets people create their own pages on them?
Like a company creating a custom page on my site only with a drag and drop system provided by my website (of course they would need to create an account).
What frameworks would I need to use?
I tried searching the web but didn't find anything. I found craft.js but I don't know if I can implement it like that.
Thank you all in advance.
Such a project would be very complex and cannot simply be "coded down". Here are the main reasons:
You need an infrastructure where and how your users can save their websites. Does every user just have one page or several (limited or unlimited)?
Drag and Drop requires some JavaScript interactions and a set of predefined web components like buttons, input fields, labels or images. You would have to define abstract components that could be individually filled with user content.
If you ask your users to register before creating websites, you must respect the "General Data Protection Regulation" (applies for the European Union).
If you want to make money with your project you'll have to consider several legal aspects depending on the country where you live.
In short, there are many reasons why homepage kits are not an easy thing to program.
is there anyway to create two homepages for moodle or someway of doing something similar to having a two homepage effect.
At my work (educational) we offer qualifications and we also offer online (e-learning) courses.
Ideally I want to create one area just for the qualifications where users will get a login and ONLY see the qualifications side of things.
Then I want to make another area JUST for the e-learning side of things. Both sets of users would not be able to see the other areas (ie. e-learning cannot see qualifications etc)
Does anybody know if this is possible?
Hopefully this makes sense.
Kind regards,
What you can do is to have a single front page and then restrict access to individual courses based on their enrollment status.
You can add an additional plugin to allow for self-enrollment with administrative approval.
Additionally, you can do things like hide specific courses or categories of courses and then configure permissions to view these hidden courses or hidden categories.
If you want to create completely unique landing pages, you may need to manage more than one instance of Moodle.
Elo!
The goal is to build a Webshop where all the product categories and products (aswell as user authentication, order placement, order history, etc etc) comes from a REST webservice..
So basically very little data will be stored in the CMS DB..
I've managed to extend the login-part (looking at "Windows Authentication Module"), but im not sure how to proceed with the other parts?
Is the answer here a way to go? However the answer seems to claim that we would need records for each product?
How to change Orchard record repository
First of all, this is something you might want to consider. Do you really want to flood the rest service with requests. From the way you put this question (very little data will be stored) it seems like every time someone browses a page, you create a REST request. This usually is not a good idea, so be sure to include some caching.
Then, I doubt it's windows authentication you want for a webshop. Make sure to check out forms authentication.
Then, I guess orchard is something you could consider for this project. Regular webshops usually have so much overhead that it is better to create a webshop (with this specific requiremetn) in a regular CMS, and orchard is very extendable.
One mayor thing is, payment. Make sure you have a good payment processor that works (or that you can make it work) for orchard.
I am designing a to-do list manager for the iPhone using GAE as the back end. My end goal is to create user sharable lists, and I was looking for some advice/examples of how to go about designing something like that. I know the google user API provides functionality for authenticating users, but from what I can tell any additional user management would be something I would need to implement myself.
Can something like this be done by simply adding usernames to a list that is a property of the data I want to share? I am guessing I am oversimplifying things, but any suggestions would be appreciated.
Thanks
you're right, app engine doesn't have any built in support for user ACLs or permissions, and a few quick web searches didn't immediately turn up any obvious open source libraries.
how to implement full-fledged permissions and ACLs for group sharing is definitely a nontrivial design question. there are a number of other questions here about it.
having said that, as a very rough first pass, you're probably on the right track with storing lists of users. i'd suggest that you abstract the list into separate Group entities, and attach those to yor data instead, so that users can define groups once instead of for every piece of data. i'd also consider storing separate lists of groups that can read vs write. finally, i'd store User properties in the group entities, instead of string usernames or email addresses.
I'm creating a site for a local retail shop using Drupal. Everything's been going very smoothly up until this current bit.
It's a comic shop, and I want to make a place where people can manage their own subscriptions. Since the number of different titles a customer subscribes to can vary pretty widely, I want a way to make a completely dynamic form, with people able to add as many new lines as they need and I'm really struggling with Drupal's documentation.
Essentially, I'd like the final version of the page to look something like this: http://www.monksp.org/foo.html
Anyone have any experience building a drupal form like this?
Could you not achieve something similar using Taxonomy and free tagging? Take a look at http://drupal.org/handbook/modules/taxonomy
So in theory you would have a content type called "Subscription", each user would only be able to create one node of this type, it would have the taxonomy applied to it. The user can then edit the node and add more subscriptions. The great thing about this is that you can also use auto-complete. So say a user is already subscribed to X-Men another user can edit their subscription and start typing "X" this would then auto populate with suggested terms already in the taxonomy. e.g:
X-men: Origins
X-men: Apocalypse Saga
X-men: Noir
I think this is the functionality you've described.