How can I communicate privately with other members?
Answer
Conversr offers two ways to have private conversations:
Private Topics:
Start a private topic from a member's profile, by clicking "Whisper" on their post and selecting "Quote post to a new Private Topic with this member," or from your account by selecting "Start a Private Topic" and entering the desired username.
Participate in the topic just like a regular forum topic.
You will receive notifications for new posts in your private topics.
Topics can be moved to the "Trash" category or other categories of your choosing for organization.
Inline Personal Posts (Whispers):
Send a private message within a public topic by clicking "Whisper" on a post and selecting "In-topic personal post to this member."
Whispers are visible only to the sender and recipient, and the whispered post is highlighted.
How can I ensure the privacy of personal information stored in my catalogues?
Answer
Composr's privacy system can help manage personal data within catalogues. To leverage it:
Use specific field types: Utilize dedicated field types for sensitive data like member IDs, usernames, emails, IP addresses, and passwords for efficient handling by the privacy system.
Enable "May contain personal information": Mark fields that may contain personal information, enabling the privacy system to identify and handle such data during purging or downloading.
Catalogue breadcrumbs can be customized using XML code (Admin Zone > Structure > Configure breadcrumb overrides). By default, they include the list of catalogues. However, Composr provides default breadcrumb XML that removes this, focusing on the current category hierarchy. Tree catalogues omit the index link, while non-tree catalogues include it.
What is a tree catalogue and how do I create one quickly?
Answer
A tree catalogue has a hierarchical category structure (which can contain sub-categories), similar to the download system. Composr offers a special feature for creating tree catalogues by simply typing the desired categories in a specific format (which is explained and available when adding a new catalogue), which automatically generates the tree structure.
Alternatively, a non-tree catalogue is simpler and only has top-level categories.
Can I customize the look and feel of my catalogue?
Answer
Yes, Composr allows advanced users to customize catalogue appearance through Tempcode programming. This involves using template IF directives to apply specific styles based on the catalogue's name and manipulating template parameters for complex layouts. Alternatively, you can create new template files using the catalogue name in the file to specify complete templates for specific catalogues. Check out the tutorials for more information.
While Composr catalogues offer great flexibility, they can become complex if you need sophisticated data relationships, efficient searching, high data reliability, or advanced customization. In these cases, a programmer's expertise in database design, normalization, and templating can be invaluable.
Catalogues are custom databases you can create within your Composr website. They allow you to define your own records with custom fields and organize them into categories. Think of them as powerful tools for managing various types of content, like a database of books, a directory of businesses, or even a classified ads system.
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.
