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 restore my Composr website from a backup?
Answer	Composr backups come as .tar or .tar.gz files. Extract the archive using an extraction program like 7-zip or your web hosting control panel. To restore a full backup: Upload the extracted files to your webserver, overwriting the existing files. Run the included restore.php script in your browser. This script will restore the database from the restore_data.php file. To restore incremental backups: Restore the initial full backup. Sequentially extract and overwrite files from each incremental backup over the restored full backup. The last extracted restore_data.php will contain the latest database state. Run restore.php to restore the final database version.

Question	What alternative backup strategies are available?
Answer	Many web hosting control panels include built-in backup features that operate at the system level, often offering higher reliability than web-based scripts. Ensure you back up both files and the database. For database backups, you can use tools like phpMyAdmin, which allows you to export your database as a .sql file.

Question	How do I create a backup of my Composr website?
Answer	Composr offers a built-in backup addon accessible from Admin Zone > Tools > Backups. You can choose between full, incremental, and database-only backups. Full backup: Backs up all files and folders within the Composr installation directory, including the database. Incremental backup: Backs up only new or changed files since the last backup, resulting in smaller backup files. Database backup only: Backs up only the database. The addon allows scheduled backups or manual backup generation. It is recommended to download backups to a location outside your web server for better security. Note: The Composr backup addon is limited by server-side PHP capabilities and might not always be reliable. Consider using alternative backup strategies offered by your web hosting control panel for increased reliability.

Question	Why are backups necessary for my Composr website?
Answer	Disasters like hard disk failures, data corruption, and unexpected errors can happen at any time. A good backup strategy helps you recover your website and its data in case of such events. Backups can also help you roll back to a previous state if needed, such as after a failed upgrade or accidental changes.

Question	How can I control the privacy of member profile fields?
Answer	You can control the privacy of member profile fields through the "Member privacy controls" configuration option. If you enable the "Extended privacy option control", you can fine-tune visibility settings for each field. Otherwise, you can set simple access levels (e.g., not at all, to members, to friends, to everyone) for each field.

Question	What is the difference between a Composr member and an author?
Answer	A member is someone who has created an account on your Composr website and can log in. They have a unique member ID and username, and can interact with the site's features. An author is someone who creates content for the site. They may or may not be a member. For example, you might have an author who submits articles via email but never actually visits or joins the website.

Question	What advanced techniques are available for dealing with persistent spammers who repeatedly create new accounts?
Answer	Composr's advanced banning features target sophisticated human spammers. Automatic bans can be configured to block users based on specific strings in their posts, while reasoned bans display customized messages to banned users, potentially deterring them. These measures, coupled with the ability to investigate users via IP address analysis, offer robust tools for managing persistent threats. You can configure advanced banning under Admin Zone > Security > Configure advanced banning.

Question	How does Composr handle user banning and what options are available?
Answer	Composr offers various banning mechanisms. You can ban members by editing their accounts (ban member tick box), preventing logins while still allowing guest access. IP address banning blocks access from specific IP addresses or ranges (Admin Zone > Security > Members > Investigate user to see their IP addresses and flag certain ones for banning). You can also restrict member submissions, or you can effectively "suspend" users by assigning them to a usergroup with minimal privileges (e.g. probation).

Question	What is the "Warn Member" form and how can I use it to handle rule violations?
Answer	The "Warn Member" form provides a centralized interface for addressing user misconduct. You can issue formal or off-the-book warnings, apply punitive actions like IP bans, usergroup changes, or probation, and even delete content or charge points. This form allows you to document reasons for actions, improving transparency and consistency in moderation. This tool can be accessed on a member's profile as staff, under Audit > Warn member. You can also review their warnings history on their "Standing" tab.

Question	How does Composr track user activity?
Answer	Composr logs IP addresses for various actions like guest posting, page views, and content submissions. This data helps identify potential spammers and track user behavior. The "Investigate user" module provides tools to analyze IP addresses and gather additional information about suspicious activity.

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