Skip to content

Commit 52be53b

Browse files
authored
Merge pull request #444 from AkameOuO/fix-broken-anchors
Fix broken anchors
2 parents ee17563 + 202d161 commit 52be53b

File tree

1 file changed

+9
-9
lines changed
  • docs/building-extensions/install-update/installation

1 file changed

+9
-9
lines changed

docs/building-extensions/install-update/installation/package.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ A package extension is created by zipping all .zip files of the indivudal extens
1818
- system plugin helloworld
1919
- template helloworld
2020

21-
then the package should have the following tree within the `pkg_helloworld` folder:
21+
then the package should have the following tree within the `pkg_helloworld` folder:
2222

2323
```
2424
pkg_helloworld
@@ -33,7 +33,7 @@ pkg_helloworld
3333
3434
```
3535

36-
The `pkg_helloworld.xml` manifest file could have the following contents:
36+
The `pkg_helloworld.xml` manifest file could have the following contents:
3737

3838
```xml title="pkg_helloworld.xml"
3939
<?xml version="1.0" encoding="UTF-8" ?>
@@ -60,7 +60,7 @@ The `pkg_helloworld.xml` manifest file could have the following contents:
6060
</extension>
6161
```
6262

63-
You then zip up the `pkg_helloworld` folder and install the package extension in the normal way.
63+
You then zip up the `pkg_helloworld` folder and install the package extension in the normal way.
6464
When you go to Manage Extensions you will then see:
6565
- an entry for the overall helloworld package, and,
6666
- entries for each of the constituent extensions within the package.
@@ -81,25 +81,25 @@ So in this case the manifest file must be named `pkg_helloworld.xml`.
8181

8282
When you uninstall a package Joomla looks for a manifest file named `pkg_<packagename>.xml` and if you don't name it correctly then the uninstall will fail with Joomla reporting that it can't find the manifest file.
8383

84-
### `id` attribute
84+
### `id` attribute
8585

86-
Within the `<file>` element of each constituent extension the `id` attribute must match the `element` column of that extension's record in the `#__extensions` table.
86+
Within the `<file>` element of each constituent extension the `id` attribute must match the `element` column of that extension's record in the `#__extensions` table.
8787

88-
(See the [Metadata](manifest.md#metadata) and [Front-end Files](manifest.md#front-end-files) sections for some explanation of how this `element` field is set).
88+
(See the [Metadata](manifest.md#metadata) and [Frontend Files](manifest.md#frontend-files) sections for some explanation of how this `element` field is set).
8989

9090
When you uninstall a package Joomla uses this information in the manifest file to perform a database lookup in the `#__extensions` table to find each constituent extension. If you don't set this correctly then Joomla will not uninstall that constituent extension.
9191

9292
### Plugin `group` attribute
9393

94-
The `group` attribute is required for the package installer to locate the plugin for uninstall.
94+
The `group` attribute is required for the package installer to locate the plugin for uninstall.
9595

96-
Group refers to the `group` attribute specified within the `<extension>` element of the plugin manifest file, and matches the subfolder name under the Joomla /plugins directory.
96+
Group refers to the `group` attribute specified within the `<extension>` element of the plugin manifest file, and matches the subfolder name under the Joomla /plugins directory.
9797

9898
### `blockChildUninstall` tag
9999

100100
Use this tag to prevent an administrator from uninstalling individually a constituent extension of your package.
101101

102-
If you omit this tag or have
102+
If you omit this tag or have
103103

104104
```xml
105105
<blockChildUninstall>false</blockChildUninstall>

0 commit comments

Comments
 (0)