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.

The telemetry service is being re-built and will not work for any sites until v11 beta7. Please report all Composr errors you encounter to the tracker to ensure the developers receive them.

Featured Sites: A-Z Index

H

Composr CMS: Your Data, Your Privacy, Your Control - Composr CMS: Your Data, Your Privacy, Your ControlComposr CMS: Your Data, Your…

Composr CMS:
Your Data, Your Privacy, Your Control - Composr CMS: Your Data, Your Privacy, Your Control

Earth & Sky

Legends of Nor'Ova

Legends of Nor'Ova

PDStig, LLC

Super Tilted

Saving Wallden

Newest 10 Entries

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.

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.

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.

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.

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.

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.

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.

Question	What is SEO and why is it important for my Composr website?
Answer	SEO is the practice of optimizing your website to rank higher in search engine results pages (SERPs). By improving your SEO, you increase the visibility of your website, driving more organic (non-paid) traffic to your content.

Question	How can I edit the metadata in Composr?
Answer	Composr provides several ways to customize your metadata: Site-wide Settings: You can configure default metadata for your entire site in the Admin Zone under Setup > Configuration > Site options. Content-Specific Settings: When adding or editing content like Comcode pages or news posts, Composr provides fields for customizing titles, descriptions, and keywords specific to that content under the "Metadata" section. Automatic Detection: Composr can automatically generate metadata by analyzing your content, but it's generally recommended to refine these suggestions manually for best results.

Question	Should I trust agencies that promise top search engine results?
Answer	No; be wary of agencies guaranteeing top rankings for any desired keyword. Achieving top results for competitive terms requires significant effort, expertise, and often, an ongoing strategy. Focus on agencies that prioritize ethical "white-hat" SEO techniques like creating valuable content, optimizing website structure, and building natural backlinks. Avoid those employing "black-hat" methods that can lead to penalties from search engines.

Top 10 Entries

Website	PDStig, LLC
Screenshot
Short Description	This is an informational site / portfolio for PDStig, LLC, the company run by one of Composr's lead developers, Patrick Schmalstig.

Website	Composr CMS: Your Data, Your Privacy, Your Control - Composr CMS: Your Data, Your Privacy, Your Control
Screenshot
Short Description	This is the main website for Composr CMS version 11. It runs the latest build of v11. Currently it is just a placeholder but will soon replace compo.sr when v11 becomes stable.

Question

Should I use the bleeding edge releases or the git repository?

Answer

That depends on several factors. Here are some pros and cons of each:

Bleeding edge releases	Git repository (v11 branch)
Easier to set up and use, and does not require knowledge of git	Harder to set up and use unless you are familiar with git; must routinely run the file integrity check, database upgrade tool, and check database schema tools in the upgrader after pulling
More stable, but less frequent updates	Less stable, but more frequent updates (almost daily!)
Only contains core code and addons unless you manually install non-bundled addons; non-bundled addons must be manually updated	Contains all core code and non-bundled addons; non-bundled addons are updated with pulls (though you will need to check file/database integrity often and check blocks/modules for available upgrades)
Ability to test the upgrader / upgrading between new v11 versions	Not able to effectively test the upgrader because git pull might load in and update new code early before the release is available
Always contains the latest files.bin and db_meta.bin because these are compiled with every release	Does not always contain the latest files.bin and db_meta.bin. Therefore, file and database integrity may report false-positives.
Intended for general user testing	Intended for developers / developer testing: * special run-time checks are enabled for extra debugging (if the .git directory exists in the install) * contains the automated test suite for running tests

Click here to access the git repository.

Question	Can I switch a v11 install from git over to using the releases from composr.app?
Answer	It is not recommended you do this because you may run into issues. For example, some changes were made in crypto_master.php and data/upgrader2.php prior to the first v11 alpha. These changes will result in a broken upgrade unless you already pulled these changes from git. Similar situations could happen in the future as well. It is recommended you either discard the git install and use a fresh install from the Downloads, or to maintain a git install and a bleeding-edge release install separately. Do not combine the two.

Question	Should I update my non-bundled addons after updating to a newer release of version 11?
Answer	Absolutely! Frequent changes may be made to both bundled and non-bundled addons. Bundled addons will be updated via the upgrader. For non-bundled addons, you will have to update them through the addons management screen (Admin Zone > Structure > Addons). You will be informed which ones need updated. Once version 11 reaches release candidate, we do not expect frequent updates to non-bundled addons anymore. But it is still good practice to check after every update.

Question	Can I upgrade a version 10 site to version 11?
Answer	Yes, for basic non-custom v10 sites. However, expect some issues to arise in the process. And please report those issues to the tracker. For v10 sites with non-bundled addons or customisations, upgrading to v11 will likely break the site until you update the non-bundled addons or temporarily remove the customisations. We aim to have the upgrader fully functional for a large majority of types of sites and for sites using non-bundled addons by the time version 11 reaches release candidate stage. We do not recommend upgrading production v10 sites at this time until v11 reaches stable.

Question	Can I upgrade a previous version 11 release to a newer one using the upgrader?
Answer	Yes (probably). Always remember especially during alpha and beta phases that things can break. Please make backups first. And let us know on the issue tracker if an issue occurs. Note: You cannot upgrade from 11 alpha to 11 beta without first upgrading to 11.alpha4 (if you are not already on 11.alpha4).

Question	What are the current release plans for version 11?
Answer	As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site. We will be releasing several beta versions in the beta phase. We do not know when we will be able to release the first Release Candidate or stable versions at this time. These plans are all subject to change without notice.

Question	Why is there a separate website for version 11?
Answer	That is explained in detail in this news article on compo.sr including the migration plans and implications.

Statistics

Forum statistics:	45 topics, 14 posts, 2 members Our newest member is test