This is just a placeholder site for Composr CMS 11 beta. It will become the new homesite once version 11 reaches stable. For the current v10 homesite, click here. Please also use the v10 tracker to report v11 issues.

The telemetry service is being re-built and will not work for any sites until v11 beta7. Please report all Composr errors you encounter to the tracker to ensure the developers receive them.

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	Can I display different content to different usergroups?
Answer	Yes, you can achieve this by leveraging Tempcode within your templates. By using conditional statements like `{$IS_IN_GROUP}` and `{$HAS_PRIVILEGE}`, you can show or hide specific content sections based on the user's group membership or privileges. This technique allows you to "tease" premium content to non-paying users or tailor the user experience based on their access level.

Question	What are match-key permissions and why would I use them?
Answer	Match-key permissions provide a more granular level of access control beyond the standard zone, page, and category permissions. They allow you to restrict access based on specific "match-keys", which are unique identifiers for different actions or content within Composr. For instance, you could use match-key permissions to prevent guests from submitting banners or to restrict access to the member directory for all but specific usergroups. You can also specify custom access denied errors for each match-key. A "match-key" is typically a page-link, such as `cms:cms_banners:add`.

Question	How can I control who can view specific pages or categories?
Answer	You can manage access control for zones, pages, and categories primarily through the Permissions Tree Editor (Admin Zone > Security > Permissions Tree Editor). This tool provides a central location to set view permissions for different usergroups. You can also edit individual zone and category permissions through their respective editing interfaces, but the Permissions Tree Editor offers a more streamlined and efficient approach.

Question	What is the difference between access permissions and privileges in Composr?
Answer	Access permissions control whether members of a certain usergroup can view specific areas of your site, such as zones, pages, and categories. A member only needs one of their usergroups to have access permission to view the content. But permissions work on a deny-first policy; if one of the permissions applicable to viewing something is denied for a usergroup, then the whole thing is denied for that usergroup (e.g. even if a download itself grants access, access will be denied if its category denies access). Privileges, on the other hand, dictate what actions a usergroup is allowed to perform across the website, like using advanced Comcode or bypassing the word filter.

Question	How can I change the news archive display to show summaries instead of just headlines?
Answer	By default, the news archive screen shows only headlines. To display summaries like the news block, add :inline=1 to the page-link. For example, if your news archive page-link is site:news, modify it to site:news:inline=1. This will show summaries instead of just the headlines in the archive view.

Question	What are Trackbacks and how do they work in Composr?
Answer	Trackbacks are a blogging feature that creates a link from an article on one blog to an article on another, acting as a citation mechanism. How Trackbacks Work: The original article includes a "trackback" link in its HTML. When another blogger writes an article referencing the original, their software uses the trackback link to inform the original site. Composr receives the trackback and displays a list of articles linking back to the original. To enable trackbacks, go to Admin Zone > Setup > Configuration > Feature options and check the "Trackbacks" option. You can then enable trackbacks for individual content items.

Question	How can I filter the news archive to show specific content?
Answer	The news system allows advanced filtering: Blog vs. Non-Blog Posts: Choose to display blog posts only, regular news posts only, or both. Category Filtering: Limit results to specific news categories. Double Filtering: Apply a second category filter for a two-level categorization system (useful for large sites). These filters are controlled through parameters passed to the news blocks and carried through navigation links. When viewing a news post, you can also filter by the categories associated with that post.

Question	How do I display external RSS feeds on my Composr website?
Answer	Composr offers two blocks for displaying RSS and Atom feeds in a news-like format: main_rss block: Suitable for main content areas side_rss block: Designed for sidebars and smaller spaces To add a block, use the Block Construction Assistant or insert the following Comcode into your page: `[block="http://example.com/feed.xml"]main_rss[/block]` `[block="http://example.com/feed.xml"]side_rss[/block]` Replace "http://example.com/feed.xml" with the actual feed URL. Important: Exercise caution when using external feeds. Ensure the source is trustworthy, as malicious feeds can contain harmful code.

Question	What are RSS/Atom feeds and how do they benefit my website?
Answer	Feeds, in formats like RSS and Atom, are XML files that syndicate your website content, making it accessible beyond your website. They can be viewed using feed reader applications (e.g., Feedly, Vienna) or integrated into other websites or web browsers. Composr supports both RSS and Atom for syndicating news and other content. While RSS is more common, Atom is a cleaner, standardized format. Both effectively share your content updates. Benefits: Wider audience reach: Your content becomes accessible to those using feed readers and aggregators. Content repurposing: Other websites can incorporate your feed, increasing visibility. Increased traffic: Users discovering your content in feeds may visit your website directly. Staying on top: Those who use your RSS feeds will see when you post new news articles.

Question	What are Personal Categories/Blogs in Composr? How do I create one?
Answer	Composr allows members of permitted usergroups to have their own personal news categories, also known as "blogs". These blogs appear as a tab on the member's profile (Conversr-only) and may also appear in the main news block depending on your configuration. To create a blog, a member simply adds a news post and selects their personal category. If the category doesn't exist, it will be automatically created upon submission. A dedicated "Blogs" CMS module (Admin Zone > Content > Blogs) is available if the "Separate blogs" configuration option is enabled. This simplified module focuses on blog posting and can be used to restrict members from submitting to general website news.

Top 10 Entries

Website	PDStig, LLC
Screenshot
Short Description	This is an informational site / portfolio for PDStig, LLC, the company run by one of Composr's lead developers, Patrick Schmalstig.

Website	Composr CMS: Your Data, Your Privacy, Your Control - Composr CMS: Your Data, Your Privacy, Your Control
Screenshot
Short Description	This is the main website for Composr CMS version 11. It runs the latest build of v11. Currently it is just a placeholder but will soon replace compo.sr when v11 becomes stable.

Question

Should I use the bleeding edge releases or the git repository?

Answer

That depends on several factors. Here are some pros and cons of each:

Bleeding edge releases	Git repository (v11 branch)
Easier to set up and use, and does not require knowledge of git	Harder to set up and use unless you are familiar with git; must routinely run the file integrity check, database upgrade tool, and check database schema tools in the upgrader after pulling
More stable, but less frequent updates	Less stable, but more frequent updates (almost daily!)
Only contains core code and addons unless you manually install non-bundled addons; non-bundled addons must be manually updated	Contains all core code and non-bundled addons; non-bundled addons are updated with pulls (though you will need to check file/database integrity often and check blocks/modules for available upgrades)
Ability to test the upgrader / upgrading between new v11 versions	Not able to effectively test the upgrader because git pull might load in and update new code early before the release is available
Always contains the latest files.bin and db_meta.bin because these are compiled with every release	Does not always contain the latest files.bin and db_meta.bin. Therefore, file and database integrity may report false-positives.
Intended for general user testing	Intended for developers / developer testing: * special run-time checks are enabled for extra debugging (if the .git directory exists in the install) * contains the automated test suite for running tests

Click here to access the git repository.

Question	Can I switch a v11 install from git over to using the releases from composr.app?
Answer	It is not recommended you do this because you may run into issues. For example, some changes were made in crypto_master.php and data/upgrader2.php prior to the first v11 alpha. These changes will result in a broken upgrade unless you already pulled these changes from git. Similar situations could happen in the future as well. It is recommended you either discard the git install and use a fresh install from the Downloads, or to maintain a git install and a bleeding-edge release install separately. Do not combine the two.

Question	Should I update my non-bundled addons after updating to a newer release of version 11?
Answer	Absolutely! Frequent changes may be made to both bundled and non-bundled addons. Bundled addons will be updated via the upgrader. For non-bundled addons, you will have to update them through the addons management screen (Admin Zone > Structure > Addons). You will be informed which ones need updated. Once version 11 reaches release candidate, we do not expect frequent updates to non-bundled addons anymore. But it is still good practice to check after every update.

Question	Can I upgrade a version 10 site to version 11?
Answer	Yes, for basic non-custom v10 sites. However, expect some issues to arise in the process. And please report those issues to the tracker. For v10 sites with non-bundled addons or customisations, upgrading to v11 will likely break the site until you update the non-bundled addons or temporarily remove the customisations. We aim to have the upgrader fully functional for a large majority of types of sites and for sites using non-bundled addons by the time version 11 reaches release candidate stage. We do not recommend upgrading production v10 sites at this time until v11 reaches stable.

Question	Can I upgrade a previous version 11 release to a newer one using the upgrader?
Answer	Yes (probably). Always remember especially during alpha and beta phases that things can break. Please make backups first. And let us know on the issue tracker if an issue occurs. Note: You cannot upgrade from 11 alpha to 11 beta without first upgrading to 11.alpha4 (if you are not already on 11.alpha4).

Question	What are the current release plans for version 11?
Answer	As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site. We will be releasing several beta versions in the beta phase. We do not know when we will be able to release the first Release Candidate or stable versions at this time. These plans are all subject to change without notice.

Question	Why is there a separate website for version 11?
Answer	That is explained in detail in this news article on compo.sr including the migration plans and implications.

Statistics

Forum statistics:	45 topics, 14 posts, 2 members Our newest member is test