• Model/API: The sources directory primarily houses scripts forming the Model/API, handling data logic and business rules.
• View: Templates in themes/default/templates represent the View, responsible for presenting data to the user. Comcode pages can also be considered part of the View.
• Controller: Entry scripts like index.php and site/dload.php act as front controllers, directing requests. Modules and blocks, residing in */pages/modules and sources/[mini]blocks, respectively, serve as controllers, managing user interactions and determining which View to render.

• Installing multiple language packs: Make sure you have at least two language packs installed.
• Enabling the Conversr multi-language option: Go to Admin Zone > Setup > Configuration > Site options > Internationalisation.
• Running a Commandr command: Execute the necessary command to set up the database structure for multi-language content (unless you already enabled Support content translations when installing).

• Template editing: You can modify templates to use different language strings based on user gender. This involves adding Tempcode logic to dynamically select the appropriate string.
• Custom Profile Fields: Create a Custom Profile Field for "Gender" and use it to conditionally display gendered language strings in templates.

• Joining the translation team on Transifex: Translate language strings collaboratively with other volunteers.
• Becoming a language maintainer: Take responsibility for the translation and support of Composr in your native language.
• Reporting translation issues: If you encounter unclear, incorrect, or duplicated language strings, file bug reports.
• Providing feedback and suggestions: Share your thoughts on improving the translation process through feature suggestions.

• Centralized translation efforts: Multiple translators can work on the same project.
• Improved translation quality: The platform facilitates consistency and accuracy.
• Simplified language pack creation: You can generate downloadable language pack addons directly from Transifex.

• Copy the EN folder: Create a new folder with the ISO code of your target language (e.g., FR for French).
• Replace the images: Replace the English images with translated versions.
• Ensure correct image paths: Update any references to these images in your templates or content to point to the translated versions.

• Editing the content directly: Go to the specific content item (page, news post, etc.) and edit it in the new language.
• Using the language editor: Access the language editor from Admin Zone > Style > Translate/rephrase Composr to modify language strings used on specific pages.

• Download the language pack: You can download language packs from the Composr website.
• Install the language pack: Upload the downloaded language pack addon through Admin Zone > Structure > Addons > Import non-bundled addon(s).
• Change the default language: Go to http://yourbaseurl/config_editor.php and set the desired language.
• Update your profile: If you had a previous language set in your profile, update it to the new language.

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