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 can I ensure my website complies with email marketing laws?
Answer	Email marketing laws like CAN-SPAM protect recipients' rights to unsubscribe. Your website must include a clear 'List-Unsubscribe' header in every email, offer an easy unsubscribe process, and respect unsubscribe requests promptly. Composr provides built-in mechanisms, including an unsubscribe endpoint and support for the List-Unsubscribe header, to facilitate compliance.

Question	What are my responsibilities regarding user privacy?
Answer	You must have a comprehensive privacy policy that details the personal data you collect, its usage, and if it's shared with third parties. Laws like GDPR have strict requirements, including logging data access, data purging, and security measures. California law mandates specific elements in your policy, like handling "Do Not Track" requests and a clear process for communicating changes. Composr has an automatic Privacy Policy generator block to help you get started. This is used by default.

Question	How can I create effective website rules?
Answer	A well-defined rules page is crucial for setting expectations for user behavior and outlining consequences for violations. It should cover a range of offenses with appropriate punishments, reference relevant laws, and assign legal responsibility to users. Composr provides default rules pages that can be customized, and this page is displayed to users upon joining the site.

Question	What are the key legal considerations for running a website?
Answer	Several legal aspects need careful attention when operating a website, especially for large or corporate sites. These include establishing clear rules and terms of service, adhering to privacy laws like GDPR and California's regulations, managing personal data responsibly, complying with email marketing regulations like CAN-SPAM, ensuring website accessibility, addressing eCommerce regulations, and understanding liability for content and user actions.

Question	How do data-tpl and data-view behaviors work in Composr's JavaScript?
Answer	Composr uses data-tpl and data-view behaviors for associating HTML templates and JavaScript views, respectively. This facilitates clean separation of presentation and logic: data-tpl: Used with the $cms.behaviors.initializeTemplates function and PARAMS_JSON tempcode directive to bind JavaScript logic to HTML templates. data-view: Used with the $cms.behaviors.initializeViews function to associate JavaScript view classes (inheriting from $cms.View) with specific HTML elements.

Question	What are the advantages of using Composr's JavaScript libraries?
Answer	Composr's JavaScript libraries like $cms, $util, and $dom offer several advantages: Organization: They provide a structured way to access Composr-specific functionalities, avoiding global namespace pollution. Abstraction: They encapsulate common tasks, simplifying DOM manipulation, form handling, and interaction with Composr's UI. Consistency: They offer a consistent API across different parts of Composr.

Question	How does Composr implement the Model-View-Controller (MVC) pattern?
Answer	Model/API: The sources directory primarily houses scripts forming the Model/API, handling data logic and business rules. View: Templates in themes/default/templates represent the View, responsible for presenting data to the user. Comcode pages can also be considered part of the View. Controller: Entry scripts like index.php and site/dload.php act as front controllers, directing requests. Modules and blocks, residing in */pages/modules and sources/[mini]blocks, respectively, serve as controllers, managing user interactions and determining which View to render.

Question	Can I translate my content into multiple languages?
Answer	Yes, Composr supports multi-language content. You can enable this feature by: Installing multiple language packs: Make sure you have at least two language packs installed. Enabling the Conversr multi-language option: Go to Admin Zone > Setup > Configuration > Site options > Internationalisation. Running a Commandr command: Execute the necessary command to set up the database structure for multi-language content (unless you already enabled Support content translations when installing). Once enabled, you can translate your content into different languages and allow visitors to choose their preferred language.

Question	My language uses gendered descriptors. How can I handle this in Composr?
Answer	Composr offers solutions for languages with gendered descriptors: Template editing: You can modify templates to use different language strings based on user gender. This involves adding Tempcode logic to dynamically select the appropriate string. Custom Profile Fields: Create a Custom Profile Field for "Gender" and use it to conditionally display gendered language strings in templates. These methods allow for flexible handling of gendered language variations.

Question	What are language strings, and how are they used?
Answer	Language strings are phrases or pieces of text used throughout Composr. They're identified by unique codenames, like WELCOME_MESSAGE. These strings are stored in .ini language files and used to display text in the user interface. By translating language strings, you change the text displayed on your website without modifying the underlying code.

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