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 the general courtesy guidelines for interacting with the Composr community?
Answer
  • Understand that Composr is developed and maintained by volunteers who dedicate their time to the project.
  • Refrain from demanding free support or expecting developers to work on specific schedules.
  • Avoid placing undue pressure on volunteers or pushing them beyond their capacity.
  • Approach the community with respect and a collaborative spirit.
  • Remember that offering financial sponsorship for desired features can accelerate development.

View

Question How can I provide design feedback for Composr?
Answer Constructive design feedback is valuable. To provide effective feedback:
  • Be specific and detailed. Identify particular issues and provide clear examples.
  • Offer solutions. Suggest improvements or provide mockups demonstrating your ideas.
  • Avoid vague statements. General comments like "it looks dated" are unhelpful.
  • Understand design constraints. Consider factors like modularity, generality, feature density, compatibility, performance, and the subjective nature of design.
Directly reporting specific design bugs to the tracker or redesigning Composr interfaces yourself are excellent ways to contribute.

View

Question How do I make a feature suggestion for Composr?
Answer You can suggest features through the tracker or the Report Issue Wizard. When making a suggestion:
  • Be comprehensive and self-contained. Provide all necessary information and context for the developers to understand your suggestion.
  • Focus on widely beneficial features. Esoteric suggestions are less likely to be implemented.
  • Understand developer constraints. Feature development depends on factors like developer availability, funding, and project strategy.
  • Consider sponsoring features. Financial contributions can prioritize the development of desired features as it affords developers the time to implement it.

View

Question How do I report an emergency problem with my Composr site?
Answer Emergency problems are events that have significantly and suddenly affected your website's functionality due to legitimate bugs or undocumented usability issues. To report these:
  • Open a tracker issue explaining the problem and providing as much detail as possible (mark it as a major bug).
  • Help the developers help you. Provide access to your site (see the software feedback tutorial for more information), describe the exact situation, and avoid protracted back-and-forth communication.
  • Take backups before upgrading. This allows for easier recovery in case of problems.
Remember that bug fixing is not a free service. While developers are committed to Composr's stability, maintaining backups and practicing restoration procedures is your responsibility.

View

Question How can I get support for Composr?
Answer The community forum is an excellent resource for support. Users can help each other out with various problems. However, please remember that there's no guarantee of free professional support. If you need immediate or guaranteed assistance, consider hiring a professional developer.

View

Question I'm getting a lot of spam on my site. What can I do?
Answer Composr offers various anti-spam measures. Refer to the Anti-spam settings tutorial for advice on configuring these settings. If you believe there's an issue with the anti-spam system itself, report it to the issue tracker. Do not report general spam incidents.

View

Question My website is experiencing performance issues. What should I do?
Answer If you are experiencing performance issues, first identify the specific problem with your web host's help. Composr provides tools to manage database size, bandwidth, and disk I/O. However, high request volume or CPU usage may require server upgrades like a VPS or dedicated server.

If your web host complains about resource usage, gather detailed information from them, including specific URLs causing problems and resource usage metrics. If their limits are unreasonable, consider switching web hosts.

View

Question How do I report a security problem?
Answer Security problems must be reported privately. You can do this by marking the issue as 'Private' on the issue tracker (if you use the Report Issue Wizard, it will do that automatically when you select security-hole). Publicly disclosing security holes is irresponsible and may result in penalties. The core developer team will disclose the issue after a patch is released.

View

Question How do I report a bug in Composr?
Answer Every bug, no matter how small, should be reported. You can report bugs using the Report Issue Wizard or directly through the issue tracker. There is also a link to report bugs on your Admin Zone Dashboard where the version information is located. And when clicking that link, you can view open issues specific to your version of Composr.

When reporting a bug, be sure to:
  • Check for duplicates: Make sure the bug hasn't already been reported.
  • Report bugs individually: Each issue should be reported separately for better tracking and resolution.
  • Verify it's a Composr bug: Issues with third-party addons and code should be reported to their respective developers.
  • Consult the FAQ and tutorials: Check for common problems and solutions, particularly server configuration issues.
  • Provide comprehensive information: Include a clear and specific title, detailed steps to reproduce the problem, your browser version, Composr version, error messages, stack traces (if available), and any other
relevant details.
  • Use clear and concise language: Write in proper English, use correct terminology, and avoid vagueness.
  • Be respectful and patient: Remember that developers are volunteers and may not respond immediately.

View

Question What is the role of robots.txt in SEO?
Answer The robots.txt file provides instructions to search engine crawlers about which parts of your website they should and should not access. You can customize the robots.txt file to prevent sensitive content from being indexed or to guide crawlers toward the most important areas of your site.

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