Features: A-Z Index

A

Administration Zone

Administration Zone

B

Banners

Banners

C

Calendar

Calendar

Catalogues

Catalogues

Chatrooms and IM

Chatrooms and IM

Community features

Community features

Content Sharing

Content Sharing

Conversr Forums

Conversr Forums

Conversr Topic Polls

Conversr Topic Polls

D

Design without barriers

Design without barriers

Downloads

Downloads

E

Ease of Use

Ease of Use

eCommerce and Subscriptions

eCommerce and Subscriptions

Extendable

Extendable

F

Featured Content

Featured Content

G

Galleries

Galleries

I

Installation

Installation

Integration

Integration

L

Localisation

Localisation

M

Membership

Membership

N

News and Blogs

News and Blogs

Newsletters

Newsletters

P

Parental Controls

Parental Controls

Performance

Performance

Points

Points

Privacy Tools

Privacy Tools

Q

Quizzes and Surveys

Quizzes and Surveys

R

Rich Media

Rich Media

S

Search Engine Optimisation

Search Engine Optimisation

Searching

Searching

Security

Security

Spam Protection

Spam Protection

Stay on Top

Stay on Top

Structure / Navigation

Structure / Navigation

Support Tickets

Support Tickets

T

Template Programming Language

Template Programming Language

Testing tools

Testing tools

Themeing tools

Themeing tools

Third party integration

Third party integration

W

Warnings / Moderation

Warnings / Moderation

Web Pages

Web Pages

Web standards

Web standards

Website Polls

Website Polls

White-labeling (Debranding)

White-labeling (Debranding)

Wiki+

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:
  • Referencing them in the child-list of an existing page.
  • Using the special Comcode syntax [[pagename]] to create inline links, which automatically generates new pages when accessed.
  • Utilizing the "Edit tree" button visible on Wiki+ pages to add child pages directly.
The tree structure can be easily manipulated through the same interface, allowing you to arrange pages in a hierarchy that suits your needs.
Question How does Wiki+ differ from a regular wiki?
Answer 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.
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:
  • Staff-only replies in the Support Ticket system enable private communication among support staff.
  • Notifications for new tickets, replies, or feedback ensure timely responses.
  • Blocks like main_contact_us provide a simplified front-end for ticket creation.
  • Forum moderation tools help manage support discussions effectively.
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:
  • Providing quick responses to common questions.
  • Ensuring consistency in staff responses.
  • Saving time and effort for staff.

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:
  • 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.
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 Structure / Navigation
Icon Image
Description

Intuitive sitemap editor: Visually browse your site structure.

Menu editor: Our user friendly editor can work with several different kinds of menu design (drop-downs, tree menus, pop-ups, etc)

Zones (sub-sites): Organise your pages into separate zones. Zones can have different menus, themes, permissions, and content. They can also use a sub-domain.

Full structural control: Edit, move, and delete existing pages and modules.

Redirects: Set up redirects if you move pages, or if you want pages to appear in more than one zone.

Title White-labeling (Debranding)
Icon Image
Description

Use Composr for clients and pretend you made it.

We ensure Composr is not hard-coded anywhere in the software where it would appear to an average user.

Title Web standards
Icon Image
Description

Responsive design and hi-dpi images

True and correct XHTML5 markup

WCAG, ATAG: Meeting of accessibility guidelines in full.

Tableless CSS markup, with no hacks

Support for all major web browsers

Inbuilt tools for checking webstandards conformance of XHTML5, CSS, and JavaScript

Extra markup semantics including Dublin Core support, schema.org, Open Graph, and microformats.

Standards-based JavaScript (modern DOM and AJAX, no DOM-0 or innerHTML)

Automatic cleanup of bad XHTML5: HTML outside your control (e.g. from RSS) will be cleaned up for you.

Title Performance
Icon Image
Description

Highly optimised code

Can run CDNs

Multiple levels of caching

Sophisticated template compiler

Self-learning optimisation system

Automatic pruning of old cache files when caches get large

Title Localisation
Icon Image
Description

Translate Composr into your own language

Translate content into multiple languages

Custom time and date formatting

Language packs: Download new language packs as users post them; host multiple languages on your website at the same time.

Time zone support: Members may choose their own time zones, and dates / times will adapt to them.

Support for different character sets and Unicode

Serve different theme images for different languages

Right-to-left languages possible

Title Ease of Use
Icon Image
Description

Professionally designed user interfaces

AJAX techniques: Streamlined website interaction.

WYSIWYG editing

Tutorials: Over 200 written tutorials, and a growing collection of video tutorials.

Displays great on mobiles: Mobile browsers can be automatically detected, or the user can select the mobile version from the footer. All public website features work great on QVGA or higher. The default theme is also responsive and will adapt to the client screen size.

A consistent and fully integrated feature-set: Breadcrumb navigation, previews, and many other features we didn't have space to mention here – are all present right across Composr.

Title Search Engine Optimisation
Icon Image
Description

Supports different URL schemes and textual monikers

Automatic site-map generation: Both XML Sitemaps and sitemaps for users.

Metadata: Meta descriptions and keywords for all content. Auto-summarisation.

Keyword density analysis when previewing content

Correct use of HTTP status codes

Content-contextualised page titles

Semantic and accessible markup (e.g. ‘alt tags')

Title Privacy Tools
Icon Image
Description

Compliance with major data protection legislation such as the GDPR

Allow members to download or purge their personal data from their profile. Set a limit on the number of days between downloads / purges to preserve server resources.

Also manage member data to a more technical degree in the Administration Zone.

Allow members to purge their data upon deleting their member account

Composr is careful to maintain important data (such as warnings or bans) when members request their data to be purged from their profile. But this data can still be purged on the admin side (in the Admin Zone).

Automatic generation of a basic Privacy Policy based on site settings and installed addons

Cookie Consent notice

Set declarations on the rules page which members must agree to on registration (or whenever they are changed) which are also stored in the database and e-mailed to the member as a written copy

Title Security
Icon Image
Description

Automatic detection, logging, notifying, and banning of hackers

2-factor-authentication: E-mail based 2-factor-authentication security when unrecognised IP addresses are used with certain usergroups (optional, Conversr-only).

Password strength checks: Enforce minimum password strengths based on length and use of upper / lower case, numbers, and symbols, and avoiding repeated characters (Conversr-only).

Architectural approaches to combat all major exploit techniques

A JavaScript framework that makes XSS attacks virtually impossible

Defence-in-depth: Multiple layers of built-in security.

Encrypted custom profile fields: Once set the CPF can't be read unless a key password is entered (Conversr-only, requires OpenSSL).

Extensive support and use of Content Security Policy (CSP)

Track failed logins and automatically ban brute-force attacks

HTML filtering

Protection against CSRF attacks: Forms and AJAX requests make use of randomly generated POST tokens

Root-kit detection kit for developers

Cookies are secure and HttpOnly where possible to prevent session hijacking

Set number of days that passwords expire or must be changed

Title Warnings / Moderation
Icon Image
Description

(Conversr Only)

Issue warnings (with an optional Private Topic sent to them) for unruly members. Optionally include one or more of several punitive actions as explained below.

Ban the member's IP address so they can no longer access the site from that device (this also adds their IP address in your htaccess file)

Ban the member so they can no longer log in (and their profile can no longer be viewed by others except high-ranking staff)

Report spammers to public blocklists such as Stop Forum Spam

Put members in a special restricted 'probation' usergroup for a specified number of days

Silence a member from the forum or topic on which they made their problematic post (this also works on comments).

Change a member's usergroup (useful to de-rank them)

Automatically delete recent or violating content / posts posted by the member

Charge points from the member's balance (also affects rank points to penalise their ability to rank up)

Reverse recent point transactions members made in abuse

Save and load explanatory messages for future use

Automatically generate punitive action text in the Private Topic sent to the member

Members can view their account standing on their profile, including any active punitive actions and their warnings history

Staff can view full details of individual warnings including an action log and options to undo some of the individual punitive actions

Develop your own cns_warnings hooks to define additional punitive actions that can be used with the warnings system

Use one of the several pre-defined "reasons" for a warning in the dropdown to include the warning in your site statistics (for number of warnings issued by reason).