Features: A-Z Index
A
B
C
D
E
F
G
I
L
M
N
P
Q
R
S
T
W
Newest 10 Entries
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:
|
Question | Can I integrate a dedicated issue management system with Composr? |
---|---|
Answer | While Composr doesn't have a built-in issue tracker, a non-bundled addon (cms_homesite_tracker) provides an integrated, modified version of Mantis. Additionally, the Support Ticket system can function as a basic private issue tracker using features like Post Templates. |
Question | How can I restrict access to the support system to specific users? |
---|---|
Answer | Utilize Composr's page access permissions to control who can access the Support Ticket page. This ensures only authorized users can submit support requests. You can also control permissions based on ticket type when adding or editing a ticket type. Make sure if you go this route that the Support Ticket page permissions are very liberal (e.g. allow anyone to access, or just restrict to guests if you will never allow guests to make tickets). Otherwise, some people cannot make tickets even if they have permission on the type. |
Question | What are Post Templates and how are they beneficial for support? |
---|---|
Answer | Post Templates are predefined text blocks that can be used as templates for new forum posts. They are particularly useful in support scenarios by:
Post Templates can be configured to be the default post in specific forums or restricted to certain user groups. Go to Admin Zone > Structure > Forums > Post Templates. |
Question | How does Composr handle email integration for support? |
---|---|
Answer | Composr can integrate with email for ticket management, assuming certain requirements are met:
With email integration, users can submit tickets via email, and staff can reply through the system. Composr cleans up email text for ticket clarity and allows forwarding emails to the integrated address for efficient handling. |
Question | How can I categorize and prioritize support requests? |
---|---|
Answer | Support Ticket System: Utilize support ticket types, managed in the Admin Zone > Setup > Support tickets. Staff can set individual notifications for different types. Discussion Forums: Create dedicated subforums for different support categories or priority levels. Feedback System: The content to which the feedback is attached implicitly categorizes it. For prioritization, subforums can be used. |
Top 10 Entries
Title | Galleries |
---|---|
Icon | ![]() |
Description | Multimedia: Supports images, videos, audio, and more. Personal galleries: Allow your members to create their own galleries which show up on their profile. Support for embedding YouTube videos: Save on bandwidth. Auto-detection of video length and resolution (most file formats) Full tree-structure support: Have galleries within galleries within galleries. Multiple display modes View entries as a slideshow Automatic thumbnail generation Mass import: Also supports importing metadata Optional watermarking: To guard against thieving swines
Geotargeting Adjustments: Automatic size and orientation adjustments according to metadata. |
Title | Catalogues |
---|---|
Icon | ![]() |
Description | Think “databases on my website”. Flexible data control: Set up multiple catalogues, each with its own set of fields. There are many types of fields, such as short text fields, upload fields, and date fields. Multiple display modes: Display the contents of categories using tables, boxes, or lists. Powerful structure: Each catalogue contains categories which contain entries. Catalogues can have a tree structure of categories and/or work from an index. Configurable searching: Choose which fields are shown on categories, and which can be used to perform searches (template searches). Compliance with data protection legislation: Specify which fields may contain sensitive data. These fields will be anonymised as appropriate when members download or purge their data. Entirely customisable: Full support for customising catalogues, categories, and entries, exactly as you want them- field by field. You can even make custom page templates per-catalogue. Classified ads: Entries can automatically expire and get archived. You can also send out view reports. Community interaction: You can allow users to comment upon and rate entries. Import data from CSV files Periodic content reviews: Helping you ensure ongoing accuracy of your data. |
Name | Patrick Schmalstig |
---|---|
Photograph | ![]() |
Title / Role | Lead Developer |
Contributions / Notes | 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. |
Links |
Name | Jim Davidson |
---|---|
Title / Role | contributor |
Contributions / Notes | written many tutorials via Arvixe |
Name | Chris Warburton |
---|---|
Title / Role | developer for ocProducts |
Contributions / Notes | Made some key contributions to ocPortal |
Name | Haydn Maidment |
---|---|
Title / Role | project manager for ocProducts |
Contributions / Notes | None available |
Name | Steve Jarvis |
---|---|
Title / Role | project manager for ocProducts |
Contributions / Notes | Wrote many tutorials via Arvixe |
Name | Philip Withnall |
---|---|
Title / Role | Early Developer |
Contributions / Notes | 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 |
Name | Allen Ellis |
---|---|
Photograph | ![]() |
Title / Role | Founder |
Contributions / Notes | 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 |
Name | Robert Goacher |
---|---|
Photograph | ![]() |
Title / Role | Founder |
Contributions / Notes | 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 |