• Default Menu: Generated automatically from the Sitemap, reflecting the structure of your content.
• Editable Menus: You can create and fully customize these menus, adding links to specific content or external websites.

• Welcome Zone: The initial landing page, often used for login/signup.
• Site Zone: Your main website content, with features for viewing, submitting, editing, and deleting content on the member level.
• Admin Zone: For site administrators to manage the website.
• Content Management Zone: Where content is added, edited, and deleted, typically by site staff.
• Forum Zone (if using Conversr): Houses the forum section of your site.

• Zones, Pages, and Categories: Control which usergroups can view specific zones, pages, and categories (permissions).
  • Admin Zone > Security > Permissions Tree Editor, or on the UI for the Zone / Page / Category.
• Global Privileges: Define permissions for actions like using advanced Comcode or bypassing the word filter, applicable across the entire site.
  • Admin Zone > Security > Global privileges
• Module/Page Overrides: Tailor privileges for particular content types by overriding them on the controlling module or page.
  • Admin Zone > Security > Permissions Tree Editor [> Content permissions]
• Category Overrides: Modify privileges for specific categories, allowing fine-grained control over actions within those categories.
  • Admin Zone > Security > Permissions Tree Editor
• Match-key Permissions: Implement ad-hoc access control based on specific match-keys, offering flexibility beyond traditional permission structures.
  • Admin Zone > Security > Match-key page restrictions

• FirePHP: This browser add-on allows you to view detailed logs of permission checks performed by Composr. By analyzing these logs, you can identify which checks are failing and adjust your settings accordingly.
• Permission Check Logging: Enable logging of failed permission checks to a file (data_custom/permission_checks.log). This provides a persistent record of permission issues that you can review and troubleshoot.

Coded the chatroom, blogging support, the analytics system, and OcCLE (now Commandr)

Masters Degree in Computer Science degree from The University Of Cambridge

Other work has included helping out with Firefox, and ongoing work on GNOME

Original designer for ocPortal

Also conceived and coded the Theme Wizard and Point Store

Son of one of the early inventors of Internet protocols (Usenet, aka Internet newsgroups)

Token non-brit

Ran some of the early websites where ocPortal came from

Technically the original developer of ocPortal, in that he wrote the first few lines of code

Heavily involved in the feature design process

Hosted some of our early meet-ups

Original developer of ocPortal, former lead developer of Composr CMS

Masters degree in Computer Science from The University Of Sheffield

Undertaken work for over 15 FTSE-100 companies, as well as many small and mid-sized organisations. Includes a number of banks and major brands.

gameRevolt (@[email protected]) - LinuxRocks.Online

That depends on several factors. Here are some pros and cons of each:

It is not recommended you do this because you may run into issues. For example, some changes were made in crypto_master.php and data/upgrader2.php prior to the first v11 alpha. These changes will result in a broken upgrade unless you already pulled these changes from git. Similar situations could happen in the future as well.

It is recommended you either discard the git install and use a fresh install from the Downloads, or to maintain a git install and a bleeding-edge release install separately. Do not combine the two.