Features: A-Z Index

A

Administration Zone

Administration Zone

B

Banners

Banners

C

Calendar

Calendar

Catalogues

Catalogues

Chatrooms and IM

Chatrooms and IM

Community features

Community features

Content Sharing

Content Sharing

Conversr Forums

Conversr Forums

Conversr Topic Polls

Conversr Topic Polls

D

Design without barriers

Design without barriers

Downloads

Downloads

E

Ease of Use

Ease of Use

eCommerce and Subscriptions

eCommerce and Subscriptions

Extendable

Extendable

F

Featured Content

Featured Content

G

Galleries

Galleries

I

Installation

Installation

Integration

Integration

L

Localisation

Localisation

M

Membership

Membership

N

News and Blogs

News and Blogs

Newsletters

Newsletters

P

Parental Controls

Parental Controls

Performance

Performance

Points

Points

Privacy Tools

Privacy Tools

Q

Quizzes and Surveys

Quizzes and Surveys

R

Rich Media

Rich Media

S

Search Engine Optimisation

Search Engine Optimisation

Searching

Searching

Security

Security

Spam Protection

Spam Protection

Stay on Top

Stay on Top

Structure / Navigation

Structure / Navigation

Support Tickets

Support Tickets

T

Template Programming Language

Template Programming Language

Testing tools

Testing tools

Themeing tools

Themeing tools

Third party integration

Third party integration

W

Warnings / Moderation

Warnings / Moderation

Web Pages

Web Pages

Web standards

Web standards

Website Polls

Website Polls

White-labeling (Debranding)

White-labeling (Debranding)

Wiki+

Wiki+

Newest 10 Entries

Question What is the Admin Zone?
Answer The Admin Zone is a special section of your Composr website that allows authorized staff members to perform various administrative tasks. It serves as the central hub for managing content, configuring settings, monitoring activity, and maintaining the overall health of your website.
Question What should I avoid doing in Composr to maintain accessibility?
Answer Avoid using Comcode tags or other HTML elements that create dynamic effects in the user's browser, such as ticker and jumping. These can have a negative impact on navigation and scrolling.
Provide alternate information for multimedia you upload so those with auditory impairments can still understand the content.
Avoid creating multiple content items with the same title, as this can lead to accessibility issues and general user confusion.
Question How does Composr handle forms for accessibility?
Answer The web standards checker ensures that form labels are properly positioned and explicitly associated with their controls.
It also checks that form elements have a logical tab order and are keyboard operable.
Question How does Composr ensure accessible data tables?
Answer The web standards checker enforces proper markup for data tables, including identifying row and column headers, and associating data cells with header cells.
It ensures that tables are not used for layout (flex boxes and HTML grids are preferred for mobile responsiveness) unless they make sense when linearized.
Composr provides summaries for tables to aid non-visual user agents in understanding their structure and content.
Question How does Composr handle color contrast for accessibility?
Answer Composr is designed with high graphic standards that aim to avoid poor color contrast in the default theme and Theme Wizard. But it is not perfect, especially for dark mode themes.
Webmasters are still responsible for ensuring sufficient contrast in their own content and in custom themes.
Question How do I provide text equivalents for images and multimedia in Composr?
Answer Composr's web standards checker ensures that alternative text (using the "alt" attribute) is provided for images. It will warn if any images do not contain alt text.
For multimedia, webmasters are responsible for providing captions and auditory descriptions either in the multimedia itself, on the description of the media, or uploaded as a caption file.
Question How can I make sure my Composr website is accessible?
Answer Enable the web standards checker in Composr while editing templates. Also do the same when previewing edited or new Comcode pages.
Use the provided accessibility options in the Admin Zone to customize the webmaster experience according to your accessibility needs.
Follow the webmaster concerns outlined in the "Helping improve site accessibility for disabled users" tutorial.
Regularly test your website using third-party accessibility validation tools such as the WAVE Web Accessibility Evaluation Tool or the AChecker.
Question What accessibility features are built into Composr?
Answer Composr has an inbuilt web standards checker that helps ensure compliance with accessibility guidelines.
Composr provides automatic sitemap generation functionality, a default sitemap page, and an advanced menu editor to manage navigation.
Composr supports ARIA (Accessible Rich Internet Applications), which helps make dynamic content accessible.
Composr includes options in the Admin Zone to fine-tune the webmaster experience for specific accessibility requirements.
Question Does Composr comply with accessibility standards?
Answer - Yes, Composr complies with the highest level of the WCAG (version 1.0 at the time of writing), level 3.
- Composr also meets Section 508 guidelines, XHTML and CSS specifications, and the highest level of ATAG.
- Composr conforms to these standards throughout, from user-facing screens to administrator interfaces.
Title Extendable
Icon Image
Description

Versatile: You can strip down to a core system, or build up with 3rd-party addons.

Full API documentation

High coding standards: No PHP notices. Type-strict codebase. MVC framework.

Free online developer's guide book (in the tutorials)

Custom field filters: For example, restrict news posts to a minimum length.

Stack traces for easy debugging

Synchronise data between staging and live sites using Resource-fs

Breadcrumb overrides

Advanced banning: Set your own banning rules for different hack attack codes. Even create your own ban pages (e.g. to mimic law enforcement bans for spammers).

Code overrides: Implement modifications to the Composr code without directly editing the original code by creating _custom files. This makes upgrading much easier. Also supports contentious_overrides hooks and the override_api for more advanced overriding.

Many different hook types allowing for modifying or extending Composr without modifying or overriding the code.

Top 10 Entries

Question What are the key classes and utilities provided by Composr Mobile SDK?
Answer CMS SDK provides several classes with utility functions mirroring PHP and Composr APIs, including:
  • CMS_Arrays: Array operations (e.g., implode, explode, list_to_map).
  • CMS_Strings: String manipulation (e.g., strip_tags, html_entity_decode, strpos).
  • CMS_Langs: Localization functions (e.g., do_lang).
  • CMS_Preferences: User preference management.
  • CMS_Timestamps: Timestamp functions (e.g., get_timezoned_date_time, time).
  • CMS_HTTP: Web service interactions (e.g., rawurlencode, json_decode, http_get_contents).
  • CMS_Users: User data and permission checks (e.g., has_page_access, is_staff).
  • CMS_Flow: App flow control (e.g., access_denied, attach_message).
  • CMS_Forms: Form building and management.
  • CMS_Database: SQLite database access and manipulation.
  • CMS_Notification: Push notification handling.
  • CMSNetworkManager: Network request execution and response handling.
Question How do I set up Composr Mobile SDK in my iOS and Android projects?
Answer iOS (Xcode):
  • Create a new project or open an existing one.
  • Add a Prefix Header file (.pch) if you don't have one, following the provided instructions.
  • Add required frameworks to your project's Build Phases.
  • Add the CMS SDK to your project, then remove references to unwanted files.
  • Set the header search path to the CMS SDK folder in build settings.
  • Add a compiler option for the JsonKit library.
  • Import CMS_SDK.h in your .pch file.

Android (Eclipse):
  • Create a new project or open an existing one.
  • Import CMS SDK into your workspace as an Android project.
  • Ensure "Is Library" is checked in the CMS SDK's "Android" properties tab.
  • Add CMS SDK as a dependent library in your project's properties.
  • Clean and rebuild your project.
Question What are some key concepts related to mobile app development with Composr?
Answer Essential concepts include:
  • SDK (Software Development Kit): An API implementation, typically as a library.
  • API (Application Programming Interface): A set of rules for software interaction.
  • JSON (JavaScript Object Notation): A common language for structured data transfer over REST.
  • REST (Representational State Transfer): An architectural style for web services.
  • Push notification: A notification sent to a mobile device.
Question What other approaches exist for mobile integration with Composr?
Answer Other approaches, in various stages of development, include:
  • Tapatalk: A third-party forum app with an official Composr addon, offering a high-quality "out-of-the-box" Composr app experience.
  • Further Composr Mobile SDK development: Plans and issues relating to the SDK's evolution can be found on the Composr tracker, driven by commercial projects and feature sponsorship.
Question What are some of the default endpoints available in the server-side API?
Answer Default endpoints cover various functionalities, including:
  • Account: join, login, lost_password, setup_push_notifications
  • Misc: contact_us
  • Content: commandr_fs

Specific details on parameters and response data for each endpoint can be found in the documentation.
Question 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.
Question 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.
Question 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.
Question How can I obtain Composr Mobile SDK?
Answer The iOS/Android SDK can be found on GitLab at: Composr ecosystem / Composr Mobile SDK · GitLab.

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.
Question What is Composr Mobile SDK?
Answer 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.