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

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.

Top 10 Entries

Question	How can I contribute to translating Composr?
Answer	You can contribute to Composr's internationalization by: Joining the translation team on Transifex: Translate language strings collaboratively with other volunteers. Becoming a language maintainer: Take responsibility for the translation and support of Composr in your native language. Reporting translation issues: If you encounter unclear, incorrect, or duplicated language strings, file bug reports. Providing feedback and suggestions: Share your thoughts on improving the translation process through feature suggestions. Your contributions are valuable and help make Composr accessible to a wider audience.

Question	What is Transifex, and how does it help with translation?
Answer	Transifex is a collaborative online platform used by the Composr community for translation. Its benefits include: Centralized translation efforts: Multiple translators can work on the same project. Improved translation quality: The platform facilitates consistency and accuracy. Simplified language pack creation: You can generate downloadable language pack addons directly from Transifex. We encourage using Transifex for translation to foster collaboration and maintain high-quality translations.

Question	Can I translate images with text on them?
Answer	Yes, you can translate images containing text. In the themes/default/images/ directory, you'll find an EN folder containing images with English text. Copy the EN folder: Create a new folder with the ISO code of your target language (e.g., FR for French). Replace the images: Replace the English images with translated versions. Ensure correct image paths: Update any references to these images in your templates or content to point to the translated versions.

Question	How do I translate the content on my Composr website?
Answer	Once you've installed a new language pack, you can translate existing content by: Editing the content directly: Go to the specific content item (page, news post, etc.) and edit it in the new language. Using the language editor: Access the language editor from Admin Zone > Style > Translate/rephrase Composr to modify language strings used on specific pages. Note that some elements like forum names are not designed to be translated directly. Instead, you should create separate forums for each language.

Question	How do I change the language of my Composr website?
Answer	Composr comes with English as the default language. To change to a different language: Download the language pack: You can download language packs from the Composr website. Install the language pack: Upload the downloaded language pack addon through Admin Zone > Structure > Addons > Import non-bundled addon(s). Change the default language: Go to `http://yourbaseurl/config_editor.php` and set the desired language. Update your profile: If you had a previous language set in your profile, update it to the new language. You can test a language without changing settings by appending &keep_lang=XX to the URL, where XX is the language code (e.g., FR for French).

Question	What should I do after successfully importing data into Composr?
Answer	After importing, if all files like avatars, photos, and attachments have been copied to Composr's directories, you can remove the imported product's directory. However, it's advisable to keep the directory, database, and import session for a few weeks in case any data was not correctly imported and needs further attention. Importing is a complex process, so keeping backups and sources for a while is a good practice.

Question	Where can I get help with the import process?
Answer	The Composr documentation provides extensive information. Additionally, you can seek assistance from experienced Composr developers, including the Composr team if your project allows for professional support.

Question	Can I switch from a third-party forum to Conversr (Composr's built-in forum)?
Answer	Yes, if an importer exists for your current forum software, you can switch to Conversr during the import process. Composr will handle the forum driver switch and remap user IDs, but it's recommended to double-check permissions afterward.

Question	How does the HTML website importer work?
Answer	The HTML website importer is an advanced tool for migrating static HTML websites to Composr. It analyzes the HTML structure to create zones, Comcode pages, and a basic template. It also attempts to fix links and file paths for Composr compatibility.

Question	What is a Composr import session?
Answer	Import sessions track the progress and ID remapping for each import, allowing you to merge multiple sites or resume interrupted imports. This is particularly useful when merging multiple Composr sites into one.

Statistics

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