Powerful parental controls configuration to comply with necessary online safety and privacy laws
Set different rules for different regions so you can comply with varying laws across the globe (according to the region members set on their profile)
Automatically generates a portion of the automatic Privacy Policy block depending on your configuration; also define your own custom text (e.g. stating the laws which enforce each rule you set)
Optionally require and/or lock down from editing certain core profile fields for compliance: date of birth, time zone, and region
Optionally enforce IP address geo-location to match the country defined on a member's profile (useful for sites featuring region-locked content)
Parental consent: require the legal guardians of members under a certain age to fill out and send in a consent form (e-mailed to the child) to gain access
Lockout: prevent anyone under a certain age from logging in at all until they are of age
Legends of Nor'Ova is a website / database based on the table-top role-playing game of the same name. It contains Wiki+ pages and catalogues with a vast amount of knowledge regarding the game and its resources. It features a customized theme / templates. And it has a community for people to discuss the game.
Super Tilted is a team of pinball enthusiasts who develop original digital pinball tables for the Visual Pinball X platform. This website showcases their releases and ongoing (public) projects. All tables are free to download. And people can request to join the team.
This site has some secret sauce behind the scenes: a custom block for Scorbit leader-boards (pinball scores), and some webhooks to alert the team in their Discord of certain site activity. It also takes advantage of the Support Tickets e-mail integration and using zones for "sub-sites" for each released pinball table.
Technically, Wiki+ pages cannot be moved because they don't have a fixed location within the network structure. Creating child links forms a path, not a strict hierarchy. However, you can manipulate the breadcrumbs by ensuring only one path leads to a page.
Yes, Wiki+ includes a revision history feature accessible through the page edit screen. This feature allows you to view a log of edits, see changes highlighted in tooltips, and revert to previous versions of a page as needed.
How can I view the complete tree structure of my Wiki+?
Answer
You can access a view of the complete Wiki+ tree structure through the designated option in the admin panel. However, it's important to note that this view will reflect guest access permissions. Some pages may be hidden if they are restricted to specific user groups.
Wiki+ offers several features to help you moderate user contributions and maintain the quality of information:
Email Notifications: When a new post is submitted, an email notification is sent to the designated staff address, alerting you to new contributions.
Permissions Control: You can configure permissions to determine whether regular users can create new pages or only contribute through posts.
Page History: The revision history feature allows you to track edits made to pages and revert to previous versions if necessary.
Composr Moderation Tools: Wiki+ integrates with Composr's site-wide moderation features, providing additional tools for monitoring and managing user contributions.
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.
