New version of plugin is pushed only to new plugin directory view

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    No, you don’t have a valid plugin in the directory at all, because https://plugins.svn.www.ads-software.com/sagenda/trunk/ is empty.

    The fact that the new directory picks up a plugin is the real problem here, because you have to have a version of the plugin in /trunk. Preferably the latest version. With a readme.txt that has a Stable Tag line pointing to your plugin’s tagged version.

    Thread Starter sagenda

    (@sagenda)

    Hello Samuel,

    Thanks for the info, when I started the plugin in 2014 it was necessary only to fill the /tags for productive release.

    As we are using GIT we never filled the SVN /trunk. Something change since the new plugin view was released, what is strange is that I don’t have the same result in both views.

    Thanks for your help! It’s working now!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘New version of plugin is pushed only to new plugin directory view’ is closed to new replies.