Featured Sites: A-Z Index

H


Newest 10 Entries

Question How do I set up the system scheduler in Composr?
Answer The system scheduler is crucial for scheduled tasks like sending notifications, running backups, and processing reports. To set it up, you need to schedule a system-level task to run the data/cron_bridge.php file at least every 10 minutes. This links Composr's scheduler with your server's scheduler (like Cron on Linux).

Composr can often detect the correct command to use for your setup. You can check by visiting http://yourbaseurl/data/cron_bridge.php?query_mode=1, which should display the suggested Cron command. Note that you may need to replace the php command with the absolute path to PHP if you cannot use the php command directly.

If your hosting doesn't support Cron or scheduled tasks, you can enable scheduled tasks to run when visitors access your site. Navigate to Admin Zone > Setup > Configuration > Performance options and check "Web requests run scheduled tasks". Keep in mind that this method relies on visitor traffic and isn't as reliable as a dedicated scheduler.

Alternatively, consider using external services like EasyCron, setcronjob.com, or onlinecronjobs.com. These services allow you to schedule calls to the data/cron_bridge.php script by URL at specified intervals.
Question What are the different security levels in Composr's Setup Wizard and what do they affect?
Answer Composr offers five security levels in the Setup Wizard: Minimum, Low, Medium, High, and Ultra High. Each level sets various security configurations that you can later customize under Admin Zone > Setup > Configuration.

The security levels influence settings such as:

  • Content Security Policy
  • Session expiry time
  • Password reset process
  • Password expiry days
  • Minimum password length and strength
  • Login error secrecy
  • IP strictness for sessions
  • Cryptographic ratchet
  • CAPTCHA usage
  • Brute force threshold
  • Audio CAPTCHA
  • URL Monikers
  • .htaccess restrictions on maintenance scripts
  • Enquiry on new IP addresses

The higher the security level, the more stringent the security measures, with Ultra High offering the most robust protection but the most potential inconvenience to users.

Generally, you should use these settings depending on your site:
  • Minimum: Very bare-bones informational-only sites
  • Low: Sites which do not allow public registrations and do not use eCommerce but have content managed by different staff, and are not concerned with privacy or data
  • Medium: Sites with social features / public accounts but do not use eCommerce.
  • High: Sites which use eCommerce.
  • Ultra High: Sites containing very sensitive data, such as but not limited to cybersecurity sites, government departments, banks, healthcare, etc.
Question How do I change my website's logo?
Answer You can change your site's logo manually or by using the Logo Wizard. To change it manually, go to Admin Zone > Style > Themes. Choose "logo/-logo" from the dropdown list, which represents the logo for the Welcome Zone and any zone without a specific logo. Replace the current image by uploading a new .jpeg, .gif, or .png file. Ensure that the 'Name' field remains unchanged.
Question What are Composr addons and how do I manage them?
Answer Composr is built using a series of addons that provide different functionalities. All "bundled" addons are installed by default. Once you are familiar with Composr, it's recommended to remove any bundled addons you don't need to simplify your site and prevent accidental exposure of unconfigured features to visitors (the Setup Wizard can also uninstall these addons based on your preferences). You can manage addons by navigating to Admin Zone > Structure > Addons. Uninstalled addons are archived and can be restored later, but any associated data will be permanently lost.

Composr also offers non-bundled addons. These addons are not bundled because they are not considered mainstream, rely on third-party services, haven't been vetted to Composr standards, or don't fully conform to those standards.

You can install non-bundled addons by going to Admin Zone > Structure > Addons, scrolling to the bottom and clicking "Import non-bundled addon(s)". You will need to browse to the addon file and click the import button. Once imported, review the warnings and proceed to install the addon.

You can also download and import addons from this website under the Downloads section.
Question What are some of the default Comcode pages in Composr?
Answer Composr includes several default Comcode pages, each serving a specific purpose:

  • home (Welcome and Site zones): The default front pages for the respective zones.
  • sitemap (Welcome zone): Displays the sitemap, typically generated automatically.
  • _rules (Welcome zone): Outlines the site rules, also displayed during registration. The "rules" page (no underscore) is a wrapper for this page.
  • privacy (Welcome zone): Provides privacy policy information. By default, this is generated automatically with Composr's privacy policy generator block.
  • 404 (Welcome zone): The page shown for 404 errors (page not found) and includes a sitemap.
  • help (Site zone): Contains general help information.
  • userguide_comcode (Site zone): A basic guide to Comcode for users.

Remember that you can edit these default pages or create entirely new ones to tailor your site's content to your specific needs.
Question How do I hide a Comcode page from the sitemap?
Answer If you want to prevent a Comcode page from appearing in your sitemap, you can simply prefix its name with an underscore (_). For example, pages named "_test" or "_example" would be excluded from the sitemap. Note that this generally does not hide the page from your site itself (to do that, use the validation addon to turn validated to "OFF" for the pages); it only hides them from the sitemap / search engines.
Question Can I organize Comcode pages in a hierarchical structure?
Answer Yes, Composr allows you to simulate a hierarchical structure for your Comcode pages using multi-part paths in the page monikers. By editing the page monikers to include slashes (e.g., "about/team"), you can create a virtual directory structure within a single zone, enhancing your site's organization and navigation.
Question How do I embed content from other modules into a Comcode page?
Answer You can use various blocks to embed content from different modules:

  • main_content block: Allows you to feature individual entries from modules/content like news or articles.
  • main_multi_content, main_cc_embed, main_gallery_embed, main_news blocks: Enable you to pull in and display multiple entries based on categories or other criteria.
  • main_include_module block: Provides a powerful way to integrate any module screen directly into a Comcode page.
Question What is the difference between blocks and boxes in Composr?
Answer While both terms may seem similar, they have distinct meanings in Composr:
  • Blocks are functional units that generate dynamic content or provide specific features. They don't inherently have a visual form and their output can vary widely.
  • Boxes are a visual design element in Composr, essentially containers that visually group content on a page and often with a title at the top.

In practice, blocks often place their content within a box, but this isn't a requirement / standard.
Question Can I customize the appearance of blocks?
Answer Yes, you can customize the appearance of blocks by editing the associated templates and CSS. Each block typically has a corresponding template file (e.g., BLOCK_MAIN_NEWS.tpl for the main_news block) that controls its HTML structure. You can modify this template to change the layout and styling of the block's output.

An easy way to do this is through the template editor in Admin Zone > Style > Themes, and click edit templates for the relevant theme.

Top 10 Entries

Website PDStig, LLC
Screenshot Image
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 Image
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.