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.
While Wiki+ shares similarities with traditional wikis, it provides two key distinctions:
Optional Post Contributions: Wiki+ allows users to contribute short snippets of information (posts) directly on pages, enriching the content without formally editing the page itself. This feature is optional and can be enabled or disabled as needed.
Optional Tree Structure: Unlike standard wikis that rely solely on cross-linking, Composr's Wiki+ offers the flexibility of organizing pages within a hierarchical tree structure. This structure can be used in conjunction with or as an alternative to cross-linking.
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.
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.
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.
How does Composr handle email integration for support?
Answer
Composr can integrate with email for ticket management, assuming certain requirements are met:
PHP IMAP extension installed.
Functional PHP mail command (local SMTP server or configured Windows SMTP settings).
Active system scheduler (Cron).
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.
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.
What are the current release plans for version 11?
Answer
As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site.
We will be releasing several beta versions in the beta phase.
We do not know when we will be able to release the first Release Candidate or stable versions at this time.
These plans are all subject to change without notice.
