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 | How do I set the correct file permissions for Composr? |
---|---|
Answer | If you're using the quick installer, it will handle file permissions automatically. On a suEXEC-style server, default permissions (744 for directories and 644 for files) are usually sufficient. However, _config.php should have 600 permissions for security. Without suEXEC, specific directories (e.g., caches, uploads) and files (e.g., _config.php) require 777 (full access) or 666 (read/write) permissions. The fixperms.php script can automate this process on Linux and Windows. |
Question | How do I install Composr on Linux? |
---|---|
Answer | After ensuring your web host meets the requirements and you have a database ready, you can install Composr on Linux using the following steps:
|
Question | What are the prerequisites for installing Composr? |
---|---|
Answer | Before installing Composr, ensure your web host meets the minimum requirements. Familiarize yourself with your web host's control panel (e.g., Plesk, cPanel), which you'll use to manage databases, subdomains, and other settings. Gather your SFTP/FTP credentials (hostname, username, password), usually emailed upon signup. Set up a MySQL database and note its details: hostname (often 'localhost'), username, password, and database name. Ensure the database user has full read/write/administer access to the database. |
Question | What tools are available for debugging Composr code? |
---|---|
Answer | Composr offers a code quality checker addon that helps identify various types of errors, including parser errors, run-time errors, and logical errors. This tool can significantly reduce debugging time and enhance code reliability. It is available through the testing_platform addon. |
Question | What are some key coding standards in Composr? |
---|---|
Answer | Composr emphasizes clean, well-structured code with a focus on readability and maintainability. Key standards include proper indentation, consistent use of comments, and clear function headers with type definitions. Remember: beautiful code leads to better functionality and collaboration! |
Question | Where can I find resources for learning PHP programming? |
---|---|
Answer | While Composr documentation doesn't cover basic PHP, resources like the official PHP documentation ( |
Question | What is the purpose of the Code Editor? |
---|---|
Answer | The Code Editor is a web-based tool for editing Composr code files directly on the server. It requires password authentication and automatically manages overrides within _custom directories. To access it, go to yourbaseurl/code_editor.php. |
Question | How can I export and import custom addons? |
---|---|
Answer | Composr allows exporting addons as TAR files, containing all necessary files and an addon.inf file for metadata. You can import these addons to share and reuse them across different Composr installations. To do this, make your necessary files for the addon in the Composr installation, and then go under Admin Zone > Structure > Addons > Export addon. You can select the relevant files for the addon, provide information about the addon, and then download the TAR file (which can then be imported on other Composr sites). |
Question | Can you give an example of creating a new module? |
---|---|
Answer | Imagine creating a "Testing" module to manage collaborative testing:
|
Question | What are the different ways to extend Composr functionality? |
---|---|
Answer | You can extend Composr through:
|
Top 10 Entries
Question | How do I report an emergency problem with my Composr site? |
---|---|
Answer | Emergency problems are events that have significantly and suddenly affected your website's functionality due to legitimate bugs or undocumented usability issues. To report these:
|
Question | How can I get support for Composr? |
---|---|
Answer | The community forum is an excellent resource for support. Users can help each other out with various problems. However, please remember that there's no guarantee of free professional support. If you need immediate or guaranteed assistance, consider hiring a professional developer. |
Question | I'm getting a lot of spam on my site. What can I do? |
---|---|
Answer | Composr offers various anti-spam measures. Refer to the Anti-spam settings tutorial for advice on configuring these settings. If you believe there's an issue with the anti-spam system itself, report it to the issue tracker. Do not report general spam incidents. |
Question | My website is experiencing performance issues. What should I do? |
---|---|
Answer | If you are experiencing performance issues, first identify the specific problem with your web host's help. Composr provides tools to manage database size, bandwidth, and disk I/O. However, high request volume or CPU usage may require server upgrades like a VPS or dedicated server. If your web host complains about resource usage, gather detailed information from them, including specific URLs causing problems and resource usage metrics. If their limits are unreasonable, consider switching web hosts. |
Question | How do I report a security problem? |
---|---|
Answer | Security problems must be reported privately. You can do this by marking the issue as 'Private' on the issue tracker (if you use the Report Issue Wizard, it will do that automatically when you select security-hole). Publicly disclosing security holes is irresponsible and may result in penalties. The core developer team will disclose the issue after a patch is released. |
Question | How do I report a bug in Composr? |
---|---|
Answer | Every bug, no matter how small, should be reported. You can report bugs using the Report Issue Wizard or directly through the issue tracker. There is also a link to report bugs on your Admin Zone Dashboard where the version information is located. And when clicking that link, you can view open issues specific to your version of Composr. When reporting a bug, be sure to:
|
Question | What is the role of robots.txt in SEO? |
---|---|
Answer | The robots.txt file provides instructions to search engine crawlers about which parts of your website they should and should not access. You can customize the robots.txt file to prevent sensitive content from being indexed or to guide crawlers toward the most important areas of your site. |
Question | What is SEO and why is it important for my Composr website? |
---|---|
Answer | SEO is the practice of optimizing your website to rank higher in search engine results pages (SERPs). By improving your SEO, you increase the visibility of your website, driving more organic (non-paid) traffic to your content. |
Question | How can I edit the metadata in Composr? |
---|---|
Answer | Composr provides several ways to customize your metadata:
|
Question | Should I trust agencies that promise top search engine results? |
---|---|
Answer | No; be wary of agencies guaranteeing top rankings for any desired keyword. Achieving top results for competitive terms requires significant effort, expertise, and often, an ongoing strategy. Focus on agencies that prioritize ethical "white-hat" SEO techniques like creating valuable content, optimizing website structure, and building natural backlinks. Avoid those employing "black-hat" methods that can lead to penalties from search engines. |