To upgrade follow the steps in your website's http://mybaseurl/upgrader.php script. You will need to copy the URL of the attached file (created via the form below) during step 4. As this is more than just a patch release it is crucial that you also choose to run a file integrity scan and a database upgrade.
Please make sure you take a backup before uploading your new files!
Your upgrade to version 11 beta1
Make a Composr upgrader
You can generate an upgrader from any version of Composr to any other version. If you access this upgrade post via the version information box on your Admin Zone dashboard then we'll automatically know what version you're running. If you'd prefer though you can enter in your version number right here:
Required field *
This is the first version of v11 that supports upgrades from v10. Please be aware of the following:
- The upgrader has not yet been tested for upgrading v10 sites with any code customisations (such as non-bundled addons)
- We have not yet tested third party API connections.
- The upgrader may still be unstable; only upgrade using a test v10 site. Please report any issues you encounter to the tracker.
- The upgrader does not (and will not) support upgrading non-bundled addons. You will likely see a bunch of alien files on the file integrity scan if you have non-bundled addons. After finishing the main upgrader, you can upgrade non-bundled addons which are hosted on composr.app through "Launch site in safe mode" > Admin Zone > Structure > Addons (not officially tested yet; will be fixed in upcoming beta releases; please report issues to the tracker).
- The upgrader now forcefully runs in safe mode so non-bundled addons do not break the upgrade process.
Be aware that we do not officially support upgrades from 11.alpha to 11.beta. although upgrading should be possible. It is highly recommended to start with a fresh install if you experience major issues.
- If you are on a version before 11.alpha4, you must upgrade to 11.alpha4 before you can upgrade to 11.beta1
- 11.beta1 introduces some database changes that may break 11.alpha sites. You may wish to run the "Check for MySQL database schema issues" tool after upgrading.
- We have some patch code in the upgrader to handle most of the breaking changes from 11 alpha to 11 beta. But we do not guarantee it is perfect, especially for non-bundled addons.
The following tracker issues have been resolved since version 11.alpha4…
- Accessibility labels incorrect for multi fields [core_form_interfaces]
- Not all error messages are being sanitised by _sanitise_error_msg [core]
- Cannot add gallery media to sub(sub)categories [galleries]
- Blog tab in Profile is missing and no way to enter one. [General / Uncategorised]
- To many emails upon logging in. [core_cns]
- Site messaging JSON is broken [actionlog]
- auto_thumbs filename conflicts [core]
- Consider configurable point discounts [ecommerce]
- Add ability to send e-mails as site with defined template and create Support Ticket [tickets]
- Cannot add a download category; parent_id not defined [downloads]
The following changes were made via git since version 11.alpha4…
- Remove installer from homesite
- Login block issues and invalid filtering on either_param_string
- Newsletters: cannot use bcrypt for hash checking
- Incorrect variable name
- Incorrectly copying default notification settings when creating an account
- Account deletion should be added to the task queue
- Merge branch 'refs/heads/v11' into cms_homesite_v11
- Make scheduler optimise other caches too, not just static cache
- Merge branch 'refs/heads/v11' into cms_homesite_v11
- Add support for having scheduler hooks disabled by default + misc changes
- Actually this should run at end of script in the event the task queue is inactive
- member_boxes bug
- Ignore CONFIG_CATEGORY_COMPOSR_APIS in telemetry
- Whoops
- Add ability to mass-ignore / mass-resolve relayed errors
- Merge branch 'refs/heads/v11' into cms_homesite_v11
- Wrong variable
- Merge branch 'refs/heads/v11' into cms_homesite_v11
- Add catch for DEFAULT_BRAND_NAME
- Wrong endpoint name
- Digest counts can get really high really quickly; make hook execute every hour
- Allow 256kb digests
- Fix overlay scrolling on mobile
- Fix _do_next_manager params in CMS modules
- banner_codename should allow blank for reading on purchase screen
- Add link to codebook 3 on tut_disaster which explains error logs
- Be smarter about when to log a failed login as an actual failed login
- Remove nulls at end of parameters in legacy code
- Tick rebuild SQL by default if database upgrade was specified required
- Also tick omni-upgrader by default if old and new version is equal (likely testing in that case)
- Oops that needs to be strict equality
- No idea why these did not commit...
- Update build info
- Use a more standard API for page-link checking
- Also page-link on admin zone
- Make it not display for members
- Missing doc images
- Merge branch 'refs/heads/v11' into cms_homesite_v11
- Force site_messaging install for next release
- Improper tutorial link generation
- Improve improveStickyForMobile
- Whoops, forgot to rename the variable
- Incorrect ordering of fields and modules in catalogue_category meta
- Always use md5 in url_to_filename to help prevent clashes with truncation in image thumb names
- Add auto_thumbs to cache clearing hook because it's temporary and can get very populated
- Add eCommerce support for karma (remove member comments support)
- Fix custom member boxes; Karma member box
- Fixes to upgrader issues (v10->v11)
- More fixes regarding the upgrader and database indices (WIP)
- Various fixes to the ticket e-mail system and upgrader
- Various make release fixes for missing files and optimisation
- Other tweaks to make release
- Must use is_file to properly ignore directories
- Wrong array key
- Avoid having to use immediate installs
- Update list of files to immediately upgrade
- Port upgrader enhancements from v10
- Forgot one portion of the port
- Upgrader should always update archived addons when possible
- Fix backwards variables
- Type error
- Merge branch 'refs/heads/v11' into cms_homesite_v11
- Incorrect null check
- Update weighted polls to use life-time points, not points balance
- Improve voting power calculator by using a graph instead of an export
- Generalise parental consent language as this section will be expanded from other laws in the future
- Database field naming consistency fixes (WIP)
- Additional database integrity fixes (WIP)
- Additional database integrity fixes (WIP)
- Unit test fixes
- Update build info
- integrity should come after outputting stack trace in upgrader errors
- Force safe mode in the upgrader so corrupt non-bundled addon overrides do not break it
- part of ecommerce upgrade must happen in version_specific
- Instead of forcing safe mode, just gracefully return on corrupt override
- No easy way to make upgrader work without safe mode
- Do not use red alert boxes for critical errors in upgrader
- _sanitise_error_msg should account Windows paths
- Do not warn_exit for attach_message in minikernel except for warn
- Support attach_message on failed overrides with $fail_ok true
- override api changes
- Clarify alien file detection for new extracted addons
- Do not upgrade non-bundled addons in the upgrader
- use URL parameter as fallback when bailing from in_safe_mode
- Should use page link, not path, for t_type_id
- Misc improvements to warnings
- ModSecurity may block ? and = entities
- Unit test fixes
- Missing table creation in purchase module
- DB schema rebuild
- Wrong version for calendar module upgrade db integrity fix
- Note about updating addon versions in make release
- Clarify underscore meaning in tests
- Upgrader: buttons going to site should not use POST forms
- Fix basic_code_formatting test (make line number of unicode explicit, fix failing file which had a BOM on it)
- Type strictness fixes
- fixed: backdoor ip generating new sessions each time
- Merge remote-tracking branch 'origin/v11' into v11
- Remove twitter_support non-bundled addon
- Remove twitter_support references
- Use ZipArchive; remove m_zip / unzip_cmd support
- Fix comcode_code test
- Merge branch 'v11' of gitlab.com:composr-foundation/composr into v11
- Add support for checking incompatible addons
- addon dependencies and files should be updated in db for upgrades
- Also need to update dependencies and files in file upgrade
- Force safe_mode in file integrity when there are incompatible addons
- Clean up db for blocks and modules removed in v10
- Create admin session when entering safe mode from upgrader
- Do not force _config.php safe mode
- Misc upgrader fixes
- Force loading non-bundled addon hooks on admin-addons in safe mode
- Upgrade db fixes
- Modularisation fixes
- Automated test fixes
- New build
- Merge branch 'refs/heads/v11' into cms_homesite_v11
- REVERT build; attempted database repair fixes
- Merge rank tab in from another project
- Cache cleanup should not limit by extension but ignore access controllers
- Consistency fixes for rank tab
- Improve upgrader steps workflow
- Set addon max CMS version to 11.9 so we force an upgrade in v12
- Re-add missing install.php
- Recover other missing installer files
- Use new dummy_data endpoint for _http_timeouts test
- Finalise dummy_data endpoint
- Failed attempt to get rootkit_detection working
- Add hash comparisons to addon manifest as additional redundancy
- Lang fix
- Fix db indexing issues; fix upgrader issues; generate db_meta before making build
- Test suite fixes
Special thanks to these members for resolving the issues above:
Special thanks to these members for reporting the issues above:
Special thanks to these individuals who contributed code to the git repository for this release:
- Lovinity (Patrick Schmalstig)
- Chris Graham
Comments
EDIT: Having trouble applying hotfixes (no files extracted)? See 0005799: Hotfixes via upgrader extracted no files - Composr CMS feature tracker
To fix, see Too many END directives (6105075e) · Commits · Composr ecosystem / Composr · GitLab (you can download the new file from Gitlab and replace it in themes/default/templates, then in Admin Zone > Tools > Cleanup Tools, clear your Block cache and Template cache)