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.
This is an informational website for a Visual Pinball X game in development called "Saving Wallden". The site features the planned game rules, development news, and a download of the game as it is so far.
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.
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
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.
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.
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.
What is the difference between natural and boolean searching?
Answer
Natural search is a more relaxed approach where you type in your search terms and Composr tries to find the most relevant results, even if they don't contain all the words. It's like a Google search.
Boolean search requires more precision and uses operators like "+", "-", and quotation marks to define exactly what you're looking for. For example, searching for "+car -maintenance" will only return results that contain the word "car" but not "maintenance".
There are a few ways to search your Composr website:
Using the search bar in the header: This is the simplest way to search. Just type your search term in the box and click the search button.
Using the 'Search' module: This module offers more detailed search options. You can access it via the 'site:search' page-link (usually under About > Search in the default menu).
From the Forum: Click the 'Search' button on the forum or use the contextual search box on the forum member bar. This will search within your current forum or topic.
For questions with predefined answers, you can mark correct answers by adding [*] after the answer. If no answer is marked correct, the question will require manual marking. You can also use the [UNMARKED] tag after a question to exclude it from scoring.
Quiz questions are inputted in blocks, separated by blank lines. The first line is the question, followed by potential answers on subsequent lines. Different question types are indicated by tags after the question, such as [MULTIPLECHOICE], [MULTIMULTIPLE], [LONG], [SHORT], and [SHORT_STRICT].
Can I create complex, multi-screen quiz interfaces in Composr?
Answer
While Composr's built-in quiz system is excellent for standard formats, creating intricate multi-screen quizzes might require custom development using Composr's decision tree framework or other programming tools. This allows for highly customized quiz structures and advanced branching logic.
Composr enables you to export quiz results to a spreadsheet file, facilitating in-depth data analysis. This is especially useful for manually marked questions, identifying competition winners, and processing data for marketing or research purposes.
Quiz Sets are a helpful organizational feature in Composr. By prefixing quiz names with "Example: ", you can group related quizzes together. This allows for combined scoring and percentage calculations, particularly beneficial for multi-part questionnaires or tests.
Yes, you can reward users with points for successfully passing a test. This incentivizes participation and encourages users to engage with your content.
