What are orphaned pages and how should I handle them?
Answer
Orphaned pages are pages that exist within the Wiki+ database but are not linked to the main tree structure. These pages are not accessible through the tree navigation but can still be reached through direct links or cross-linking.
Orphaned pages are not necessarily problematic. They can be intentional if you prefer to link pages using the wiki-style syntax instead of a rigid tree hierarchy. You have the flexibility to choose the linking method that best suits your content organization.
While Wiki+ shares similarities with traditional wikis, it provides two key distinctions:
Optional Post Contributions: Wiki+ allows users to contribute short snippets of information (posts) directly on pages, enriching the content without formally editing the page itself. This feature is optional and can be enabled or disabled as needed.
Optional Tree Structure: Unlike standard wikis that rely solely on cross-linking, Composr's Wiki+ offers the flexibility of organizing pages within a hierarchical tree structure. This structure can be used in conjunction with or as an alternative to cross-linking.
Wiki+ is a feature in Composr that allows you to create a collaborative, tree-structured database of information. It functions similarly to a traditional wiki but offers enhanced features such as post contributions, a hierarchical structure, and moderation capabilities.
Can I integrate a dedicated issue management system with Composr?
Answer
While Composr doesn't have a built-in issue tracker, a non-bundled addon (cms_homesite_tracker) provides an integrated, modified version of Mantis. Additionally, the Support Ticket system can function as a basic private issue tracker using features like Post Templates.
How can I restrict access to the support system to specific users?
Answer
Utilize Composr's page access permissions to control who can access the Support Ticket page. This ensures only authorized users can submit support requests.
You can also control permissions based on ticket type when adding or editing a ticket type. Make sure if you go this route that the Support Ticket page permissions are very liberal (e.g. allow anyone to access, or just restrict to guests if you will never allow guests to make tickets). Otherwise, some people cannot make tickets even if they have permission on the type.
How does Composr handle email integration for support?
Answer
Composr can integrate with email for ticket management, assuming certain requirements are met:
PHP IMAP extension installed.
Functional PHP mail command (local SMTP server or configured Windows SMTP settings).
Active system scheduler (Cron).
With email integration, users can submit tickets via email, and staff can reply through the system. Composr cleans up email text for ticket clarity and allows forwarding emails to the integrated address for efficient handling.
How can I categorize and prioritize support requests?
Answer
Support Ticket System: Utilize support ticket types, managed in the Admin Zone > Setup > Support tickets. Staff can set individual notifications for different types.
Discussion Forums: Create dedicated subforums for different support categories or priority levels.
Feedback System: The content to which the feedback is attached implicitly categorizes it. For prioritization, subforums can be used.
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.
What is rate limiting and how can I enable it in Composr?
Answer
Rate limiting prevents server overload by restricting the number of requests allowed from a single IP address within a specific timeframe. To enable Composr's built-in rate limiting, add the following to your _config.php file:
Static caching drastically improves performance by serving pre-generated pages to bots and guests. This works because these users typically don't require dynamic content. To enable it:
Go to the Installation Options editor (yourbaseurl/config_editor.php). You will need your maintenance password.
Activate the static cache option.
Composr intelligently determines what to cache, and you can further control this via options within the Installation Options. Be aware that enabling static caching may disable eCommerce features for guests unless specifically configured.
If you're having issues with notifications, here are some troubleshooting steps:
Check Email Logs: View the email log (Admin Zone > Audit > E-mail queue/log) to see what notifications have been sent.
Use the SU Feature: Impersonate a member using the SU feature (described in the "Testing access and privileges" tutorial) to view their notification settings and confirm they are set up correctly.
Enable Carbon-copy Email: Configure a "Carbon-copy e-mail address" in the configuration settings to receive copies of all outgoing emails, including notifications. This helps you monitor email delivery.
Verify System Scheduler: Ensure the system scheduler is configured correctly if members are not receiving digest emails.
Check Digest Settings: Confirm that "Enable digest notifications" is enabled in the Messages configuration settings.
Review "Safety listing limit": If a notification has too many categories, members might not see the full selection tree. Adjust the "Safety listing limit" in the configuration settings if necessary.
Can I control which notifications members receive?
Answer
Yes, you can control notification settings through two mechanisms:
Notification Defaults: You can set default notification preferences for all members. You can enable or disable specific notifications and choose the delivery method (Admin Zone > Setup > Notification defaults).
Notification Lock-down: You can force members to receive or prevent them from receiving certain notifications (Admin Zone > Setup > Notification lock-down). This allows you to enforce specific notification policies and manage email volume.
What notification options are available to members?
Answer
Members can choose from a wide range of notifications, including:
Content Updates: Notifications for new or updated content, such as news articles, forum posts, and gallery images.
Private Messages: Alerts for new private messages received.
Friend Requests: Notifications for new friend requests.
Administrative Actions: Alerts for actions taken by site administrators, such as account approvals or content moderation decisions.
Members can choose to receive notifications via:
Email: Notifications sent directly to their email address.
Digest Email: Combined summaries of activity sent in batched emails. This requires the system scheduler and the digest e-mails configuration option to be enabled.
Private Topics: Notifications delivered as private forum topics.
SMS: Notifications sent as text messages (requires configuration and incurs costs).
Web Notifications: Real-time alerts displayed within the Composr interface.
