Composr follows a rolling release model. This means:
New major/minor versions are released as they are ready.
Patch releases, primarily containing bug fixes, are only released for the latest supported major/minor version branch.
Users are responsible for staying updated to the latest release or applying necessary hotfixes.
This policy allows developers to focus resources on the latest versions and encourages users to leverage the ongoing improvements. You can find the release status on the Composr maintenance status page.
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.
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.
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.
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.
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.
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.
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.
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.
What are cleanup tools in Composr and how do I use them?
Answer
Cleanup tools assist with website maintenance by deleting unnecessary data and optimizing database tables. They are divided into "De-cachers" and "Optimizers". You can access them through:
PHP-Info provides a comprehensive overview of your PHP configuration. You can access it within Composr by navigating to Admin Zone > Tools > PHP-Info / Server Checks.
This page also provides additional useful server information.
What is the purpose of the Health Check feature in Composr?
Answer
The Health Check feature in Composr proactively identifies potential issues that may affect your website's performance, security, and overall health. It performs various checks and alerts you to problems like:
Broken links and forms
Security vulnerabilities
Outdated software versions
Server performance issues
Email configuration problems
The Health Check can be run manually or scheduled to run automatically and send e-mail notifications of results.
How can I use Content Delivery Networks (CDNs) to enhance my website?
Answer
CDNs improve website performance by serving content from geographically distributed servers, reducing latency and server load. You can leverage CDNs for your Composr website by:
Configuring the CDN option in Composr with a comma-separated list of CDN domain names.
Ensuring your files are mirrored on the CDN servers.
Utilizing the CDN_FILTER directive and symbol to control what content is served via CDN.
What is rate limiting and how can I enable it in Composr?
Answer
Rate limiting prevents server overload by restricting the number of requests allowed from a single IP address within a specific timeframe. To enable Composr's built-in rate limiting, add the following to your _config.php file:
Static caching drastically improves performance by serving pre-generated pages to bots and guests. This works because these users typically don't require dynamic content. To enable it:
Go to the Installation Options editor (yourbaseurl/config_editor.php). You will need your maintenance password.
Activate the static cache option.
Composr intelligently determines what to cache, and you can further control this via options within the Installation Options. Be aware that enabling static caching may disable eCommerce features for guests unless specifically configured.
If you're having issues with notifications, here are some troubleshooting steps:
Check Email Logs: View the email log (Admin Zone > Audit > E-mail queue/log) to see what notifications have been sent.
Use the SU Feature: Impersonate a member using the SU feature (described in the "Testing access and privileges" tutorial) to view their notification settings and confirm they are set up correctly.
Enable Carbon-copy Email: Configure a "Carbon-copy e-mail address" in the configuration settings to receive copies of all outgoing emails, including notifications. This helps you monitor email delivery.
Verify System Scheduler: Ensure the system scheduler is configured correctly if members are not receiving digest emails.
Check Digest Settings: Confirm that "Enable digest notifications" is enabled in the Messages configuration settings.
Review "Safety listing limit": If a notification has too many categories, members might not see the full selection tree. Adjust the "Safety listing limit" in the configuration settings if necessary.
Can I control which notifications members receive?
Answer
Yes, you can control notification settings through two mechanisms:
Notification Defaults: You can set default notification preferences for all members. You can enable or disable specific notifications and choose the delivery method (Admin Zone > Setup > Notification defaults).
Notification Lock-down: You can force members to receive or prevent them from receiving certain notifications (Admin Zone > Setup > Notification lock-down). This allows you to enforce specific notification policies and manage email volume.
