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.
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.
How do I install geo-location data for Composr statistics?
Answer
Geo-location data installation is usually automatic during the Composr installation process. If not, you can manually install it by navigating to Admin Zone > Audit > Site statistics > Install geolocation data. This action will reschedule the installation task. If you don't see this option, the geo-location data is already installed.
What tools and strategies can be used for staff training and development?
Answer
While Composr itself doesn't provide built-in training features, several approaches can be used for staff development:
Documentation & Tutorials: Utilize the extensive Composr documentation and tutorials available online to familiarize staff with the platform's functionalities.
Mentorship: Pair experienced staff with newcomers to provide guidance and support during the initial learning phase.
Private Forums & Chat: Create dedicated communication channels where staff can exchange knowledge, ask questions, and share best practices.
Regular Meetings: Conduct regular staff meetings to discuss updates, share information, and address any arising challenges.
External Resources: Leverage external resources like online courses or workshops focused on relevant skills, such as content management or community moderation.
By investing in ongoing staff training and development, communities can ensure their teams possess the necessary knowledge and skills to perform their roles effectively and contribute to the platform's overall success.
