This is just a placeholder site for Composr CMS 11 beta. It will become the new homesite once version 11 reaches stable. For the current v10 homesite, click here. Please also use the v10 tracker to report v11 issues.
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.
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.
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.
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.
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."
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.
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.
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.
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.
Composr offers three main systems for providing online support:
1. Support Ticket System: This system allows users to submit tickets and staff to respond, track, and resolve them. It features email notifications, ticket categorization and prioritization, staff assignment, and attachment support.
2. Discussion Forums: Conversr, Composr's built-in forum software, can be utilized for support by creating dedicated forums or subforums. Features like post templates and multi-moderations enhance support capabilities.
3. Feedback System: This system allows for comments on various content types, facilitating support directly related to that content.
How can I access the raw data behind the statistics graphs?
Answer
Every graph in Composr offers a spreadsheet export option. This allows you to download the data in a spreadsheet format, enabling detailed manual review or further analysis using third-party tools.
All times in Composr statistics are displayed according to the configured website time zone, regardless of visitor or user account time zones. While this is a limitation due to pre-computation, some graphs displaying hourly stats and country filtering offer insights into local times for manual analysis.
What are the limitations of pre-computed statistics in Composr?
Answer
Pre-computed statistics introduce certain limitations:
Filtering constraints: Limits filtering options to those incorporated in the data structure.
Historical data limitation: To maintain site stability, statistics older than 31 days aren't pre-processed. This may lead to data gaps if the system scheduler malfunctions or statistical data is manually deleted.
