|
9 | 9 |
|
10 | 10 | # Upgrade add-on products |
11 | 11 |
|
12 | | -```{admonition} Description |
13 | | -The steps to take to migrate your third party products |
14 | | -``` |
| 12 | +This chapter describes the steps to migrate your third party products. |
15 | 13 |
|
16 | | -- Shut down your Plone server instance. |
17 | | -- If you specified concrete versions of the third-party products in your *buildout.cfg* file (so-called "pinning", and a recommended practice), like *Products.PloneFormGen* = 1.7.17, update these references to point to the new versions. |
| 14 | +- Shut down your Plone server instance. |
| 15 | +- If you pinned versions of third-party products in your `buildout.cfg` or other configuration files, such as `Products.PloneFormGen = 1.7.17`, update these references to point to the new versions. |
18 | 16 |
|
19 | | -```{note} |
20 | | -Without pinning, i.e. specifying only, for example, *Products.PloneFormGen* and no version, buildout will pick the newest version of the products by default. |
21 | | -``` |
| 17 | + ```{note} |
| 18 | + Without pinning, such as specifying `Products.PloneFormGen` without a version number, your build tool, buildout or make, will pick the newest version of the products by default. |
| 19 | + ``` |
22 | 20 |
|
23 | | -- Run *bin/buildout*. Wait until all new software is downloaded and installed. |
24 | | -- Start Plone again - your site may look weird, or even be inaccessible until you have performed the next step |
25 | | -- Navigate to the Add-on screen (add `/prefs_install_products_form` to your site URL, and upgrade products if you can (products that support both your current and new version of Plone). |
26 | | - : - Perform product-specific upgrade procedures (if any). |
27 | | - - You will find these in the documentation of each product. |
| 21 | +- Run your build tool. |
| 22 | + Wait until all new software is downloaded and installed. |
| 23 | +- Start Plone again. |
| 24 | + Your site may look weird, or even be inaccessible, until you perform the next step. |
| 25 | +- Navigate to the Add-on screen by adding `/prefs_install_products_form` to your site's URL. |
| 26 | + Upgrade products if you can. |
| 27 | + Upgradeable products would be those that support both your current and new versions of Plone. |
| 28 | +- Perform product-specific upgrade procedures, if any. |
| 29 | + You will find these in the documentation of each product. |
28 | 30 |
|
29 | | -Should the `/prefs_install_products_form` be unreachable, you should try doing the add-on upgrades from the Management Interface. |
| 31 | +If `/prefs_install_products_form` is unreachable, you should try doing the add-on upgrades from the Management Interface. |
30 | 32 | Navigate to the quickinstaller in the Management Interface, and reinstall or upgrade products that are shown to be outdated. |
31 | 33 |
|
32 | | -```{note} |
| 34 | +```{warning} |
33 | 35 | Be careful when updating add-ons through the Management Interface. |
34 | | -It may show outdated themes as well with a hint to update. |
| 36 | +It may show outdated themes as well, with a hint to update. |
35 | 37 | If you do that, the updated theme will activate itself, overriding your current theme. |
36 | 38 | If this happens, re-enable your theme in the theming panel. |
37 | | -``` |
| 39 | +``` |
0 commit comments