HTML Logo by World Wide Web Consortium (www.w3.org). Click to learn more about our commitment to accessibility and standards.

Moving forward with Composr

ocPortal has been relaunched as Composr CMS, which is now in beta. ocPortal 9 will be superseded by Composr 10.

Head over to compo.sr for our new site, and to our migration roadmap. Existing ocPortal member accounts have been mirrored.


Zones with independent CEDIs (modules)

Login / Search

 [ Join | More ]
 Add topic 
Posted
Rating:
#88758 (In Topic #17971)

Non-joined user

Is there a way for each zone to 'owns' its own modules, e.g. it's private CEDI and Catalog

Hello,

I recently discovered ocPortal and found the software very suitable for an online project documentation/development and file management portal site.

Particularly the CEDI and catalog functions are great. And the software as a whole seems very thought of.
But there are some structural paradigms I'm not sure of how to use, and for which I don't find direct documentation.

At the moment I'm experimenting on a local machine to create a suitable design and structure.

The main concern is the use of modules in different Zones.

The structure of the 'site' is to have different project documentation sections which are completely separate and independent from each other. With ocPortal that seems to be done with the use of zones.
But when a new zone is added it has no modules of it's own. If I want to have a catalog module it seems that it has to be linked to the catalog (or section in it) which belongs to the main site. The tree structure of the zone has no modules of it's own.

From the perspective of the administration back-end UI there seems no way of importing/loading certain necessary modules for each zone.
It seems awkward having to link in a certain zone to f.e. the CEDI module of the main site.

What I found was to manually copy a module in the zone modules directory, Although it shares the same database the module belongs to that zone, and with some subsections in the CEDI it seems possible to separate sections in the catalog to certain zones (which in my case are independent projects).

recently I found the redirect function, which seems to achieve the same structure and (mimicked) behavior of keeping databases autonomous.

So what is the best practice:
-Is copying modules manually a good 'legal' way, or will it create problems in the future I can't know of.
-Or is the redirect function the best way to achieve that structure.
Is there an other way to get different CEDI and catalogs linked to its own zone (and perhaps with independent databases)

Thanks
Eli
Back to the top
 
Posted
Rating:
#88759
Avatar

Redirect is best, other issue solved by 'virtual roots' feature, should be covered in docs.


Become a fan of ocPortal on Facebook or add me as a friend. Add me on on Twitter.
Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about ocPortal whenever you see the opportunity.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying ocPortal on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Back to the top
 
Posted
Rating:
#88766
Avatar

Fan in training

Hello,
Thanks very much for your answer and pointer.

I read up on 'virtual roots' and from how I understand it:

-create a transparent redirect to the CEDI catalog
 -in the new zone ad link to a sub section (meant for that zone) in the CEDI catalog tree-node
-the 'virtual root' seems to be the masqarade of the breadcrump (so that you can't go up to the root)

 instead of inserting the whole url, i did this as below (extracted from full url)
 some-project-1:cedi:type=misc:id=6&keep_cedi_root

Seems to work.

ocPortal is impressive well thought off

Thank you very much. Eli
Back to the top
 
Posted
Rating:
#88767
Avatar

That's it :).


Become a fan of ocPortal on Facebook or add me as a friend. Add me on on Twitter.
Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about ocPortal whenever you see the opportunity.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying ocPortal on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Back to the top
 
Posted
Rating:
#88768
Avatar

Fan in training

That's quick :o

Thanks, Eli
Back to the top
 
There are too many online users to list.
Control functions:

Quick reply   Contract

Your name:
Your message: