I have been laboring at setting up website with XOOPS to house myself and two other non-html coding members. I have had no success finding a way to separate all members' content in a suitable way in my limited knowledge of cms and XOOPS systems. So I have decided that the only way that this will be possible is if I setup three separate databases and install three different setups of XOOPS on each database. Or can all three fit on one database?

This way all of the members needs will be served separately.

My main goal for setting up a cms was to allow non-html literate members manage complete fully stocked websites on their own without me. I hope that this works out for me, for us. Please feel free to step in and give me any pointers on this or say. "Stop, don't!", etc. Hehe. But I'm going for it in the meantime.

I will host our portal's forum and shop with my own Xoop's website.

I am starting to wonder which forum is the right forum to post in here for certain basic questions that I have about the Xoop's system and my needs for my website. I hope that someone can help me with this. Thanks in advance.

I am attempting to setup my website with two other group members that have "0" html skills. I wanted to use a few modules to let them log in and create their own content for their area of my website. I was trying to avoid any need to constantly update their html documents manually.

This is the main reason why CMS systems interested me in the first place.

I just wanted some simple member user reusable modules that I could use to house a members website articles and content in. I also need these modules to operate seperately for each member. I wanted these modules to allow the members to enter their content in the html/css layouts via php forms within their Admin area. I also want these members to have other modules that allow them to customize their group with Admin rights.

I tried WF-Sections but as I am new to the Xoop's system and I have no docs for this module I am having trouble understanding its relationship parts of the Xoop's system.

So without trying to hit my head against a module setup in a trial and error fashion for which I have "0" time for. I really am looking for a workflow path to help me to meet the goals of setting up a good CMS website that serves the presentation needs of my non-members and my short term and long term development goals. If I can't find a clear way to do this with Xoop's I have to find another solution.

I have tried phpnuke, postnuke and now Xoop's since late September. I am willing to try any CMS that will help me to complete my website goals. And if my "short term" goals can't be met through simple customizations of the Xoop's system I am not willing to invest more time trying to alter Xoop's too much.

Someone mentioned to me that Xoop's later versions will provide a more manageable workflow for webmasters and website members. I like the Xoop's system and I am looking forward to those updates. I hope that I can get everything to work out in the end whatever happens.

How much php skills do I need to create a "one page module" and add onto that module a simple user "data entry" based interface for group members to have access to preconfigured html layouts. I want to add gui's that provide entry data for a page content like, "Title", "Content", "About Us", etc.- with sub content data entry points for menu titles and linked sub pages. I am learning php and I was told to pick a live php based CMS tool and learn php coding within that development model. I have been working with various modules and have found that I will have to build a few of my own simple modules even for custom page content block creation. Even if you can not be too specific on the workflow details that have helped you in creation of a simple module like this, any links to resources would be helpful. Thanks.

My first impression on php and CMS was that I would have to start my own from scratch for a customized CMS development project. Then I discovered open source CMS developments. My goal is to learn to use Xoop's enough to be able to add my talents to its development. Xoop's is the first open source CMS tool that makes sense enough for me to start my own php development through.

I am working with the WF-Sections module and I am new to its usage. Can I use the WF-Sections module to connect a group to my custom "one page module"?

I'm reading the licensing info on the Enterprise-x module and I see that it can't be used in a business model as such.

Well thaere goes that idea.

Ok, now I want to get at the Enterprise-x module's forms and edit the php files to adjust it's form content to suite my sites needs. Can someone point me to the right forum or resource that will help me to do this? Can I make simple adjustments to the form text comments without messing up the code of the php? Thanks.

Quote:


I am setting up my XOOPS website using these Modules:

- Home
-News
-Polls
-Forum
-Enterprise-x
-Contact us
-Counter
-Shop
-WF-Section
-Edito
-Members


I intend to setup user groups for two businesses. I will use WF-Section to allow these groups to edit their own Blocks of articles. I will give one user group that is my business partner limited access to Admin "Comments" as I was not able to allow a user group to have Admin rights to edit a Module without giving them one form of access to the Sys Admin. This user will control the Enterprise-X Module. I will give these two users their own areas on the Forum. I'm not quite sure how to mix in the Edito Module for all of the members. I'm also looking for a Module that will allow the other Member to schedule and plan events for their clients who are Registered Users.

The other Modules I will manage and add articles to the News section from to of the Members with Module Admin rights. I wish that I knew how to create a workflow with a Mod for storing these users articles in an organized and scheduled manner for deployment later.

The Shopping Module will be managed by myself and I will need a Module that will let the members with Modules Admin rights upload product pictures, comments, pricing info, etc to specific categories for later retrieval and implementation by myself.

I want to keep everything simple right now. I hope that this description of my XOOPS site makes sense.

I also have to say that you guys rock! I mean you are really helpful and I haven't gotten a tip that directed me to code in basic features or edit a config file just to get something simple done. The XOOPS doc's are great, the XOOPS members are great. As I said I'm loving this!

Quote:

I had a bad experience with another CMS tool and that brought me to Xoops. The other CMS tool was just too manual for me at this point. With XOOPS even if you don't have worry about editing php code just to get my site to function. I am aware that you have to know how to code with php to get beyond the limits of the CMS database tools. I am learning php and I am glad that XOOPs is stable enough for me to play around with coding existing modules and themes.

But that's a while off now as my work gives me little time to even attempt at playing with php code.

When I try to add Module Admin rights in the Groups settings I can't give Module Admin rights to a group unless they have at least one System Admin right. Why is that the case?

I really need to have some of my members share modules with myself and each other but have separate access rights and separate general website visitor access to these modules. I looked up this prospect and found an article on cloning modules. This seems to be the only way to do this with XOOPS for now, but it is too complicated for my schedule right now.

I guess that I will have to make one member the admin of certain modules that I setup and give them access rights to this module exclusively. Then for the other members Link up WF-sections for them and give them access to the article sections that WF-sections allows them to access.

I wanted to set up a group, assign a member to that group and assign modules access rights to that group. I also wanted that group's area look different than the rest of the main CMS. I wanted these separate groups to have their own Homepage, business presentation area links, News, forum, polls, contact forms, e-commerce module, etc. But I also wanted these separate groups to show links to the main CMS sites Homepage, forum, news, etc.

My partners and I really need this kind of CMS setup, but as we are new to CMS development we will use whatever works at this stage.