Features: A-Z Index
A
Administration Zone
B
Banners
C
Calendar
Catalogues
Chatrooms and IM
Community features
Content Sharing
Conversr Forums
Conversr Topic Polls
D
Design without barriers
Downloads
E
Ease of Use
eCommerce and Subscriptions
Extendable
F
Featured Content
G
Galleries
I
Installation
Integration
L
Localisation
M
Membership
N
News and Blogs
Newsletters
P
Parental Controls
Performance
Points
Privacy Tools
Q
Quizzes and Surveys
R
Rich Media
S
Search Engine Optimisation
Searching
Security
Spam Protection
Stay on Top
Structure / Navigation
Support Tickets
T
Template Programming Language
Testing tools
Themeing tools
Third party integration
W
Warnings / Moderation
Web Pages
Web standards
Website Polls
White-labeling (Debranding)
Wiki+
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
| Question | How do I open or close my Composr website to the public? |
|---|---|
| Answer | By default, your Composr site is closed after installation. To open it to the public (or to close an opened site), go to Admin Zone > Setup > Configuration > Site options > Closed site and adjust the setting accordingly. You can also configure a closed site message. While a closed site prevents public access, it's worth noting that users can still join a closed Conversr-powered site if they have access to the join module URL. However, they won't be able to log in unless they're assigned to a usergroup with "Access closed site" permissions. You can modify the join module's permissions to restrict access further. |
| Question | What is the .htaccess file and how does it relate to Composr? |
|---|---|
| Answer | The .htaccess file is a configuration file for the Apache web server. It allows you to define settings that apply to the directory where it's located and its subdirectories. Composr can leverage .htaccess to enhance security and enable features like "URL Schemes." You can try renaming the provided recommended.htaccess file to .htaccess. This file includes recommended options that tighten security and ensure Composr has necessary PHP and Apache features activated. Note that some web hosts might restrict the use of .htaccess files. You should regularly review recommended.htaccess for changes between Composr updates. |
| Question | How do Composr permissions work? |
|---|---|
| Answer | Composr employs a multi-layered permission system with two main types: privileges and access permissions. The system grants users the best possible access based on the combination of their usergroups. Privileges define broad permissions, such as accessing a closed site or content manipulation abilities based on impact level (low, medium, high). You can set privileges for usergroups via checkboxes, with the option to override them for specific pages or categories. Go to Admin Zone > Security > Global privileges. Access permissions control what content users can view. These permissions are layered:
To configure access permissions, you can edit the specific resource or utilize the Permissions Tree Editor under Admin Zone > Security > Permissions Tree Editor. |
| Question | How do I set up the system scheduler in Composr? |
|---|---|
| Answer | The system scheduler is crucial for scheduled tasks like sending notifications, running backups, and processing reports. To set it up, you need to schedule a system-level task to run the data/cron_bridge.php file at least every 10 minutes. This links Composr's scheduler with your server's scheduler (like Cron on Linux). Composr can often detect the correct command to use for your setup. You can check by visiting http://yourbaseurl/data/cron_bridge.php?query_mode=1, which should display the suggested Cron command. Note that you may need to replace the php command with the absolute path to PHP if you cannot use the php command directly. If your hosting doesn't support Cron or scheduled tasks, you can enable scheduled tasks to run when visitors access your site. Navigate to Admin Zone > Setup > Configuration > Performance options and check "Web requests run scheduled tasks". Keep in mind that this method relies on visitor traffic and isn't as reliable as a dedicated scheduler. Alternatively, consider using external services like EasyCron, setcronjob.com, or onlinecronjobs.com. These services allow you to schedule calls to the data/cron_bridge.php script by URL at specified intervals. |
| Question | What are the different security levels in Composr's Setup Wizard and what do they affect? |
|---|---|
| Answer | Composr offers five security levels in the Setup Wizard: Minimum, Low, Medium, High, and Ultra High. Each level sets various security configurations that you can later customize under Admin Zone > Setup > Configuration. The security levels influence settings such as:
The higher the security level, the more stringent the security measures, with Ultra High offering the most robust protection but the most potential inconvenience to users. Generally, you should use these settings depending on your site:
|
| 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. |
