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

As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site.

We will be releasing several beta versions in the beta phase.

We do not know when we will be able to release the first Release Candidate or stable versions at this time.

These plans are all subject to change without notice.

• $SITE_INFO['disable_smart_decaching'] = '1';
• $SITE_INFO['no_disk_sanity_checks'] = '1';
• $SITE_INFO['hardcode_common_module_zones'] = '1';
• $SITE_INFO['prefer_direct_code_call'] = '1';
• $SITE_INFO['charset'] = 'utf-8';
• $SITE_INFO['known_suexec'] = '1';
• $SITE_INFO['dev_mode'] = '0';
• $SITE_INFO['no_extra_logs'] = '1';
• $SITE_INFO['no_extra_bots'] = '1';
• $SITE_INFO['no_extra_closed_file'] = '1';
• $SITE_INFO['no_installer_checks'] = '1';
• $SITE_INFO['assume_full_mobile_support'] = '1';
• $SITE_INFO['no_extra_mobiles'] = '1';

• Go to the Installation Options editor (yourbaseurl/config_editor.php). You will need your maintenance password.
• Activate the static cache option.

• Language cache: Eliminates the need to parse language files on each page load.
• Template cache: Avoids reparsing template files repeatedly.
• Comcode page cache & Comcode cache: Reduces the need to parse Comcode pages and general Comcode usage.
• Block cache: Caches blocks based on their parameters, minimizing execution.
• Theme image cache: Prevents redundant searches for theme images.
• Values caches: Stores calculated values like member post counts.
• Persistent cache: Keeps frequently used data in memory for faster access.
• Advanced admin cache: Allows admins to view cached pages while the server generates updates.
• Static cache: Serves static pages to bots and guests, bypassing much of the framework.
• Self learning cache: Optimizes resource loading by learning which resources each page requires.

• Check Email Logs: View the email log (Admin Zone > Audit > E-mail queue/log) to see what notifications have been sent.
• Use the SU Feature: Impersonate a member using the SU feature (described in the "Testing access and privileges" tutorial) to view their notification settings and confirm they are set up correctly.
• Enable Carbon-copy Email: Configure a "Carbon-copy e-mail address" in the configuration settings to receive copies of all outgoing emails, including notifications. This helps you monitor email delivery.
• Verify System Scheduler: Ensure the system scheduler is configured correctly if members are not receiving digest emails.
• Check Digest Settings: Confirm that "Enable digest notifications" is enabled in the Messages configuration settings.
• Review "Safety listing limit": If a notification has too many categories, members might not see the full selection tree. Adjust the "Safety listing limit" in the configuration settings if necessary.

• Notification Defaults: You can set default notification preferences for all members. You can enable or disable specific notifications and choose the delivery method (Admin Zone > Setup > Notification defaults).
• Notification Lock-down: You can force members to receive or prevent them from receiving certain notifications (Admin Zone > Setup > Notification lock-down). This allows you to enforce specific notification policies and manage email volume.

• Content Updates: Notifications for new or updated content, such as news articles, forum posts, and gallery images.
• Private Messages: Alerts for new private messages received.
• Friend Requests: Notifications for new friend requests.
• Administrative Actions: Alerts for actions taken by site administrators, such as account approvals or content moderation decisions.

• Email: Notifications sent directly to their email address.
• Digest Email: Combined summaries of activity sent in batched emails. This requires the system scheduler and the digest e-mails configuration option to be enabled.
• Private Topics: Notifications delivered as private forum topics.
• SMS: Notifications sent as text messages (requires configuration and incurs costs).
• Web Notifications: Real-time alerts displayed within the Composr interface.

• Rank ladders: Use the default rank ladder for main site ranks and secondary usergroups for subcommunity memberships.
• New member status: Set default usergroups for new members to grant them initial access while allowing removal if necessary.
• Leadership: Assign leaders to usergroups to allow members to manage subcommunities.
• Clubs: Consider using Clubs for member-driven subcommunities with their own forums.

• No special permissions by default, simplifying permission management.
• Members can join and leave like regular usergroups.
• Provide a dedicated forum for the club.