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.
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).
Composr offers three main systems for providing online support:
1. Support Ticket System: This system allows users to submit tickets and staff to respond, track, and resolve them. It features email notifications, ticket categorization and prioritization, staff assignment, and attachment support.
2. Discussion Forums: Conversr, Composr's built-in forum software, can be utilized for support by creating dedicated forums or subforums. Features like post templates and multi-moderations enhance support capabilities.
3. Feedback System: This system allows for comments on various content types, facilitating support directly related to that content.
How can I access the raw data behind the statistics graphs?
Answer
Every graph in Composr offers a spreadsheet export option. This allows you to download the data in a spreadsheet format, enabling detailed manual review or further analysis using third-party tools.
All times in Composr statistics are displayed according to the configured website time zone, regardless of visitor or user account time zones. While this is a limitation due to pre-computation, some graphs displaying hourly stats and country filtering offer insights into local times for manual analysis.
What are the limitations of pre-computed statistics in Composr?
Answer
Pre-computed statistics introduce certain limitations:
Filtering constraints: Limits filtering options to those incorporated in the data structure.
Historical data limitation: To maintain site stability, statistics older than 31 days aren't pre-processed. This may lead to data gaps if the system scheduler malfunctions or statistical data is manually deleted.
KPIs (Key Performance Indicators) are specific measurements selected for marketing analysis. In Composr, time-series graphs can be added as KPIs. They offer several benefits:
Quick reference: Available on the Admin Zone dashboard staff checklist.
Target setting: Allows setting targets against KPIs, visualized on graphs and in overview summaries.
Notifications: Staff members receive regular notifications regarding target achievement status.
Tracking codes help you identify the sources driving user sessions to your website or associate specific split testing variations with users. Composr offers integrated referral tracking through various means:
URL parameter: The _t URL parameter can contain any custom tracking code, automatically registered by the stats addon.
Recommend addon: This addon automatically includes tracking codes for the referral source, referring member, and the referred page.
Member joining: When a referred member joins, the referring member receives points and a friend request.
Referrals addon: Allows manual tracking code input upon joining and facilitates a referrer reward system.
Stats addon: Generates graphs of tracking codes, including conversion rate measurements.
User lookup tool: Allows checking if a user accessed the site via a tracking code.
Tempcode integration: Inject tracking codes into Tempcode using symbols like {$SET_TRACKING_CODE,some code} or {$SPLIT_TEST,some code,some other code}.
What are the different ways to track events in Composr?
Answer
Composr offers various methods for tracking events:
Inbuilt events: Automatically recorded for actions like form submissions, purchases, newsletter signups, etc.
Tempcode symbol: Use the {$LOG_STATS_EVENT,event} symbol within your templates to track events when the template is displayed.
JavaScript function: Employ the $cms.statsEventTrack JavaScript function to track events from within your JavaScript code.
HTML data attribute: Add data-click-stats-event-track="{ category: 'some event', nativeTracking: true }" to HTML elements. This method acts as a wrapper for the JavaScript function.
URL wrapping: Wrap URLs in links using the {$STATS_TRACK_URL,URL,event} symbol. This approach records events via a redirection script and doesn't rely on JavaScript.
The JavaScript and HTML data attribute methods can also be integrated with Google Analytics events.
