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.
Composr offers three main systems for providing online support:
1. Support Ticket System: This system allows users to submit tickets and staff to respond, track, and resolve them. It features email notifications, ticket categorization and prioritization, staff assignment, and attachment support.
2. Discussion Forums: Conversr, Composr's built-in forum software, can be utilized for support by creating dedicated forums or subforums. Features like post templates and multi-moderations enhance support capabilities.
3. Feedback System: This system allows for comments on various content types, facilitating support directly related to that content.
How can I access the raw data behind the statistics graphs?
Answer
Every graph in Composr offers a spreadsheet export option. This allows you to download the data in a spreadsheet format, enabling detailed manual review or further analysis using third-party tools.
All times in Composr statistics are displayed according to the configured website time zone, regardless of visitor or user account time zones. While this is a limitation due to pre-computation, some graphs displaying hourly stats and country filtering offer insights into local times for manual analysis.
What are the limitations of pre-computed statistics in Composr?
Answer
Pre-computed statistics introduce certain limitations:
Filtering constraints: Limits filtering options to those incorporated in the data structure.
Historical data limitation: To maintain site stability, statistics older than 31 days aren't pre-processed. This may lead to data gaps if the system scheduler malfunctions or statistical data is manually deleted.
KPIs (Key Performance Indicators) are specific measurements selected for marketing analysis. In Composr, time-series graphs can be added as KPIs. They offer several benefits:
Quick reference: Available on the Admin Zone dashboard staff checklist.
Target setting: Allows setting targets against KPIs, visualized on graphs and in overview summaries.
Notifications: Staff members receive regular notifications regarding target achievement status.
Tracking codes help you identify the sources driving user sessions to your website or associate specific split testing variations with users. Composr offers integrated referral tracking through various means:
URL parameter: The _t URL parameter can contain any custom tracking code, automatically registered by the stats addon.
Recommend addon: This addon automatically includes tracking codes for the referral source, referring member, and the referred page.
Member joining: When a referred member joins, the referring member receives points and a friend request.
Referrals addon: Allows manual tracking code input upon joining and facilitates a referrer reward system.
Stats addon: Generates graphs of tracking codes, including conversion rate measurements.
User lookup tool: Allows checking if a user accessed the site via a tracking code.
Tempcode integration: Inject tracking codes into Tempcode using symbols like {$SET_TRACKING_CODE,some code} or {$SPLIT_TEST,some code,some other code}.
What are the different ways to track events in Composr?
Answer
Composr offers various methods for tracking events:
Inbuilt events: Automatically recorded for actions like form submissions, purchases, newsletter signups, etc.
Tempcode symbol: Use the {$LOG_STATS_EVENT,event} symbol within your templates to track events when the template is displayed.
JavaScript function: Employ the $cms.statsEventTrack JavaScript function to track events from within your JavaScript code.
HTML data attribute: Add data-click-stats-event-track="{ category: 'some event', nativeTracking: true }" to HTML elements. This method acts as a wrapper for the JavaScript function.
URL wrapping: Wrap URLs in links using the {$STATS_TRACK_URL,URL,event} symbol. This approach records events via a redirection script and doesn't rely on JavaScript.
The JavaScript and HTML data attribute methods can also be integrated with Google Analytics events.
