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 Can I integrate a dedicated issue management system with Composr?
Answer While Composr doesn't have a built-in issue tracker, a non-bundled addon (cms_homesite_tracker) provides an integrated, modified version of Mantis. Additionally, the Support Ticket system can function as a basic private issue tracker using features like Post Templates.
Question How can I restrict access to the support system to specific users?
Answer Utilize Composr's page access permissions to control who can access the Support Ticket page. This ensures only authorized users can submit support requests.

You can also control permissions based on ticket type when adding or editing a ticket type. Make sure if you go this route that the Support Ticket page permissions are very liberal (e.g. allow anyone to access, or just restrict to guests if you will never allow guests to make tickets). Otherwise, some people cannot make tickets even if they have permission on the type.
Question What are Post Templates and how are they beneficial for support?
Answer Post Templates are predefined text blocks that can be used as templates for new forum posts. They are particularly useful in support scenarios by:
  • Providing quick responses to common questions.
  • Ensuring consistency in staff responses.
  • Saving time and effort for staff.

Post Templates can be configured to be the default post in specific forums or restricted to certain user groups.

Go to Admin Zone > Structure > Forums > Post Templates.
Question How does Composr handle email integration for support?
Answer Composr can integrate with email for ticket management, assuming certain requirements are met:
  • PHP IMAP extension installed.
  • Functional PHP mail command (local SMTP server or configured Windows SMTP settings).
  • Active system scheduler (Cron).

With email integration, users can submit tickets via email, and staff can reply through the system. Composr cleans up email text for ticket clarity and allows forwarding emails to the integrated address for efficient handling.
Question How can I categorize and prioritize support requests?
Answer Support Ticket System: Utilize support ticket types, managed in the Admin Zone > Setup > Support tickets. Staff can set individual notifications for different types.

Discussion Forums: Create dedicated subforums for different support categories or priority levels.

Feedback System: The content to which the feedback is attached implicitly categorizes it. For prioritization, subforums can be used.
Question What are the advantages of using the Support Ticket system over the Discussion Forums?
Answer While both systems can be used for support, the Support Ticket system provides advantages like:
  • Separating replies into individual tickets.
  • Ticket assignment to specific staff members.
  • Tracking who has read a ticket.
  • Private replies between staff members.
  • Filtering tickets by type.
  • Automatic ticket creation, unlike manually creating forum topics.
  • Conflict detection when multiple staff are working on the same ticket.
  • Real-time alerts and display updates upon ticket replies.
Question How can Composr be used as a support desk tool?
Answer Composr offers three main systems for providing online support:

1. Support Ticket System: This system allows users to submit tickets and staff to respond, track, and resolve them. It features email notifications, ticket categorization and prioritization, staff assignment, and attachment support.

2. Discussion Forums: Conversr, Composr's built-in forum software, can be utilized for support by creating dedicated forums or subforums. Features like post templates and multi-moderations enhance support capabilities.

3. Feedback System: This system allows for comments on various content types, facilitating support directly related to that content.
Question How can I access the raw data behind the statistics graphs?
Answer Every graph in Composr offers a spreadsheet export option. This allows you to download the data in a spreadsheet format, enabling detailed manual review or further analysis using third-party tools.
Question How are time zones handled in Composr statistics?
Answer All times in Composr statistics are displayed according to the configured website time zone, regardless of visitor or user account time zones. While this is a limitation due to pre-computation, some graphs displaying hourly stats and country filtering offer insights into local times for manual analysis.
Question What are the limitations of pre-computed statistics in Composr?
Answer Pre-computed statistics introduce certain limitations:
  • Filtering constraints: Limits filtering options to those incorporated in the data structure.
  • Historical data limitation: To maintain site stability, statistics older than 31 days aren't pre-processed. This may lead to data gaps if the system scheduler malfunctions or statistical data is manually deleted.