The Composr Member System is the system used by the Conversr forum software to manage user accounts and information. This includes usernames, passwords, profile information, and usergroups. It also handles user registration, login, and account management. For websites not using Conversr, the member system of the third-party forum software would be used.
Yes, Composr supports creating podcasts from galleries. The podcast URL follows this format: http://yourbaseurl/backend.php?mode=galleries&select=galleryname&type=rss&itunes=1. Replace yourbaseurl and galleryname accordingly. This URL can be used to subscribe to the podcast in iTunes or other podcast applications.
When viewing an image or video in a gallery, visitors can initiate a slide-show that automatically cycles through subsequent entries. The slide-show can be paused with a click or keypress. The default slide-show speed can be adjusted by modifying the GALLERY_ENTRY_SCREEN.tpl template.
Watermarks are semi-transparent images overlaid on gallery images to mark their origin or deter unauthorized use. When you add or edit a gallery, you can choose to apply watermarks to the corners of images. Watermarking applies permanently to the uploaded image. Composr uses a reverse tree structure for watermarks: if a sub-gallery doesn't have a watermark defined, it inherits the watermark from its parent gallery.
Yes, members with the "have personal galleries" permission can create their own galleries. These personal galleries are displayed under designated "Personal category container" galleries. They also show up in a tab on the member's profile. Members can only add content to their own galleries unless they have the "Submit to categories belonging to other members" permission.
Rep-images, short for "representative images," are thumbnails that represent a gallery when it's displayed within a list of galleries. They offer a visual preview of the gallery's contents. You can set a rep-image when adding or editing a gallery, or when adding an image to a gallery.
You can import images in bulk using a CSV file. The file should be named descriptions.csv and placed in the uploads/galleries directory. The first column should contain filenames (without the path), and the second column should contain descriptions. The filenames should correspond to images also located in the uploads/galleries directory. Composr will automatically match the descriptions to the images during import.
Composr Galleries are a system for storing, organizing, and displaying images and videos. They function like categories, allowing you to group related media together. Galleries can be structured hierarchically, with sub-galleries nested under parent galleries, similar to a folder system. Each gallery has settings that control its appearance and behavior.
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.
