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.
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 does Composr handle user authentication with external systems like LDAP or HTTP authentication?
Answer
Composr can integrate with LDAP and HTTP authentication, but these features are considered complex and may require programming experience to set up correctly. Both methods allow users to log in to Composr using their existing credentials from the external system, streamlining access and management.
What are the limitations of using a third-party forum driver?
Answer
Using a third-party forum driver can lead to limitations. Custom profile fields of type LONG_TEXT are limited to TEXT length, cookie integration is not officially supported and can be complex, and some forum drivers have specific quirks detailed in the nuances tutorial.
What are the implications of using the "none-forum" driver?
Answer
Using the "none-forum" driver disables or limits many Composr features, including commenting, points, and user interactions. Consider using Conversr instead and restricting access to the forum zone, join module, and personal zone.
How can I integrate my forum visually into my website?
Answer
Composr allows you to integrate your forum visually into your website. Enable "Show forum within website" in the Admin Zone configuration module and update the forum link in your menu to pass through the "forums" embedding module. You may need to adjust CSS to achieve a seamless look.
The forum base URL should be a URL prefix to your forums without a script name. For example, http://forums.example.com is correct, while http://forums.example.com/index.php is incorrect. You can fix this using the config_editor.php script and then clear the Comcode page cache.
Most Composr resources with commenting enabled create comment topics in the configured comment forum. If the forum uses BBCode, Comcode features not supported by BBCode may not display correctly. Moderate comments from the forum as you would any other topic.
It's not easy to switch forums after installing Composr. The member and usergroup IDs referenced by Composr would lose their association. Check the "Importing data into Composr" tutorial for more information on this.
Conversr is Composr's built-in forum system. It offers seamless integration, allowing you to use Comcode for forum posts, a unified Admin Zone, shared themes and templates, and innovative features like Private Topics and in-post whispers. Using a third-party forum can be clunky and may lead to maintenance headaches.
Composr supports several forum drivers, including Invision Board, phpBB, myBB, vBulletin, Burning Board, and Simple Machine Forum. If your forum is not listed, professional developers can add support. Composr also provides converters for migrating from these forums to its own forum system, Conversr.
