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 customize Composr without modifying the core files?
Answer	Composr offers a robust override system. Instead of altering the original files, create a parallel structure within _custom directories. For example, to modify site/pages/modules/polls.php, place your customized version in site/pages/modules_custom/polls.php. The tutorials outline additional information on how to utilise overrides.

Question	What are the main components of the Composr framework?
Answer	Composr consists of: Modules: PHP files that provide related screens, forming the building blocks of addons. Comcode: Text files containing content written in a simplified markup language. HTML: Files containing standard HTML for web pages. Sources: PHP code files for the core API and functionality. Hooks: PHP files enabling addons to interact and extend each other's functionality. Blocks/Miniblocks: Reusable components for displaying dynamic content within pages. Themes: Folders containing images, CSS, and templates to define the look and feel. Language files: Files holding text strings for multilingual support.

Question	How can I embed third-party widgets into my Composr pages?
Answer	Composr supports embedding widgets from various websites, like Google Maps, Vimeo, and YouTube, by simply pasting the URL. For manually embedding widget code, you can paste it into the HTML source view of the WYSIWYG editor or within Comcode html tags if not using the WYSIWYG editor.

Question	What is the difference between blocks and boxes in Composr?
Answer	Boxes are visual elements that provide a container for content, while blocks are functional units that generate and display dynamic content. Although blocks often appear within boxes in the default templates, they are not inherently tied to any visual representation.

Question	Can I customize the appearance of blocks?
Answer	Yes, you can style blocks by editing the associated templates and CSS. Templates are typically named after the block they represent. For example, the main_news block uses the BLOCK_MAIN_NEWS.tpl template.

Question	How do I create custom filter forms for my content?
Answer	The main_content_filtering block can help you generate filter forms automatically. You can use it to create a default form and then customize the generated Filtercode string to refine the filtering options. Once satisfied, you can either continue using the block or extract the HTML and modify it further.

Question	Where can I use Filtercode and Selectcode in Composr?
Answer	Filtercode is supported in various blocks, such as main_multi_content, main_gallery_embed, and main_cc_embed. It's also actively used in modules like catalogues, downloads, galleries, members, and news. Selectcode is supported in blocks and Comcode tags that explicitly mention it, including the main_multi_content block and the if_in_group Comcode tag.

Question	What is the difference between Filtercode and Selectcode?
Answer	Filtercode is used for querying content based on properties and values, while Selectcode is used for directly specifying a list of IDs or categories to include or exclude. Filtercode offers more complex filtering options, while Selectcode is more straightforward for simple selections.

Question	How can I filter content in Composr?
Answer	Composr provides two filtering systems: Filtercode and Selectcode. Filtercode is used for selecting content based on defined filters, such as field values, ratings, or keywords. It utilizes a syntax of comparisons, separated by commas, where each comparison specifies a field and a matching condition. Selectcode is a simpler syntax for specifying a list of IDs or categories to include or exclude from the results. It uses a comma-separated list of match-specifier tokens, such as individual IDs, ranges, or wildcard characters.

Question	What are blocks in Composr and how can I use them?
Answer	Blocks are dynamic elements that can be inserted into Comcode pages to add interactive and data-bound functionality to your website. They are essentially reusable components that automatically generate content, such as recent forum posts or information about the logged-in user. You can add blocks to your pages using the block construction assistant, which allows you to select from a list of available blocks, set their parameters, preview them, and generate the necessary Comcode.

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