Contributors: A-Z Index
A
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Allen Ellis | Founder |
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 |
View |
C
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Chris Graham | Founder |
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. |
View | |
Chris Warburton | developer for ocProducts |
Made some key contributions to ocPortal |
View |
H
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Haydn Maidment | project manager for ocProducts |
None available |
View |
J
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Jim Davidson | contributor |
written many tutorials via Arvixe |
View |
P
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Patrick Schmalstig | Lead Developer |
Joined Chris Graham behind the scenes in the development of Composr CMS in 2016. Took on the lead developer role in 2023 when Chris Graham stepped back to attend to his new lifestyle changes. Spearheaded the development of Composr CMS v11 and the new website, Composr.app. Formed the company PDStig, LLC to take on professional support and development for Composr CMS users especially after the discontinuation of ocProducts, Ltd. |
View | |
Philip Withnall | Early Developer |
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 |
View |
R
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Robert Goacher | Founder |
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 |
View |
S
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Steve Jarvis | project manager for ocProducts |
Wrote many tutorials via Arvixe |
View |
Newest 10 Entries
Question | Can I move a Wiki+ page? |
---|---|
Answer | Technically, Wiki+ pages cannot be moved because they don't have a fixed location within the network structure. Creating child links forms a path, not a strict hierarchy. However, you can manipulate the breadcrumbs by ensuring only one path leads to a page. |
Question | Can I track changes made to Wiki+ pages? |
---|---|
Answer | Yes, Wiki+ includes a revision history feature accessible through the page edit screen. This feature allows you to view a log of edits, see changes highlighted in tooltips, and revert to previous versions of a page as needed. |
Question | How can I view the complete tree structure of my Wiki+? |
---|---|
Answer | You can access a view of the complete Wiki+ tree structure through the designated option in the admin panel. However, it's important to note that this view will reflect guest access permissions. Some pages may be hidden if they are restricted to specific user groups. |
Question | What moderation tools are available in Wiki+? |
---|---|
Answer | Wiki+ offers several features to help you moderate user contributions and maintain the quality of information:
|
Question | Can users contribute content to Wiki+? |
---|---|
Answer | Yes, users can contribute content to Wiki+ through posts. When the "Show posts" option is enabled for a page, users can add their insights and information as posts below the main page content. |
Question | What are orphaned pages and how should I handle them? |
---|---|
Answer | Orphaned pages are pages that exist within the Wiki+ database but are not linked to the main tree structure. These pages are not accessible through the tree navigation but can still be reached through direct links or cross-linking. Orphaned pages are not necessarily problematic. They can be intentional if you prefer to link pages using the wiki-style syntax instead of a rigid tree hierarchy. You have the flexibility to choose the linking method that best suits your content organization. |
Question | How can I create and organize pages in Wiki+? |
---|---|
Answer | Pages in Wiki+ can be created in several ways:
|
Question | How does Wiki+ differ from a regular wiki? |
---|---|
Answer | While Wiki+ shares similarities with traditional wikis, it provides two key distinctions:
|
Question | What is Wiki+? |
---|---|
Answer | Wiki+ is a feature in Composr that allows you to create a collaborative, tree-structured database of information. It functions similarly to a traditional wiki but offers enhanced features such as post contributions, a hierarchical structure, and moderation capabilities. |
Question | Are there other Composr features helpful for support? |
---|---|
Answer | Yes, features like:
|
Top 10 Entries
Question | How do I change my website's logo? |
---|---|
Answer | You can change your site's logo manually or by using the Logo Wizard. To change it manually, go to Admin Zone > Style > Themes. Choose "logo/-logo" from the dropdown list, which represents the logo for the Welcome Zone and any zone without a specific logo. Replace the current image by uploading a new .jpeg, .gif, or .png file. Ensure that the 'Name' field remains unchanged. |
Question | What are Composr addons and how do I manage them? |
---|---|
Answer | Composr is built using a series of addons that provide different functionalities. All "bundled" addons are installed by default. Once you are familiar with Composr, it's recommended to remove any bundled addons you don't need to simplify your site and prevent accidental exposure of unconfigured features to visitors (the Setup Wizard can also uninstall these addons based on your preferences). You can manage addons by navigating to Admin Zone > Structure > Addons. Uninstalled addons are archived and can be restored later, but any associated data will be permanently lost. Composr also offers non-bundled addons. These addons are not bundled because they are not considered mainstream, rely on third-party services, haven't been vetted to Composr standards, or don't fully conform to those standards. You can install non-bundled addons by going to Admin Zone > Structure > Addons, scrolling to the bottom and clicking "Import non-bundled addon(s)". You will need to browse to the addon file and click the import button. Once imported, review the warnings and proceed to install the addon. You can also download and import addons from this website under the Downloads section. |
Question | What are some of the default Comcode pages in Composr? |
---|---|
Answer | Composr includes several default Comcode pages, each serving a specific purpose:
Remember that you can edit these default pages or create entirely new ones to tailor your site's content to your specific needs. |
Question | How do I hide a Comcode page from the sitemap? |
---|---|
Answer | If you want to prevent a Comcode page from appearing in your sitemap, you can simply prefix its name with an underscore (_). For example, pages named "_test" or "_example" would be excluded from the sitemap. Note that this generally does not hide the page from your site itself (to do that, use the validation addon to turn validated to "OFF" for the pages); it only hides them from the sitemap / search engines. |
Question | Can I organize Comcode pages in a hierarchical structure? |
---|---|
Answer | Yes, Composr allows you to simulate a hierarchical structure for your Comcode pages using multi-part paths in the page monikers. By editing the page monikers to include slashes (e.g., "about/team"), you can create a virtual directory structure within a single zone, enhancing your site's organization and navigation. |
Question | How do I embed content from other modules into a Comcode page? |
---|---|
Answer | You can use various blocks to embed content from different modules:
|
Question | What is the difference between blocks and boxes in Composr? |
---|---|
Answer | While both terms may seem similar, they have distinct meanings in Composr:
In practice, blocks often place their content within a box, but this isn't a requirement / standard. |
Question | Can I customize the appearance of blocks? |
---|---|
Answer | Yes, you can customize the appearance of blocks by editing the associated templates and CSS. Each block typically has a corresponding template file (e.g., BLOCK_MAIN_NEWS.tpl for the main_news block) that controls its HTML structure. You can modify this template to change the layout and styling of the block's output. An easy way to do this is through the template editor in Admin Zone > Style > Themes, and click edit templates for the relevant theme. |
Question | How do I add dynamic content to my Comcode pages? |
---|---|
Answer | Composr utilizes "blocks" to embed dynamic content and functionality within Comcode pages. These blocks can range from displaying recent forum posts to showing information about the logged-in user. To add a block, you can use the "block construction assistant" accessible via a button above the editor. This tool provides a user-friendly way to:
|
Question | How do I create a new Comcode page? |
---|---|
Answer | Composr provides two easy ways to create a new Comcode page: Method 1: Direct URL Entry Type the desired URL of your new page into your browser's address bar. Since the page doesn't exist yet, Composr will present you with a 404 error and a link to create it. Click the link to open the Comcode page editor. Method 2: Admin Zone Navigate to Admin Zone > Content > Pages (Comcode pages). Scroll down to the list of existing pages and enter the name of your new page using the ":" (page-link) format. For example, a new page in the Welcome zone named "about" would be entered as ":about", or a new page in the "site" zone named "foobar" would be entered as "site:foobar". |