Contributors: A-Z Index
A
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Allen Ellis | Founder |
Original designer for ocPortal Also conceived and coded the Theme Wizard and Point Store Son of one of the early inventors of Internet protocols (Usenet, aka Internet newsgroups) Token non-brit |
View |
C
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Chris Graham | Founder |
Original developer of ocPortal, former lead developer of Composr CMS Masters degree in Computer Science from The University Of Sheffield Undertaken work for over 15 FTSE-100 companies, as well as many small and mid-sized organisations. Includes a number of banks and major brands. |
View | |
Chris Warburton | developer for ocProducts |
Made some key contributions to ocPortal |
View |
H
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Haydn Maidment | project manager for ocProducts |
None available |
View |
J
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Jim Davidson | contributor |
written many tutorials via Arvixe |
View |
P
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Patrick Schmalstig | Lead Developer |
Joined Chris Graham behind the scenes in the development of Composr CMS in 2016. Took on the lead developer role in 2023 when Chris Graham stepped back to attend to his new lifestyle changes. Spearheaded the development of Composr CMS v11 and the new website, Composr.app. Formed the company PDStig, LLC to take on professional support and development for Composr CMS users especially after the discontinuation of ocProducts, Ltd. |
View | |
Philip Withnall | Early Developer |
Coded the chatroom, blogging support, the analytics system, and OcCLE (now Commandr) Masters Degree in Computer Science degree from The University Of Cambridge Other work has included helping out with Firefox, and ongoing work on GNOME |
View |
R
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Robert Goacher | Founder |
Ran some of the early websites where ocPortal came from Technically the original developer of ocPortal, in that he wrote the first few lines of code Heavily involved in the feature design process Hosted some of our early meet-ups |
View |
S
Name | Photograph | Title / Role | Contributions / Notes | |
---|---|---|---|---|
Steve Jarvis | project manager for ocProducts |
Wrote many tutorials via Arvixe |
View |
Newest 10 Entries
Question | Are there any limitations to importing forum data? |
---|---|
Answer | Yes, some limitations exist, particularly with specific forum platforms.
|
Question | Where can I find the import functionality in Composr? |
---|---|
Answer | Navigate to Admin Zone > Tools > Import. |
Question | What data formats can Composr import? |
---|---|
Answer | Composr primarily uses database connections for importing. However, it also supports neutral data formats like CSV spreadsheet files and importing downloads from a directory. |
Question | Can I import data from other platforms into Composr? |
---|---|
Answer | Yes, Composr offers importers for several popular platforms:
|
Question | How do I move my Composr website to a new server? |
---|---|
Answer | Moving a Composr site involves transferring both the files and the database. Files:
Database:
Important Steps:
|
Question | Can I integrate third-party JavaScript libraries into Composr? |
---|---|
Answer | Yes, you can integrate third-party JavaScript libraries using various methods:
|
Question | How does Composr handle user authentication with external systems like LDAP or HTTP authentication? |
---|---|
Answer | Composr can integrate with LDAP and HTTP authentication, but these features are considered complex and may require programming experience to set up correctly. Both methods allow users to log in to Composr using their existing credentials from the external system, streamlining access and management. |
Question | What are the limitations of using a third-party forum driver? |
---|---|
Answer | Using a third-party forum driver can lead to limitations. Custom profile fields of type LONG_TEXT are limited to TEXT length, cookie integration is not officially supported and can be complex, and some forum drivers have specific quirks detailed in the nuances tutorial. |
Question | What are the implications of using the "none-forum" driver? |
---|---|
Answer | Using the "none-forum" driver disables or limits many Composr features, including commenting, points, and user interactions. Consider using Conversr instead and restricting access to the forum zone, join module, and personal zone. |
Question | How can I integrate my forum visually into my website? |
---|---|
Answer | Composr allows you to integrate your forum visually into your website. Enable "Show forum within website" in the Admin Zone configuration module and update the forum link in your menu to pass through the "forums" embedding module. You may need to adjust CSS to achieve a seamless look. |
Top 10 Entries
Question | What are some of the default endpoints available in the server-side API? |
---|---|
Answer | Default endpoints cover various functionalities, including:
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. |
Question | What is the Composr maintenance policy? |
---|---|
Answer | Composr follows a rolling release model. This means:
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. |
Question | What are the general courtesy guidelines for interacting with the Composr community? |
---|---|
Answer |
|
Question | How can I provide design feedback for Composr? |
---|---|
Answer | Constructive design feedback is valuable. To provide effective feedback:
|
Question | How do I make a feature suggestion for Composr? |
---|---|
Answer | You can suggest features through the tracker or the Report Issue Wizard. When making a suggestion:
|