Allow users to selete and edit their own theme
Permalink
I seem to really be missing something. I've been trying to figure out how to get Concrete5.6.1.2 to allow me to add a user and then when they log in selete a theme and setup the page. Then only they will be able to edit their own page. I found the permission to allow a user to edit their own, but when a user is created it doesn't allow them access to any part of the system to do anything, not even log out.
If another user is created and they log in are they able to selete the same theme to use? but not edit the other users pages?
Thanks
Bob
If another user is created and they log in are they able to selete the same theme to use? but not edit the other users pages?
Thanks
Bob
Or Drupal, Joomla, WP, ImpressPages, jcore, Plone, Phire, SilverStripe and that was one week. The list goes on but C5 handles the building/editing much better for the novice (Clients I'm looking to reach) with the new system I'm building in AWS.
I'm not able to do a the coding like you mention, I've only used Slackware since 1995 to run an ISP for 15 years. I know my way around a system, and still beta many setups but not changing code to fix errors unless it's simple syntex error or permissions.
I read that there was a Multi Site/User in C5 add on but haven't been able to locate it to see if it might work.
Several other CMS's (I've installed at least a dozen over the past couple weeks) have multi user but the way to edit the pages will discurage the novice customer (I have the wife test each one after install) quickly. If novice can't work it, I move on. I've tried Drupal 5 or 6 times because I would fine something new but didn't help. C5 is the first that was actually easy for the novice to use, but they can get into other user pages. That needs to be prevented.
I found the writeup someone was able to have multiple installs and used one core, just not sure yet if it will do what I'm looking. It might. I have to run the setup today and see.
There was a place that has the Webmaster setup but had no demo, you had to buy to try.
I'm not able to do a the coding like you mention, I've only used Slackware since 1995 to run an ISP for 15 years. I know my way around a system, and still beta many setups but not changing code to fix errors unless it's simple syntex error or permissions.
I read that there was a Multi Site/User in C5 add on but haven't been able to locate it to see if it might work.
Several other CMS's (I've installed at least a dozen over the past couple weeks) have multi user but the way to edit the pages will discurage the novice customer (I have the wife test each one after install) quickly. If novice can't work it, I move on. I've tried Drupal 5 or 6 times because I would fine something new but didn't help. C5 is the first that was actually easy for the novice to use, but they can get into other user pages. That needs to be prevented.
I found the writeup someone was able to have multiple installs and used one core, just not sure yet if it will do what I'm looking. It might. I have to run the setup today and see.
There was a place that has the Webmaster setup but had no demo, you had to buy to try.
Yes, it depends on the breakdown of manual/automatic work you're looking for.
If I understand correctly, you want to offer hosted C5 sites to end users.
The most straightforward method, used by most hosts, is separate installs. That does duplicate code, takes up more space on the server, and requires more maintenance when upgrading. The server space typically becomes insignificant when user content is added. However, upgrading existing installs can be an issue -- however, most hosts expect that individual users will upgrade.
The one install, multiple sites approach I haven't used. It does cut down on the install space. However, it does tether users together for the application in the large. When upgrading C5, you may run into issues on individual sites.
If you're looking for nested websites available for users, it's possible to set that up. In this case, you'd offer something comparable to SaaS -- you provide the environment and allow folks to work within that.
Let me sketch out a manual approach to this. Use advanced permissions. Create a folder for the user, which serves as their website. Give only them (and you) permission to access their folder.
Then, the fun stuff. You'd need to filter the dashboard on only the items their site uses, and only their folder structure. You'd want to code the theme selector so that they could choose a theme for their site which would serve as the default. (Users can select a theme for any page, but the default would always be the overall site default). I'm sure there are other issues, but that at least gives a sense of the approach.
This outlines some strategies I'd consider, depending on the desired end result.
If I understand correctly, you want to offer hosted C5 sites to end users.
The most straightforward method, used by most hosts, is separate installs. That does duplicate code, takes up more space on the server, and requires more maintenance when upgrading. The server space typically becomes insignificant when user content is added. However, upgrading existing installs can be an issue -- however, most hosts expect that individual users will upgrade.
The one install, multiple sites approach I haven't used. It does cut down on the install space. However, it does tether users together for the application in the large. When upgrading C5, you may run into issues on individual sites.
If you're looking for nested websites available for users, it's possible to set that up. In this case, you'd offer something comparable to SaaS -- you provide the environment and allow folks to work within that.
Let me sketch out a manual approach to this. Use advanced permissions. Create a folder for the user, which serves as their website. Give only them (and you) permission to access their folder.
Then, the fun stuff. You'd need to filter the dashboard on only the items their site uses, and only their folder structure. You'd want to code the theme selector so that they could choose a theme for their site which would serve as the default. (Users can select a theme for any page, but the default would always be the overall site default). I'm sure there are other issues, but that at least gives a sense of the approach.
This outlines some strategies I'd consider, depending on the desired end result.
Thanks for your reply.
I was looking at the multi-site add on, but not sure that will really work but I'm going to take a look first since I really like the editor C5 has.
I've also been looking at a few small flat file CMS I ran across to do this. The editors are a little clunky, but works well.
I'll create a simple perl script to create their directory, copy the files to the directory, ask them what template setup they want, copy those files to their public dir, and create a password to access the editor.
One takes up about 6 megs space with no pages, another 32 megs and the other about 45 megs.
I'll have to create a simple database to keep track of their directory names for them since most might get confused with /~dirname etc. and work on a rewrite mod.
This way one person messes up it's only their site and it doesn't migrate to any others or the system. I'll have a one click start over available. Limits it completly to their directorys. One diretory will be the public viewable page and another will be proteted that has their editor.
This is going to only be basic web sites for the novice, and they will be able to choose from the templates only, maybe 4 - 5 pages max on a couple of them. Maybe 20 - 30 megs each site when they finish and a little more for someone if they have a small photo galary.
In our area most are on the internet, but many people and more than I expected small business's don't have even a single web page. I'm hoping to tap that market. One reason I need it to be very, very simple. I won't be have shopping carts and larger sites.
They login and get their web site in the editor and can edit in-page.
They don't need anything else. The more experenced users will go to a large host anyway.
Bob
I was looking at the multi-site add on, but not sure that will really work but I'm going to take a look first since I really like the editor C5 has.
I've also been looking at a few small flat file CMS I ran across to do this. The editors are a little clunky, but works well.
I'll create a simple perl script to create their directory, copy the files to the directory, ask them what template setup they want, copy those files to their public dir, and create a password to access the editor.
One takes up about 6 megs space with no pages, another 32 megs and the other about 45 megs.
I'll have to create a simple database to keep track of their directory names for them since most might get confused with /~dirname etc. and work on a rewrite mod.
This way one person messes up it's only their site and it doesn't migrate to any others or the system. I'll have a one click start over available. Limits it completly to their directorys. One diretory will be the public viewable page and another will be proteted that has their editor.
This is going to only be basic web sites for the novice, and they will be able to choose from the templates only, maybe 4 - 5 pages max on a couple of them. Maybe 20 - 30 megs each site when they finish and a little more for someone if they have a small photo galary.
In our area most are on the internet, but many people and more than I expected small business's don't have even a single web page. I'm hoping to tap that market. One reason I need it to be very, very simple. I won't be have shopping carts and larger sites.
They login and get their web site in the editor and can edit in-page.
They don't need anything else. The more experenced users will go to a large host anyway.
Bob
Bob --
That sounds pretty straightforward, and a good business model. 50% of all businesses have websites, 50% don't. When you think about it, that's an incredible adoption rate. And yet, it still leaves a wide open market. The difference is based a lot on demographic and business factors -- addressing those with custom product can really encourage folks to get on the web.
The approach you're looking at is likely a sweet spot. I'm assuming that you are not using cPanel, so you'll be doing all the OS level work. That division of labor, as you note, can be automated to some extent.
The latest release of C5 includes a command line installer, so that might really streamline your install --http://www.concrete5.org/documentation/how-tos/developers/install-c... . Do note that the C5 install is more complex than file-based CMSes -- with database creation and population, so the install either GUI or command line really is required.
All the best.
That sounds pretty straightforward, and a good business model. 50% of all businesses have websites, 50% don't. When you think about it, that's an incredible adoption rate. And yet, it still leaves a wide open market. The difference is based a lot on demographic and business factors -- addressing those with custom product can really encourage folks to get on the web.
The approach you're looking at is likely a sweet spot. I'm assuming that you are not using cPanel, so you'll be doing all the OS level work. That division of labor, as you note, can be automated to some extent.
The latest release of C5 includes a command line installer, so that might really streamline your install --http://www.concrete5.org/documentation/how-tos/developers/install-c... . Do note that the C5 install is more complex than file-based CMSes -- with database creation and population, so the install either GUI or command line really is required.
All the best.
BTW, it's probably not that big of a deal to allow people to have multiple themes and allow them to choose in their site design rather than ahead of time.
I can't say for certain, but I believe that all the standard themes use a standard naming convention so that essentially content can be displayed in any of them without a loss.
The one page type that I typically develop, not in the standard themes, is a 3 column. I tend to use a 960 base or freeform, which makes that straightforward.
I can't say for certain, but I believe that all the standard themes use a standard naming convention so that essentially content can be displayed in any of them without a loss.
The one page type that I typically develop, not in the standard themes, is a 3 column. I tend to use a 960 base or freeform, which makes that straightforward.
However, if you're wanting each user to have their own mini-website and content, that's something you'll need to program. Or, perhaps a social media system -- such as Elgg -- is a better foundation for your application.