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 some social considerations for running a website with community features?
Answer Managing a community involves addressing social issues like child protection, free speech, discrimination, and abuse. Establish clear policies on these matters, including content moderation guidelines and procedures for handling feedback. Consider the diverse personalities and potential vulnerabilities of your users.

View

Question What are my legal responsibilities regarding illegal content posted by users?
Answer While "safe harbor" laws offer some protection, you are still obligated to take down illegal content upon becoming aware of it. Implement measures like content checks, clear rules prohibiting illegal uploads, and liability disclaimers. The level of responsibility varies depending on the severity of the content, from copyright infringement to more serious criminal content.

View

Question What steps should I take to make my website accessible?
Answer Website accessibility is essential for inclusivity and may be legally required under anti-discrimination laws. Composr is designed to meet high accessibility standards, but you need to maintain this when creating content or modifying templates. Following WCAG guidelines is crucial, and you can find more information in the accessibility tutorial.

View

Question How can I ensure my website complies with email marketing laws?
Answer Email marketing laws like CAN-SPAM protect recipients' rights to unsubscribe. Your website must include a clear 'List-Unsubscribe' header in every email, offer an easy unsubscribe process, and respect unsubscribe requests promptly. Composr provides built-in mechanisms, including an unsubscribe endpoint and support for the List-Unsubscribe header, to facilitate compliance.

View

Question What are my responsibilities regarding user privacy?
Answer You must have a comprehensive privacy policy that details the personal data you collect, its usage, and if it's shared with third parties. Laws like GDPR have strict requirements, including logging data access, data purging, and security measures. California law mandates specific elements in your policy, like handling "Do Not Track" requests and a clear process for communicating changes.

Composr has an automatic Privacy Policy generator block to help you get started. This is used by default.

View

Question How can I create effective website rules?
Answer A well-defined rules page is crucial for setting expectations for user behavior and outlining consequences for violations. It should cover a range of offenses with appropriate punishments, reference relevant laws, and assign legal responsibility to users. Composr provides default rules pages that can be customized, and this page is displayed to users upon joining the site.

View

Question What are the key legal considerations for running a website?
Answer Several legal aspects need careful attention when operating a website, especially for large or corporate sites. These include establishing clear rules and terms of service, adhering to privacy laws like GDPR and California's regulations, managing personal data responsibly, complying with email marketing regulations like CAN-SPAM, ensuring website accessibility, addressing eCommerce regulations, and understanding liability for content and user actions.

View

Question How do data-tpl and data-view behaviors work in Composr's JavaScript?
Answer Composr uses data-tpl and data-view behaviors for associating HTML templates and JavaScript views, respectively. This facilitates clean separation of presentation and logic:
  • data-tpl: Used with the $cms.behaviors.initializeTemplates function and PARAMS_JSON tempcode directive to bind JavaScript logic to HTML templates.
  • data-view: Used with the $cms.behaviors.initializeViews function to associate JavaScript view classes (inheriting from $cms.View) with specific HTML elements.

View

Question What are the advantages of using Composr's JavaScript libraries?
Answer Composr's JavaScript libraries like $cms, $util, and $dom offer several advantages:
  • Organization: They provide a structured way to access Composr-specific functionalities, avoiding global namespace pollution.
  • Abstraction: They encapsulate common tasks, simplifying DOM manipulation, form handling, and interaction with Composr's UI.
  • Consistency: They offer a consistent API across different parts of Composr.

View

Question How does Composr implement the Model-View-Controller (MVC) pattern?
Answer
  • Model/API: The sources directory primarily houses scripts forming the Model/API, handling data logic and business rules.
  • View: Templates in themes/default/templates represent the View, responsible for presenting data to the user. Comcode pages can also be considered part of the View.
  • Controller: Entry scripts like index.php and site/dload.php act as front controllers, directing requests. Modules and blocks, residing in */pages/modules and sources/[mini]blocks, respectively, serve as controllers, managing user interactions and determining which View to render.

View

Top 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.

View

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.

View

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.

View

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.

View

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.

View

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.

View

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.

View

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.

View

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.

View

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.

View