Gift points are a separate points balance that can only be sent to other members as gifts. They cannot be spent directly or used in escrow transactions.
Gift points are earned daily based on usergroup membership and replenish independently of the regular points balance. When a member sends gift points, they become regular points for the recipient.
Yes, members can send points to each other as a token of appreciation, reward for a service, or as part of an agreement using the Points Escrow system.
Points are typically awarded immediately upon content submission to encourage participation. However, forum posts requiring validation only earn points after approval to deter spam. To further encourage high-quality content, consider using the "awards" addon to reward exceptional contributions.
Can I reward members who use specific browsers or operating systems?
Answer
Yes, Composr allows you to configure bonus points based on browser/platform criteria. You can set bonus points for members using Open Source browsers, specific operating systems, or even those who have enabled privacy features like "Do Not Track" (DNT) or "Global Privacy Control" (GPC).
What's the difference between points balance and rank points?
Answer
Points balance refers to the number of points a member currently has available to spend. This is the 'liquid' currency they can use for various actions.
Rank points represent the total points a member has accumulated throughout their time on the website. These points determine the member's rank, which can grant access to additional privileges and act as a status symbol.
What are cleanup tools in Composr and how do I use them?
Answer
Cleanup tools assist with website maintenance by deleting unnecessary data and optimizing database tables. They are divided into "De-cachers" and "Optimizers". You can access them through:
PHP-Info provides a comprehensive overview of your PHP configuration. You can access it within Composr by navigating to Admin Zone > Tools > PHP-Info / Server Checks.
This page also provides additional useful server information.
What is the purpose of the Health Check feature in Composr?
Answer
The Health Check feature in Composr proactively identifies potential issues that may affect your website's performance, security, and overall health. It performs various checks and alerts you to problems like:
Broken links and forms
Security vulnerabilities
Outdated software versions
Server performance issues
Email configuration problems
The Health Check can be run manually or scheduled to run automatically and send e-mail notifications of results.
How can I use Content Delivery Networks (CDNs) to enhance my website?
Answer
CDNs improve website performance by serving content from geographically distributed servers, reducing latency and server load. You can leverage CDNs for your Composr website by:
Configuring the CDN option in Composr with a comma-separated list of CDN domain names.
Ensuring your files are mirrored on the CDN servers.
Utilizing the CDN_FILTER directive and symbol to control what content is served via CDN.
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.
