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.
When viewing an image or video in a gallery, visitors can initiate a slide-show that automatically cycles through subsequent entries. The slide-show can be paused with a click or keypress. The default slide-show speed can be adjusted by modifying the GALLERY_ENTRY_SCREEN.tpl template.
Watermarks are semi-transparent images overlaid on gallery images to mark their origin or deter unauthorized use. When you add or edit a gallery, you can choose to apply watermarks to the corners of images. Watermarking applies permanently to the uploaded image. Composr uses a reverse tree structure for watermarks: if a sub-gallery doesn't have a watermark defined, it inherits the watermark from its parent gallery.
Yes, members with the "have personal galleries" permission can create their own galleries. These personal galleries are displayed under designated "Personal category container" galleries. They also show up in a tab on the member's profile. Members can only add content to their own galleries unless they have the "Submit to categories belonging to other members" permission.
Rep-images, short for "representative images," are thumbnails that represent a gallery when it's displayed within a list of galleries. They offer a visual preview of the gallery's contents. You can set a rep-image when adding or editing a gallery, or when adding an image to a gallery.
You can import images in bulk using a CSV file. The file should be named descriptions.csv and placed in the uploads/galleries directory. The first column should contain filenames (without the path), and the second column should contain descriptions. The filenames should correspond to images also located in the uploads/galleries directory. Composr will automatically match the descriptions to the images during import.
Composr Galleries are a system for storing, organizing, and displaying images and videos. They function like categories, allowing you to group related media together. Galleries can be structured hierarchically, with sub-galleries nested under parent galleries, similar to a folder system. Each gallery has settings that control its appearance and behavior.
