Where are download galleries located, and can I move them?
Answer
By default, download galleries (to contain screenshots of a download) are placed under the root gallery. You can move them to a different gallery for better organization. Here's how:
Create a new container gallery (e.g., with codename "downloads").
Change the "Create download galleries under" configuration option to your new gallery's codename.
Use Commandr to move existing galleries to the new location.
Yes, the download system integrates with the points system, allowing you to charge for downloads. This is particularly useful for communities where members create and share content, like game modifications. You can set prices for downloads and creators earn points when users purchase them. Additionally, you can create a subscription-based system by requiring points for downloads, which users can purchase via methods like PayPal.
Outmoding means marking a download as superseded or replaced by a newer version. When editing the older download, you link it to the new one in the "outmode" field. This makes it clear to users that there is a newer version available. This is handy especially if you provide software.
What are the different ways to add downloads to my Composr site?
Answer
Composr offers several methods for adding files to the download system:
Uploading via web form (when adding a download in the Content Management Zone): This is the simplest method, where you attach the file directly when defining the download details. However, it's not suitable for large files and can be affected by unreliable internet connections.
Uploading and referencing the URL: You can manually upload the file using FTP/SFTP/SCP and then provide the URL to the file in the 'Add download' form. While this is better for large files, it requires additional
access, and the file isn't managed directly by Composr.
Batch adding from an FTP server: This allows staff to add multiple downloads from an FTP server in one go using FTP URLs. It's efficient for bulk uploads but requires separate addition of descriptions.
Batch adding from a directory: Similar to the FTP method, staff can add downloads from a web server directory accessible by URL.
File/media library (filedump): Webmasters can use any of the above methods to upload a file to uploads/filedump and then reference it in a download. This is especially handy if you are going to reference the file more than once on your site.
How can I change the structure of my Composr website's pages?
Answer
You can delete and move pages using the Admin Zone > Structure > Sitemap editor. However, moving pages between zones might invalidate existing page-links unless specified using the _SEARCH zone in the link.
To avoid issues with existing links and search engine indexing, consider setting up redirects when moving pages. This can be done through Admin Zone > Structure > Redirects.
It is recommended not to move default Composr pages as it can complicate future upgrades.
How do I open or close my Composr website to the public?
Answer
By default, your Composr site is closed after installation. To open it to the public (or to close an opened site), go to Admin Zone > Setup > Configuration > Site options > Closed site and adjust the setting accordingly. You can also configure a closed site message.
While a closed site prevents public access, it's worth noting that users can still join a closed Conversr-powered site if they have access to the join module URL. However, they won't be able to log in unless they're assigned to a usergroup with "Access closed site" permissions. You can modify the join module's permissions to restrict access further.
What is the .htaccess file and how does it relate to Composr?
Answer
The .htaccess file is a configuration file for the Apache web server. It allows you to define settings that apply to the directory where it's located and its subdirectories.
Composr can leverage .htaccess to enhance security and enable features like "URL Schemes." You can try renaming the provided recommended.htaccess file to .htaccess. This file includes recommended options that tighten security and ensure Composr has necessary PHP and Apache features activated.
Note that some web hosts might restrict the use of .htaccess files.
You should regularly review recommended.htaccess for changes between Composr updates.
Composr employs a multi-layered permission system with two main types: privileges and access permissions. The system grants users the best possible access based on the combination of their usergroups.
Privileges define broad permissions, such as accessing a closed site or content manipulation abilities based on impact level (low, medium, high). You can set privileges for usergroups via checkboxes, with the option to override them for specific pages or categories. Go to Admin Zone > Security > Global privileges.
Access permissions control what content users can view. These permissions are layered:
Zone access permissions
Page (or content entry) access permissions
Catalogue access permissions
Category access permissions
To configure access permissions, you can edit the specific resource or utilize the Permissions Tree Editor under Admin Zone > Security > Permissions Tree Editor.
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.
