Skip to content

Commit 60e06f6

Browse files
committed
Update Readme
1 parent d7bd37c commit 60e06f6

File tree

2 files changed

+10
-2
lines changed

2 files changed

+10
-2
lines changed

README.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,18 @@ example:
1515
- Store associated details, for example the author(s) of a document,
1616
year of issue, duration of a music track ...
1717

18-
## Installation / Deinstallation
18+
## Installation / Deinstallation / Upgrading
1919

2020
### Installation
2121

2222
Paste the `.txt` installer code into the *Admin › Plugins* panel, or
2323
upload the plugin's `.php` file via the *Upload plugin* button, then
2424
install and enable the plugin.
2525

26+
### Upgrading
27+
28+
The plugin automatically migrates custom field data and the database structure from the earlier single custom field variant (v0.1) to the new format. No changes are needed to the public tags as the new default settings correspond to the old tag. Nevertheless, it is always advisable to make a database backup before upgrading.
29+
2630
### De-installation
2731

2832
The plugin cleans up after itself: deinstalling (deleting) the plugin

README.textile

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,16 @@ Use whenever extra information needs to be stored with a file. For example:
1010
* Store associated details, for example the author(s) of a document, year of issue, duration of a music track …
1111

1212

13-
h2. Installation / Deinstallation
13+
h2. Installation / Deinstallation / Upgrading
1414

1515
h3. Installation
1616

1717
Paste the @.txt@ installer code into the _Admin › Plugins_ panel, or upload the plugin's @.php@ file via the _Upload plugin_ button, then install and enable the plugin.
1818

19+
h3. Upgrading
20+
21+
The plugin automatically migrates custom field data and the database structure from the earlier single custom field variant (v0.1) to the new format. No changes are needed to the public tags as the new default settings correspond to the old tag. Nevertheless, it is always advisable to make a database backup before upgrading.
22+
1923
h3. De-installation
2024

2125
The plugin cleans up after itself: deinstalling (deleting) the plugin removes the extra columns from the database as well as custom field names and labels. To stop using the plugin but keep the custom field data in the database, just disable (deactivate) the plugin but don't delete it.

0 commit comments

Comments
 (0)