Yesterday I released the first upgrade of piwigo-jplayer, but it can't be upgraded in the admin site. As this is my very first time, I probably missed an obvious step and I hope that a good soul will be able to help me here.
Correct me if I am wrong but what I figured out is that the ugrade of a plugin if driven by the comment header of main.Inc.php.
I've made 2 changes in that section of this file:
* Convert the line termination (call me crazy but I don't like to have CRLF files on mi Linux :) )
* Change version from 0.1 to 0.2
The full commit history is available on github.
I suspect that it could also be related to the name of the plugin (jplayer) being different from the name of the directory containing the plugin (piwigo-jplayer).
Did I do something wrong or did I missed something?
Offline
d-matt wrote:
Yesterday I released the first upgrade of piwigo-jplayer, but it can't be upgraded in the admin site.
What is exactly happening?
(It seems that you made it right.)
Offline
Actually, nothing happens... In the admin site, on the plugin list tab I see the old version of jplayer (0.2), there is nothing on the update tab but I can see the new version (0.3) on the last tab (and I can install it as if it was a different plugin)
As a complement, there is the folowing entry in my piwigo-plugins table :
id | state | version piwigo-jplayer | active | 0.2
This has been tested on piwigo 2.3.5 and 2.4.1
Offline
In the header comment of main.inc.php, what is your Plugin URI?
Offline
plg wrote:
In the header comment of main.inc.php, what is your Plugin URI?
The github projet :
Plugin URI: https://github.com/d-matt/piwigo-jplayer
Offline
This is not the good URI, use http://piwigo.org/ext/extension_view.php?eid=594 instead. 594 is the ID of your plugin on piwigo.org, Piwigo uses it to know if there is any new version available.
If you want to add another URL, use "Author URI" instead.
Offline
My bad... Anyway, thanks I've pushed v0.4 and next upgrades will be smooth !
Offline