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).
How does authentication work with the server-side API?
Answer
Authentication is handled automatically using cookies, similar to regular website requests. If cookies are not feasible, the response parameters device_auth_member_id_cn/device_auth_pass_hashed_cn/device_auth_member_id_vl/device_auth_pass_hashed_vl from the login endpoint can be resent as POST parameters in subsequent requests.
How do I access the server-side API for my mobile app?
Answer
The server-side API can be accessed via HTTP calls to http://yourbaseurl/data/endpoint.php. Results are returned in JSON format. The API utilizes endpoints with a 'hook' name and a 'hook type' categorization. Both REST-style and GET-parameter style requests are supported, with the latter recommended for simplicity.
What is the purpose of the Composr Mobile SDK Toolkit?
Answer
The Toolkit, part of the composr_mobile_sdk addon, aids in mirroring Composr website resources into a mobile app. It includes tools for generating iOS/Android string resources from language files and exporting theme images in a directory structure suitable for iOS/Android app image assets.
To connect to a Composr site, you will need to install the composr_mobile_sdk addon, which is not bundled. This addon provides scripting to generate app assets from the Composr site.
Composr Mobile SDK (CMS SDK) is a toolkit designed for experienced iOS and Android developers to build mobile apps that integrate with a Composr-powered website. It offers both Composr-specific integrations and a collection of standalone utilities for building apps, providing a common base between iOS and Android akin to the PHP and Composr APIs, enabling easier code porting while maintaining a native experience.
Composr follows a rolling release model. This means:
New major/minor versions are released as they are ready.
Patch releases, primarily containing bug fixes, are only released for the latest supported major/minor version branch.
Users are responsible for staying updated to the latest release or applying necessary hotfixes.
This policy allows developers to focus resources on the latest versions and encourages users to leverage the ongoing improvements. You can find the release status on the Composr maintenance status page.
Constructive design feedback is valuable. To provide effective feedback:
Be specific and detailed. Identify particular issues and provide clear examples.
Offer solutions. Suggest improvements or provide mockups demonstrating your ideas.
Avoid vague statements. General comments like "it looks dated" are unhelpful.
Understand design constraints. Consider factors like modularity, generality, feature density, compatibility, performance, and the subjective nature of design.
Directly reporting specific design bugs to the tracker or redesigning Composr interfaces yourself are excellent ways to contribute.
Be comprehensive and self-contained. Provide all necessary information and context for the developers to understand your suggestion.
Focus on widely beneficial features. Esoteric suggestions are less likely to be implemented.
Understand developer constraints. Feature development depends on factors like developer availability, funding, and project strategy.
Consider sponsoring features. Financial contributions can prioritize the development of desired features as it affords developers the time to implement it.
