Please Log in or Create an account to join the conversation.
globalgridfree wrote: I am building a free collaboration community catering to self sustainability and renewable energy for off grid communities and individuals or anyone wanting to try to live easier and healthier.
www.gridfree.ca
I am currently confused on the basic set up and structure of cb 2.0. I cant seem to get the full picture on how CB groupjive,blogs and articles category structure should be set up with user groups and access levels especially once you add projectfork.
1. lets say i have a category called energy , I would like to have the forum,blogs,and articles +projectfork categories "energy" associated with the group energy.
2.when a user makes a new article in "energy" only the article categories should be visible to choose its location(currently all categories in joomla are showing)?
3.choose where to show the content,example energy articles, profile page user1
what i am trying to achieve is, having the choice of a group to join, based on the categories of the site, homesteading,energy,growing,construction etc.
I would also like to have a designated page to each category which will have the categories different content(project,blogs,forum,articles etc)available in a single location in different positions.
I would also like projectfork to have the same main categories that are locked to registered members for changes, but will allow creation of a new project as project admin and allow them to use projectfork for there own personal projects set there own access levels, example,
mike wants to build a solar tractor, mike can go into projectfork energy category and make a project "solar tractor" mike would be admin to this "solar tractor" project only, mike can also choose weather his project is private or invite or open to registered members(site set up for registered to post,public to view). to start i would like project default to be public view. and allow "mike" to choose.
I would also like the project visible in someway in profile? if cb 2.0 plugin not out soon..
what i want to achieve is with projectfork,
1. each registered user can create there own project
2.each creator is the super user for his/her project.
3. each creator can choose weather project be for all registered users, or private (invite only),any registered user can join.
4. the viewing of the project category should only be visible depending on the project privacy setting chosen in step 3.
5.creator chooses access right for there own project, manager, super user,etc for his her own project only
My questions
1. what is the best way to set this up where it wont break CB 2.0 groups?
2.what is the function of allow create group for each project?
3. will enabling the create new groups function break CB 2.0 user and/or groups?
4.if projectfork creates groups how will Community Builder members get access?
5.anything i may be missing
6.do you add groups and access levels for projectfork in cb,joomla,or projectfork, or groupjive?
I am a newbie, so if its really technical an idiot guide would be great, especially for any code work if needed.
thanks for all the new video tutorials
any and all help is greatly appreciated
thank you in advance
Please Log in or Create an account to join the conversation.
nant wrote: I have no idea how Projectfork categories work and if in fact they integrate with Joomla categories.
nant wrote: Sorry, I have no experience with ProjectFork and I am not aware of a CB 2.0 plugin integrating to it (certainly not in our planning).
Please Log in or Create an account to join the conversation.
You could probably use CB Auto Actions and its Query action to push user information to ProjectFork. Alternative is a Code action and just use ProjectFork API in it to synchronize the users. There's no plans for an official ProjectFork integration at this time.That's a bad news, it could certainly be more quick if you were. I'm waiting for an upgrade since a long time but no answer
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.