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

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.

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.

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.

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

• 32-bit PHP build: Files larger than 2GB are not supported.
• 64-bit PHP build: Files larger than 2GB are supported, but the file size will not be displayed.

• Protection from hackers: Uploaded files are stored with obscured filenames, preventing direct access and bypassing of the download system. Additionally, an anti-leech feature (when enabled) prevents direct download links from being shared on other websites (this is done by requiring a session ID which is validated against the person / device accessing it and only provided when Composr presents the download links to you on the site).
• Basic security: Composr will not let anyone upload dangerous scripts (such as PHP files) which can be executed.
• Rootkit detection: The rootkit detection tool under yourbaseurl/rootkit_detection.php can help scan files for shell scripts and backdoors. Composr's Health Check can also do this regularly. Note this only offers very basic detection and will not work for obfuscated backdoors (you should use antivirus to scan for those).

• Create a new container gallery (e.g., with codename "downloads").
• Change the "Create download galleries under" configuration option to your new gallery's codename.
• Use Commandr to move existing galleries to the new location.

• 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

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

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