adam/Piwigo
1
0
Fork 0
mirror of https://github.com/Piwigo/Piwigo.git synced 2026-08-11 03:03:01 +02:00
Code Issues Packages Projects Releases Wiki Activity

Create page explaining how to publish an extension on PEM

HWFord
2026-04-28 10:34:49 +02:00
parent 7da9ad339c
commit c5be9c2a99
1 changed files with 35 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Publishing-an-extension.md
+35
@@ -0,0 +1,35 @@
# Publishing an extension on PEM
Once you extension is ready you can publish it via the <a href="https://piwigo.org/ext/" target="blank"> Piwigo extension manager</a> (PEM).
Either create an account or login. On your user page, accesible via clicking on your username in the menu you need to add an extension with a name and a category
<img width="700" height="auto" alt="image" src="https://github.com/user-attachments/assets/423febdc-fbb8-4e9a-893e-86e46744663d" />
<img width="700" height="auto" alt="Screenshot 2026-04-28 095857" src="https://github.com/user-attachments/assets/f9f204a2-68bf-44e7-a2c4-07f5ed76fa0c" />
<br><br>
The success message contains a link directly to the extension page.
On this page you can edit all information relative to the extension (image, description, authos ...) These are accessible via the edit mode switch at the top of the page.
To be able to publish the extension a revision is needed. Before adding a revsion you need to add the svn/git configuration. We strongly suggest having the extension in a github repository.
<img width="700" height="auto" alt="Screenshot 2026-04-28 100511" src="https://github.com/user-attachments/assets/e9f6d648-00f2-48b2-9d2d-fe4fb355f560" />
Once saved some other svn/git settings are automaticlaly filled. There should be no need to changes these settings. The only one that could be modified is the Archive root directory which should be the ID of the plugin defined in main.inc.php of the plugin code
<img width="700" height="auto" alt="Screenshot 2026-04-28 100710" src="https://github.com/user-attachments/assets/9e71ad04-bec5-45e8-9015-7333d609f846" />
<br><br>
The next step is to add a revision
<img width="700" height="auto" alt="Screenshot 2026-04-28 102013" src="https://github.com/user-attachments/assets/ec2e0d76-c55a-409a-843c-dc298a576024" />
Except for a few plugins, the plugins versions should be name using the current version of piwigo followed by alphabetical letters for each new version. With each new Piwigo version the main number of the extension version should also change. For example: 16.a, 16.b, 17.a, 17.b, 17.c, 18.a ...etc
<img width="700" height="auto" alt="Screenshot 2026-04-28 101030" src="https://github.com/user-attachments/assets/b5d6d511-1a6b-4fa8-9d8d-63f1f9ddc235" />
Once at least one revision exists the extension is published and any Piwigo user can add it to their Piwigo via the administration interface.