What is "pinging" and how does it work in Composr?
Answer
In blogging, "pinging" is an automatic notification sent to blog search engines and other services when you publish a new post. Composr can automatically ping services defined in Admin Zone > Setup > Configuration > Feature options. These services then index your new article, making it searchable.
A default ping service (http://pingomatic.com/ping/?title=title&blogurl=url&rssurl=rss) is pre-configured to relay your ping to numerous other services.
You can customize the ping URL with these placeholders:
title: The article title
url: The article URL
rss: The URL of your news RSS feed
Pinging only occurs for news categories accessible to the public (guests).
How do I schedule a news post to be published at a specific time?
Answer
Once you have enabled the system scheduler (requires the Composr calendar and commandr addons), an advanced scheduling option will appear when adding or editing news posts. By setting a future date and time, your post will remain unvalidated until the chosen time, at which point it will be automatically validated and published.
How can members edit their profiles and account settings?
Answer
Members can edit their profiles and account settings through the "Edit" tab on their profile page. They can change their password, update personal information, manage their avatar and signature, and adjust their privacy settings. Administrators have access to additional options for managing member accounts.
Welcome Emails are a series of automated emails sent to new members on a predefined schedule. They can be used to introduce the website's features, encourage engagement, and provide helpful information. Website administrators can customize the content and schedule of these emails.
How can I enhance or enforce the security of member passwords?
Answer
Composr offers several features to improve password security:
Password Strength Setting: Administrators can set a minimum password strength requirement, forcing members to choose stronger passwords. Password strengths are calculated on a scale of 1-10 using algorithms that take into account letters (including case), numbers, symbols, repeat characters, use of dictionary words, and use of usernames / dates of birth / e-mail addresses.
Forced Password Resets: Administrators can force specific members or all members to change their passwords upon next login, enhancing security in case of potential breaches.
Expiring passwords: Administrators can require members to change their password after so many days.
Encrypted CPFs: If the server has the OpenSSL PHP extension installed, specific CPFs (such as ones containing other passwords) can be encrypted to protect sensitive member data in case of a server compromise.
Yes, Composr allows you to import and export member data using CSV spreadsheet files. This is useful for transferring member information between different systems, performing bulk updates, or creating backups. The export feature provides various filtering options, and the import feature supports adding new members and updating existing ones.
Go to Admin Zone > Security > Members > Export members.
Usergroups are a way to categorize members and assign them specific permissions and privileges. Each member can belong to one or more usergroups, and the permissions granted by those usergroups determine what actions they can perform on the website. Website administrators can create and manage usergroups, define their permissions, and assign members to them. They can also assign leaders who then have permission to manage the members of that specific usergroup.
What are Custom Profile Fields (CPFs) and how are they used?
Answer
CPFs allow website administrators to collect additional information from members beyond the basic profile fields. These fields can be customized to fit the specific needs of the website, such as collecting job roles, hobbies, or interests. CPFs can be used to:
Enforce specific requirements for membership (e.g., job role in a company forum).
Categorize members based on their interests or affiliations (e.g., football players in a school forum).
Display additional information on member profiles and forum posts.
Regular Registration: Users can click on "join" links, agree to your rules, and fill out a registration form. They will then receive an activation email to confirm their email address (if enabled).
Invites: You can restrict joining to invite-only. Existing members can send invites, and only those who receive an invite can register.
Manual Addition: Administrators can manually create member accounts through the Admin Zone. This is useful for pre-joining members or handling issues with the regular registration process.
Other Methods: Composr also supports automatic member joining through LDAP and HTTP authentication.
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.