Points escrow is a system that holds points securely during transactions involving a written agreement, often for a product or service. This ensures trust and provides a resolution mechanism in case of disputes.
Creating an Escrow: You initiate an escrow on the member's profile points tab, specifying the amount, reason, and any agreement details.
Points Held: The points are deducted from your balance and held by the system.
Agreement Fulfillment: Both parties must mark the escrow as satisfied upon fulfilling the agreement.
Points Release: Once both parties are satisfied, the recipient receives the points.
Disputes: If either party has a dispute, they can dispute the escrow, which then locks it down and notifies a staff member to review and take a resolution action.
Can I create a leaderboard to showcase top point earners?
Answer
Yes, Composr offers a leaderboard block and module to display top point holders. You can customize the leaderboard to show weekly, monthly, or yearly rankings, filter by usergroups, and exclude staff members if desired. This can encourage healthy competition and motivate members to earn points.
Go to Admin Zone > Setup > Leader-boards to create a leader-board.
Staff members with the "Moderate members' points" privilege can directly credit or debit points from members' accounts. This can be used to reward exceptional contributions, refund purchases, or penalize rule violations.
The ledger provides a transparent and immutable record of every point transaction on the website. It ensures accountability and allows members to track their point activity. Members can view their own ledger, and with the appropriate privilege, they can also see the ledgers of others.
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.
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.
How do I report an emergency problem with my Composr site?
Answer
Emergency problems are events that have significantly and suddenly affected your website's functionality due to legitimate bugs or undocumented usability issues. To report these:
Open a tracker issue explaining the problem and providing as much detail as possible (mark it as a major bug).
Help the developers help you. Provide access to your site (see the software feedback tutorial for more information), describe the exact situation, and avoid protracted back-and-forth communication.
Take backups before upgrading. This allows for easier recovery in case of problems.
Remember that bug fixing is not a free service. While developers are committed to Composr's stability, maintaining backups and practicing restoration procedures is your responsibility.
The community forum is an excellent resource for support. Users can help each other out with various problems. However, please remember that there's no guarantee of free professional support. If you need immediate or guaranteed assistance, consider hiring a professional developer.
I'm getting a lot of spam on my site. What can I do?
Answer
Composr offers various anti-spam measures. Refer to the Anti-spam settings tutorial for advice on configuring these settings. If you believe there's an issue with the anti-spam system itself, report it to the issue tracker. Do not report general spam incidents.
My website is experiencing performance issues. What should I do?
Answer
If you are experiencing performance issues, first identify the specific problem with your web host's help. Composr provides tools to manage database size, bandwidth, and disk I/O. However, high request volume or CPU usage may require server upgrades like a VPS or dedicated server.
If your web host complains about resource usage, gather detailed information from them, including specific URLs causing problems and resource usage metrics. If their limits are unreasonable, consider switching web hosts.
Security problems must be reported privately. You can do this by marking the issue as 'Private' on the issue tracker (if you use the Report Issue Wizard, it will do that automatically when you select security-hole). Publicly disclosing security holes is irresponsible and may result in penalties. The core developer team will disclose the issue after a patch is released.
Every bug, no matter how small, should be reported. You can report bugs using the Report Issue Wizard or directly through the issue tracker. There is also a link to report bugs on your Admin Zone Dashboard where the version information is located. And when clicking that link, you can view open issues specific to your version of Composr.
When reporting a bug, be sure to:
Check for duplicates: Make sure the bug hasn't already been reported.
Report bugs individually: Each issue should be reported separately for better tracking and resolution.
Verify it's a Composr bug: Issues with third-party addons and code should be reported to their respective developers.
Consult the FAQ and tutorials: Check for common problems and solutions, particularly server configuration issues.
Provide comprehensive information: Include a clear and specific title, detailed steps to reproduce the problem, your browser version, Composr version, error messages, stack traces (if available), and any other
relevant details.
Use clear and concise language: Write in proper English, use correct terminology, and avoid vagueness.
Be respectful and patient: Remember that developers are volunteers and may not respond immediately.
