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 How do I install geo-location data for Composr statistics?
Answer Geo-location data installation is usually automatic during the Composr installation process. If not, you can manually install it by navigating to Admin Zone > Audit > Site statistics > Install geolocation data. This action will reschedule the installation task. If you don't see this option, the geo-location data is already installed.

View

Question What are the key differences between Google Analytics and Composr statistics?
Answer While there is some overlap, Composr statistics and Google Analytics are complementary tools.

Google Analytics Pros:
  • Offers sophisticated functionality for professional marketers.
  • Integrates with other Google products like AdSense and Search Console.
  • Provides insights based on Google's marketing data, such as visitor demographics.

Google Analytics Cons:
  • Limited to web visit data unless custom programming or complex configuration is implemented.
  • Relies on JavaScript for tracking, which can be blocked by users.
  • Uses tracking cookies, raising privacy concerns and potential GDPR compliance issues.
  • Data is potentially sold to third-party data brokers or used for targeted advertising by Google.
  • Closed-source platform.

Composr Statistics Pros:
  • Server-side tracking, independent of JavaScript and browser configurations.
  • Contextual information and graphs for data beyond web visits (e.g., sales).
  • Enhanced privacy as it only uses IP addresses, session IDs, and member IDs.
  • Complete data control as it is hosted on your website.
  • Open-source addon, fully customizable.

Basic users may find Composr statistics sufficient, while expert marketers might prefer the power of Google Analytics.

View

Question What tools and strategies can be used for staff training and development?
Answer While Composr itself doesn't provide built-in training features, several approaches can be used for staff development:
  • Documentation & Tutorials: Utilize the extensive Composr documentation and tutorials available online to familiarize staff with the platform's functionalities.
  • Mentorship: Pair experienced staff with newcomers to provide guidance and support during the initial learning phase.
  • Private Forums & Chat: Create dedicated communication channels where staff can exchange knowledge, ask questions, and share best practices.
  • Regular Meetings: Conduct regular staff meetings to discuss updates, share information, and address any arising challenges.
  • External Resources: Leverage external resources like online courses or workshops focused on relevant skills, such as content management or community moderation.

By investing in ongoing staff training and development, communities can ensure their teams possess the necessary knowledge and skills to perform their roles effectively and contribute to the platform's overall success.

View

Question How can potential conflicts between staff members be avoided (regarding content moderation)?
Answer Composr incorporates "conflict detection" features to prevent staff from accidentally overwriting each other's work. When multiple staff members attempt to edit the same resource simultaneously, a warning message appears, prompting communication and coordination.

Open communication and transparency are crucial. Encourage staff to share their ongoing tasks and plans with each other to prevent overlaps and potential conflicts. Utilizing shared tools like the staff checklist and private forums can further facilitate coordination.

View

Question What should be considered when assigning roles and responsibilities to staff?
Answer When assigning roles, it's recommended to start new staff with limited responsibilities and gradually increase their authority based on performance and dedication. This fosters a sense of progression and prevents discouragement among existing staff.

Always consider the individual's skills and interests when assigning tasks. For example, someone with strong writing skills might be well-suited for managing content creation, while a technically-minded person could excel at site maintenance.

View

Question How can staff be effectively managed in a Composr community?
Answer Successful staff management requires a mindful approach that prioritizes fostering a positive and productive environment. Key recommendations include:
  • Respect staff limitations: Avoid overwhelming staff with excessive workload or overly ambitious site expansions.
  • Active involvement: Maintain active involvement in overseeing staff activities and ensuring their effective functioning.
  • Open communication: Engage in regular communication, providing feedback, addressing concerns, and recognizing achievements.
  • Foster teamwork: Encourage collaboration and information sharing among staff members.
  • Lead by example: Ensure staff adhere to community rules and demonstrate expected behavior.
  • Empowerment and trust: Grant sufficient freedom and control to enable staff to excel in their roles.

By fostering a supportive and empowering environment, community managers can enable staff to contribute their best efforts and drive the community's success.

View

Question How should staff members be chosen for a Composr-based online community?
Answer Choosing staff for online communities differs from traditional hiring processes due to factors like unpaid positions, varying time commitments, and remote interactions. Focus should be placed on identifying individuals with:
  • Genuine interest: Look for members passionate about the community and its goals.
  • Available time: Ensure potential staff can dedicate sufficient time to fulfill their responsibilities.
  • Relevant skills: Prioritize skills and experience aligned with the specific role requirements.
  • Maturity and discipline: Seek individuals who demonstrate responsible behavior and commitment.
  • Recruitment methods like directly approaching active community members or allowing the Composr points system (or the karma non-bundled addon) to identify dedicated contributors can be more effective than traditional advertising.

View

Question How can content issues be reported and addressed by staff?
Answer Composr's content reporting system, powered by the Tickets addon, allows users to report problematic content to staff. Key features include:
  • Report links: "Report this" links embedded throughout the site enable users to flag content for review.
  • Custom reporting interface: Forums offer a dedicated interface for reporting individual posts.
  • Anonymous reporting: Logged-in users can choose to report content anonymously.
  • Ticket-based management: Reports are automatically created as support tickets, facilitating staff collaboration and record-keeping.
  • Comprehensive report details: Tickets include content title, type, ID, submitter information, an embedded rendering of the reported content, and the reporter's explanation.

This system ensures efficient handling of content issues, allowing staff to address concerns effectively while maintaining a transparent record of actions taken.

View

Question How can staff members collaborate effectively in Composr?
Answer Composr offers various tools to facilitate staff collaboration:
  • Private forums: Dedicated forums with restricted access enable staff to discuss site operations and coordinate activities. Composr installs a staff forum by default in Conversr.
  • Conflict detection: When multiple staff members attempt to edit the same resource simultaneously, Composr displays warnings at the top to prevent accidental overwrites.
  • Staff checklist & dashboard: The Admin Zone dashboard provides a shared checklist for task management, along with space for notes and links.
  • Staff notifications and tickets system: Staff receive notifications about various site events, including support tickets from the "Contact Us" page, allowing for efficient issue handling.
  • Content notes: Staff can embed notes within Comcode or use dedicated "staff notes" fields for various content types to share information and context.
  • Validation and workflows: Content can be intentionally left unvalidated even by staff, enabling secondary checks before publishing. A dedicated workflows addon allows for complex approval processes with multiple stages involving different staff groups.

View

Question What defines a staff member in Composr?
Answer There are two ways to define "staff" in Composr:
  • System-defined staff: This includes administrators and super moderators who have specific privileges within the forum/member system (Conversr).
  • Privilege-based staff: Anyone granted the necessary permissions for a particular situation is considered staff for that context.

Composr prioritizes flexibility by utilizing privileges over fixed roles, allowing for customized staff responsibilities. However, certain features like "staff reply" in tickets inherently rely on a pre-existing understanding of "staff."

View