• General: Private messages are often combined into private topics.
• phpBB: Usergroup configuration and HTML entities may require manual adjustments after import.
• vBulletin: Calendar recurrences, ratings (karma), and 'goes to coventry' are not imported perfectly. Attachments may need to be extracted directly from the live database due to potential corruption in SQL dumps.
• Simple Machine Forum: Banning features may not import perfectly due to differences in how Composr handles bans.

• Forum Software: Invision Board, MyBB, phpBB, Simple Machine Forum, vBulletin
• Content Management Systems: WordPress
• Special Importers: HTML website importer, Composr merge (for merging another Composr site)

• On the old server, ZIP the entire Composr directory.
• Download the ZIP file to your computer.
• Upload the ZIP file to the new server using SFTP/FTP.
• On the new server, unzip the file.

• On the old server, create an SQL dump of your database using the mysqldump command or phpMyAdmin.
• Download the SQL dump file.
• If your URL is changing, search and replace the old URL with the new one in the SQL dump file.
• Upload the SQL dump file to the new server.
• Restore the database on the new server using the mysql command or phpMyAdmin.

• File Permissions: After transferring files, ensure correct file permissions are set on the new server. You can use the fixperms.php script, the upgrader script, or manually adjust them.
• Configuration: If database settings are different on the new server, update the _config.php file or use the config_editor.php script to change the settings for both the site and forum databases.
• Base URL: If your URL has changed, update the base URL setting in the Installation Options editor (config_editor.php).
• Caches: Clear the block cache using the upgrader.php script.

• Direct reference by URL: Include the library's URL in your theme's HTML.
• Composr's JavaScript API: Use Composr's API for organized inclusion and potential future compatibility benefits.
• Manual integration: Directly include the library's code in appropriate template files.

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.