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 can I ensure my website complies with email marketing laws? |
---|---|
Answer | Email marketing laws like CAN-SPAM protect recipients' rights to unsubscribe. Your website must include a clear 'List-Unsubscribe' header in every email, offer an easy unsubscribe process, and respect unsubscribe requests promptly. Composr provides built-in mechanisms, including an unsubscribe endpoint and support for the List-Unsubscribe header, to facilitate compliance. |
Question | What are my responsibilities regarding user privacy? |
---|---|
Answer | You must have a comprehensive privacy policy that details the personal data you collect, its usage, and if it's shared with third parties. Laws like GDPR have strict requirements, including logging data access, data purging, and security measures. California law mandates specific elements in your policy, like handling "Do Not Track" requests and a clear process for communicating changes. Composr has an automatic Privacy Policy generator block to help you get started. This is used by default. |
Question | How can I create effective website rules? |
---|---|
Answer | A well-defined rules page is crucial for setting expectations for user behavior and outlining consequences for violations. It should cover a range of offenses with appropriate punishments, reference relevant laws, and assign legal responsibility to users. Composr provides default rules pages that can be customized, and this page is displayed to users upon joining the site. |
Question | What are the key legal considerations for running a website? |
---|---|
Answer | Several legal aspects need careful attention when operating a website, especially for large or corporate sites. These include establishing clear rules and terms of service, adhering to privacy laws like GDPR and California's regulations, managing personal data responsibly, complying with email marketing regulations like CAN-SPAM, ensuring website accessibility, addressing eCommerce regulations, and understanding liability for content and user actions. |
Question | How do data-tpl and data-view behaviors work in Composr's JavaScript? |
---|---|
Answer | Composr uses data-tpl and data-view behaviors for associating HTML templates and JavaScript views, respectively. This facilitates clean separation of presentation and logic:
|
Question | What are the advantages of using Composr's JavaScript libraries? |
---|---|
Answer | Composr's JavaScript libraries like $cms, $util, and $dom offer several advantages:
|
Question | How does Composr implement the Model-View-Controller (MVC) pattern? |
---|---|
Answer |
|
Question | Can I translate my content into multiple languages? |
---|---|
Answer | Yes, Composr supports multi-language content. You can enable this feature by:
|
Question | My language uses gendered descriptors. How can I handle this in Composr? |
---|---|
Answer | Composr offers solutions for languages with gendered descriptors:
|
Question | What are language strings, and how are they used? |
---|---|
Answer | Language strings are phrases or pieces of text used throughout Composr. They're identified by unique codenames, like WELCOME_MESSAGE. These strings are stored in .ini language files and used to display text in the user interface. By translating language strings, you change the text displayed on your website without modifying the underlying code. |
Top 10 Entries
Question | What is the purpose of "confirmed" and "non-confirmed" sessions? |
---|---|
Answer | Composr distinguishes between confirmed and non-confirmed sessions for added security:
You can configure zones to require confirmed sessions, preventing access from cookie-based logins alone. The Admin Zone uses this by default. |
Question | How can I enhance the security of my Composr installation on shared hosting? |
---|---|
Answer | Shared hosting environments can be inherently less secure. Here are some tips:
|
Question | How does Composr protect against Cross-Site Scripting (XSS) attacks? |
---|---|
Answer | Composr utilizes multiple layers of defense against XSS attacks:
|
Question | What are the different types of security alerts in Composr? |
---|---|
Answer | Composr has a variety of hack-attack codenames that trigger security alerts and logging. Some common examples include:
You can customize alert handling for each type in data_custom/xml_config/advanced_banning.xml (Admin Zone > Security > Configure advanced banning). |
Question | What are some tips for secure website maintenance? |
---|---|
Answer |
|
Question | What are the main security features of Composr? |
---|---|
Answer | Composr has a robust set of security features to protect your website, including: Passwords:
Login Restrictions:
Auditing Systems:
Framework Security:
Other features:
|
Question | Why are my searches slow, and how can I improve search speed? |
---|---|
Answer | Slow searches can occur when dealing with large amounts of content. Here are some workarounds and solutions:
|
Question | How does the search engine handle different languages? |
---|---|
Answer | Composr's fast custom index supports multiple languages. Content is indexed based on its translated version, ensuring that you get relevant results even when searching in a different language. |
Question | What are quoted phrases and how do they work? |
---|---|
Answer | Quoted phrases allow you to search for an exact sequence of words. For example, searching for "red apple" will only return results containing that exact phrase. Keep in mind that enabling quoted phrases can increase disk space usage. |
Question | How do stop words affect search results? |
---|---|
Answer | Stop words are common words (like "the", "a", "is") that are ignored by the search engine because they add noise and don't contribute to the meaning of the search query. You can customize the list of stop words for the fast custom index. See the search tutorial for more information. |