|
42.
|
|
|
Errors (✗) shown above won't stop the upgrade from happening, but may be indicative of a need for manual intervention after the upgrade is finished. Please keep a copy of them (put them into a document for safe keeping).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]FU_THEME_ERRORS
|
|
43.
|
|
|
Go ahead and upgrade themes
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]FU_THEME_UPGRADE_FINAL
|
|
44.
|
|
|
This will attempt to merge in default theme changes to your custom theme CSS. This is not perfect, it will likely result in some small theme errors that you would need to fix manually. Unless the upgrade specifies major theme changes, this step is not necessary. Are you sure you want to do it?
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]FU_WILL_MERGE
|
|
45.
|
|
|
Do a database upgrade (upgrade/install core-database/modules/blocks)
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]FU_DATABASE_UPGRADE
|
|
46.
|
|
|
<em>(Only needed for feature/major upgrades)</em>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]FU_NOT_FOR_PATCH
|
|
47.
|
|
|
Carefully (re)read the upgrader tutorial
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]FU_TUTORIAL
|
|
49.
|
|
|
ocProducts cannot make any guarantees about the speed of which any new bugs might be patched. It is your own responsibility to make and test a full website backup (files and database) before you upgrade, for if you need to roll-back.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]FU_BUGS
|
|
50.
|
|
|
Release notes
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]FU_RELEASE_NOTES
|
|
51.
|
|
|
Read the release notes in the announcement for the version you are upgrading to.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]FU_REFER_RELEASE_NOTES
|
|
52.
|
|
|
Upgrade steps
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]FU_UPGRADE_STEPS
|