WordPress.org

1. Michel - xiligroup dev
   Member
   Posted 1 year ago #

   CONGRATULATIONS FOR THIS POWERFUL TOOL.
   Just a detail... the images are not currently in trunk but in latest tags folder.
   [readme]xili-postinpost[/readme] (in tags/0.9.1)
   Michel
   http://dev.xiligroup.com

   http://wordpress.org/extend/plugins/wp-readme-parser/

2. dartiss
   Member
   Posted 1 year ago #

   Rather than look in the trunk, is there an issue with assuming it's in the tag folder instead?

   David.

3. Michel - xiligroup dev
   Member
   Posted 1 year ago #

   It depends how developers use the plugin repository

   method 1 : the stable version is inside the trunk so - Stable tag - in readme of trunk is set to 'trunk'

   method 2 : in the trunk, only a readme in trunk where -Stable tag- is set to the version by example 0.9.1 or 1.8.5 so the kit is inside the /tags/0.9.1/ and repository keep and compress it.

   As you can see in 'other versions' tabs of repository, the trunk in this way contains development version. I don't use it to avoid errors... (I prefer to work on localhost)

   I prefer method 2 in our plugins : http://wordpress.org/extend/plugins/search.php?q=xili&sort=

   When I decide to set an 'other version' as 'current version', I just copy the readme.txt of the tags (becoming stable) to the trunk folder... it is why in this page ( http://dev.xiligroup.com/?p=1831 ) I can use your plugin with only a line added in #135. But in trunk the readme can not the same as this in stable tags which is displayed by WP repository.

   // If displaying the latest version, link to download
                       if (substr($file_array[$i],0,11)=="Stable tag:") {
                           $version=substr($file_array[$i],12);
                           $download="http://downloads.wordpress.org/plugin/".$plugin_name.".".$version.".zip";
                           $screenshot_url="http://plugins.svn.wordpress.org/".$plugin_name."/tags/".$version."/"; //temporary fixes error

   Hope that help you.

4. dartiss
   Member
   Posted 1 year ago #

   Thanks for that - really helped. Looks like I'd never read the README.TXT document thoroughly first ;o)

   I'm going to release a new version of the plugin any minute now - hopefully that should resolve the issue.

   David.

Topic Closed

This topic has been closed to new replies.