Featured Sites: A-Z Index

H


Newest 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.

Top 10 Entries

Question Can I leave notes for myself or other staff members?
Answer Yes, the Admin Zone includes a dedicated "Notes" block for you and your staff to leave messages and reminders. This space serves as a shared communication hub for your team.
Question How can I stay informed about the latest Composr version?
Answer The Admin Zone dashboard displays information about your current Composr version and alerts you if it's not the most recent one. A link will be provided to guide you through the upgrade process if necessary.
Question What is the action log, and how can I use it?
Answer The action log keeps track of administrative and content-related actions on your website. It allows you to see who did what and when, providing valuable insights into site activity and accountability. You can filter the log to focus on specific actions, users, or timeframes. It's also helpful for revisiting previous tasks by providing links to the relevant content or settings.
Go to the Admin Zone > Audit > Action logs. A quick action log block is also available on the dashboard.
Question What is the staff checklist in the Admin Zone?
Answer The staff checklist is an automatically generated list of tasks that need attention on your website. It includes routine updates like assigning new awards or adding news, as well as less frequent but important tasks like backups, software updates, newsletters, content validation, and periodic content reviews. You can customize the frequency of these tasks in the 'Configuration' section under 'Administrative options'. You can also add your own custom tasks. Anyone with Admin Zone access can see the checklist. So you can collaborate with your highest level staff on it.
Question I'm lost! How can I find a specific feature or setting?
Answer The Admin Zone has a powerful search feature that you can access under the Help icon. It searches through various categories, including configuration options, privileges, templates, language strings, administrative modules, and more. You can even refine your search by adding "@sectionname" to the end of your search term to limit results to a specific section.
Question How do I access the Admin Zone?
Answer You can access the Admin Zone by clicking the "Admin Zone" link located at the bottom of every page on your website, assuming you are using the default theme. If you are logged in as a staff member, your user menu will also have a link to the Admin Zone or the Content Management Zone. You might be asked to log in again / confirm your session for security reasons.
Question What is the Admin Zone?
Answer The Admin Zone is a special section of your Composr website that allows authorized staff members to perform various administrative tasks. It serves as the central hub for managing content, configuring settings, monitoring activity, and maintaining the overall health of your website.
Question What should I avoid doing in Composr to maintain accessibility?
Answer Avoid using Comcode tags or other HTML elements that create dynamic effects in the user's browser, such as ticker and jumping. These can have a negative impact on navigation and scrolling.
Provide alternate information for multimedia you upload so those with auditory impairments can still understand the content.
Avoid creating multiple content items with the same title, as this can lead to accessibility issues and general user confusion.
Question How does Composr handle forms for accessibility?
Answer The web standards checker ensures that form labels are properly positioned and explicitly associated with their controls.
It also checks that form elements have a logical tab order and are keyboard operable.
Question How does Composr ensure accessible data tables?
Answer The web standards checker enforces proper markup for data tables, including identifying row and column headers, and associating data cells with header cells.
It ensures that tables are not used for layout (flex boxes and HTML grids are preferred for mobile responsiveness) unless they make sense when linearized.
Composr provides summaries for tables to aid non-visual user agents in understanding their structure and content.