• Open a tracker issue explaining the problem and providing as much detail as possible (mark it as a major bug).
• Help the developers help you. Provide access to your site (see the software feedback tutorial for more information), describe the exact situation, and avoid protracted back-and-forth communication.
• Take backups before upgrading. This allows for easier recovery in case of problems.

• Check for duplicates: Make sure the bug hasn't already been reported.
• Report bugs individually: Each issue should be reported separately for better tracking and resolution.
• Verify it's a Composr bug: Issues with third-party addons and code should be reported to their respective developers.
• Consult the FAQ and tutorials: Check for common problems and solutions, particularly server configuration issues.
• Provide comprehensive information: Include a clear and specific title, detailed steps to reproduce the problem, your browser version, Composr version, error messages, stack traces (if available), and any other

• Use clear and concise language: Write in proper English, use correct terminology, and avoid vagueness.
• Be respectful and patient: Remember that developers are volunteers and may not respond immediately.

• Site-wide Settings: You can configure default metadata for your entire site in the Admin Zone under Setup > Configuration > Site options.
• Content-Specific Settings: When adding or editing content like Comcode pages or news posts, Composr provides fields for customizing titles, descriptions, and keywords specific to that content under the "Metadata" section.
• Automatic Detection: Composr can automatically generate metadata by analyzing your content, but it's generally recommended to refine these suggestions manually for best results.

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

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

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

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.

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

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

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.