adam/Piwigo
1
0 Fork 0
mirror of https://github.com/Piwigo/Piwigo.git synced 2026-10-30 21:52:00 +01:00
Code Issues 657 Packages Projects Releases Wiki Activity

Compatibility check for Plugins #1158

New Issue
Open
opened 2026-10-05 00:33:36 +02:00 by adam · 2 comments
adam commented 2026-10-05 00:33:36 +02:00
Owner
Copy link
Copy source

Hello,

I'm running my Piwigo installation with a lot of useful plugins. On my sandbox installation, I already upgraded to 11.3.0. The upgrade went smooth and I started activating my plugins. Some of them are marked as not compatible, but they seem to work.

I would like to know how Piwigo checks which plugins are compatible and which are not. Is there a file in every plugin that lists the versions of Piwigo that are supported?

Please give me a hint .... :-)

Merci beaucoup!

Thanks and best regards

Jens

Hello, I'm running my Piwigo installation with a lot of useful plugins. On my sandbox installation, I already upgraded to 11.3.0. The upgrade went smooth and I started activating my plugins. Some of them are marked as not compatible, but they seem to work. I would like to know how Piwigo checks which plugins are compatible and which are not. Is there a file in every plugin that lists the versions of Piwigo that are supported? Please give me a hint .... :-) Merci beaucoup! Thanks and best regards Jens <!-- github-sync-id:803778960 -->
adam commented 2026-10-05 00:33:37 +02:00
Author
Owner
Copy link
Copy source

Hi Jens,

how Piwigo checks which plugins are compatible and which are not.

Manual check. First by the plugin creator. If it takes too long, a team member takes the time to test. Hopefully it works and no change is needed. A simple edition of the last revision of the plugin to mark it as compatible and we're done. If the extension needs a change, we have 2 options:

  1. the code is hosted on our old SVN : easy, we have the ability to commit changes and publish a new version
  2. the code is hosted on Github, on their own account. We can't do much :-/ Well, after thinking, we can still use the translation user to make some changes, but it was designed for that.

What would be nice, for the future, is a system on piwigo.org/ext to declare as a tester, "I've tested with Piwigo 11 and it works". We could make the check a community effort :-)

Hi Jens, > how Piwigo checks which plugins are compatible and which are not. Manual check. First by the plugin creator. If it takes too long, a team member takes the time to test. Hopefully it works and no change is needed. A simple edition of the last revision of the plugin to mark it as compatible and we're done. If the extension needs a change, we have 2 options: 1. the code is hosted on our old SVN : easy, we have the ability to commit changes and publish a new version 2. the code is hosted on Github, on their own account. We can't do much :-/ Well, after thinking, we can still use the translation user to make some changes, but it was designed for that. What would be nice, for the future, is a system on piwigo.org/ext to declare as a tester, "I've tested with Piwigo 11 and it works". We could make the check a community effort :-) <!-- github-comment-id:775338871 -->
adam commented 2026-10-05 00:33:38 +02:00
Author
Owner
Copy link
Copy source

Hello Pierrick!

Thanks for the explanation. Let me ask one more question regarding this.
How does a new Piwigo version like 11.x know that the existing plugins are
compatible or not. They show this road sign "Attention" if they are not
compatible.

Thanks and regards

Jens

Am Mo., 8. Feb. 2021 um 19:10 Uhr schrieb Pierrick Le Gall <
notifications@github.com>:

Hi Jens,

how Piwigo checks which plugins are compatible and which are not.

Manual check. First by the plugin creator. If it takes too long, a team
member takes the time to test. Hopefully it works and no change is needed.
A simple edition of the last revision of the plugin to mark it as
compatible and we're done. If the extension needs a change, we have 2
options:

  1. the code is hosted on our old SVN : easy, we have the ability to
    commit changes and publish a new version
  2. the code is hosted on Github, on their own account. We can't do
    much :-/ Well, after thinking, we can still use the translation user to
    make some changes, but it was designed for that.

What would be nice, for the future, is a system on piwigo.org/ext to
declare as a tester, "I've tested with Piwigo 11 and it works". We could
make the check a community effort :-)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Piwigo/Piwigo/issues/1335#issuecomment-775338871, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABERJAQKJS7OCP3WRPNHIB3S6ASJ7ANCNFSM4XJNAJUA
.

Hello Pierrick! Thanks for the explanation. Let me ask one more question regarding this. How does a new Piwigo version like 11.x know that the existing plugins are compatible or not. They show this road sign "Attention" if they are not compatible. Thanks and regards Jens Am Mo., 8. Feb. 2021 um 19:10 Uhr schrieb Pierrick Le Gall < notifications@github.com>: > Hi Jens, > > how Piwigo checks which plugins are compatible and which are not. > > Manual check. First by the plugin creator. If it takes too long, a team > member takes the time to test. Hopefully it works and no change is needed. > A simple edition of the last revision of the plugin to mark it as > compatible and we're done. If the extension needs a change, we have 2 > options: > > 1. the code is hosted on our old SVN : easy, we have the ability to > commit changes and publish a new version > 2. the code is hosted on Github, on their own account. We can't do > much :-/ Well, after thinking, we can still use the translation user to > make some changes, but it was designed for that. > > What would be nice, for the future, is a system on piwigo.org/ext to > declare as a tester, "I've tested with Piwigo 11 and it works". We could > make the check a community effort :-) > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/Piwigo/Piwigo/issues/1335#issuecomment-775338871>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABERJAQKJS7OCP3WRPNHIB3S6ASJ7ANCNFSM4XJNAJUA> > . > <!-- github-comment-id:776223887 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Piwigo#1158