Featured Sites: A-Z Index

H


Newest 10 Entries

Name Robert Goacher
Photograph Image
Title / Role Founder
Contributions / Notes

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

Name Chris Graham
Photograph Image
Title / Role Founder
Contributions / Notes

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.

Links

gameRevolt (@[email protected]) - LinuxRocks.Online

Website Earth & Sky
Screenshot Image
Short Description Earth & Sky is a Composr v11 gallery website showcasing natural photography by Mark Brunner.
Website Saving Wallden
Screenshot Image
Short Description This is an informational website for a Visual Pinball X game in development called "Saving Wallden". The site features the planned game rules, development news, and a download of the game as it is so far.
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: Content management meets social media
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.

Top 10 Entries

Question What does it mean to "outmode" a download?
Answer Outmoding means marking a download as superseded or replaced by a newer version. When editing the older download, you link it to the new one in the "outmode" field. This makes it clear to users that there is a newer version available. This is handy especially if you provide software.
Question What are the different ways to add downloads to my Composr site?
Answer Composr offers several methods for adding files to the download system:

  • Uploading via web form (when adding a download in the Content Management Zone): This is the simplest method, where you attach the file directly when defining the download details. However, it's not suitable for large files and can be affected by unreliable internet connections.
  • Uploading and referencing the URL: You can manually upload the file using FTP/SFTP/SCP and then provide the URL to the file in the 'Add download' form. While this is better for large files, it requires additional
 access, and the file isn't managed directly by Composr.
  • Batch adding from an FTP server: This allows staff to add multiple downloads from an FTP server in one go using FTP URLs. It's efficient for bulk uploads but requires separate addition of descriptions.
  • Batch adding from a directory: Similar to the FTP method, staff can add downloads from a web server directory accessible by URL.
  • File/media library (filedump): Webmasters can use any of the above methods to upload a file to uploads/filedump and then reference it in a download. This is especially handy if you are going to reference the file more than once on your site.
Question What is the Composr Setup Wizard and what does it do?
Answer The Setup Wizard is a guided process to help you configure essential settings for your Composr website after installation.

It can:
  • Generate a default theme and logo
  • Set initial site options
  • Remove predefined content and unnecessary addons
  • Place initial blocks on your pages

While convenient, be aware that re-running the Setup Wizard may overwrite existing settings and customizations if you already configured your site.
Question How can I change the structure of my Composr website's pages?
Answer You can delete and move pages using the Admin Zone > Structure > Sitemap editor. However, moving pages between zones might invalidate existing page-links unless specified using the _SEARCH zone in the link.

To avoid issues with existing links and search engine indexing, consider setting up redirects when moving pages. This can be done through Admin Zone > Structure > Redirects.

It is recommended not to move default Composr pages as it can complicate future upgrades.
Question What are Installation Options and how can I change them?
Answer Installation Options are low-level settings for Composr, such as database details and default language.

You can access the Installation Options editor through:

  • The script: http://yourbaseurl/config_editor.php
  • The Admin Zone: Admin Zone > Setup > Configuration > Installation Options

Remember that you'll need your maintenance password, specified during installation, to access and modify these options.
Question How do I open or close my Composr website to the public?
Answer By default, your Composr site is closed after installation. To open it to the public (or to close an opened site), go to Admin Zone > Setup > Configuration > Site options > Closed site and adjust the setting accordingly. You can also configure a closed site message.

While a closed site prevents public access, it's worth noting that users can still join a closed Conversr-powered site if they have access to the join module URL. However, they won't be able to log in unless they're assigned to a usergroup with "Access closed site" permissions. You can modify the join module's permissions to restrict access further.
Question What is the .htaccess file and how does it relate to Composr?
Answer The .htaccess file is a configuration file for the Apache web server. It allows you to define settings that apply to the directory where it's located and its subdirectories.

Composr can leverage .htaccess to enhance security and enable features like "URL Schemes." You can try renaming the provided recommended.htaccess file to .htaccess. This file includes recommended options that tighten security and ensure Composr has necessary PHP and Apache features activated.

Note that some web hosts might restrict the use of .htaccess files.

You should regularly review recommended.htaccess for changes between Composr updates.
Question How do Composr permissions work?
Answer Composr employs a multi-layered permission system with two main types: privileges and access permissions. The system grants users the best possible access based on the combination of their usergroups.

Privileges define broad permissions, such as accessing a closed site or content manipulation abilities based on impact level (low, medium, high). You can set privileges for usergroups via checkboxes, with the option to override them for specific pages or categories. Go to Admin Zone > Security > Global privileges.

Access permissions control what content users can view. These permissions are layered:

  • Zone access permissions
  • Page (or content entry) access permissions
  • Catalogue access permissions
  • Category access permissions

To configure access permissions, you can edit the specific resource or utilize the Permissions Tree Editor under Admin Zone > Security > Permissions Tree Editor.
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.