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.
Structure: Composr's forums follow a hierarchical structure. You can create forum groupings, forums, and sub-forums (and sub-sub-forums etc) in that order of hierarchy.
Strategies: Avoid creating too many forums, which can dilute activity. Start with a few well-defined forums and expand as needed.
Permissions: Use Composr's permission system to control access to forums and features. For example, you can create private staff forums.
Composr provides several tools to help you stay up-to-date with forum activity:
Virtual Forums: Special forums like "Posts since last visit" and "Topics with unread posts" provide filtered views of recent activity.
Read Status: Topics with unread posts are displayed in bold with a jump-to-first-unread link. You can manually mark topics or entire forums as read or unread.
Notifications: You can enable email notifications for specific topics or forums, either manually or automatically based on your activity.
What security measures should I consider for local payments?
Answer
While Composr supports local payments (Authorize.Net), it requires high PCI compliance. Ensure you adhere to the PCI Data Security Standard (PCI DSS) guidelines, including secure coding practices, firewalls, intrusion detection systems, regular security audits, and staff screening.
Composr provides tools for monitoring your eCommerce activities:
Sales list management: Cancel purchases, view sales history, and manage refunds (Admin Zone > Audit > eCommerce > Sales list management).
Charts: Generate profit/loss accounts and cash flow diagrams for specific periods (Admin Zone > Audit > eCommerce, and Admin Zone > Audit > Site statistics).
Manual transactions: Record transactions outside of Composr for accurate accounting (Admin Zone > Audit > eCommerce > Manual transaction).
Monetary payments: Issue refunds through your payment gateway.
Point payments: Manually refund points through the points system.
Cancellations: Cancel purchases in the Admin Zone to allow repurchasing. Remember to manually undo any associated actions (e.g., removing name highlighting).
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.
