WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Bug? Plugin repository not updating plugin page from readme.txt (16 posts)

  1. H.O.W.D.Y. Media
    Member
    Posted 2 years ago #

    Okay, it's been about 24 hours and I've tried several things and times to update the plugin page from the link below. The problem is that the readme.txt can be updated, but the website doesn't reflect the changes. I want users to be able to see the thumbnails, read the FAQs, and get the most up-to-date compatibility information. Short of releasing a new version, I can't think of what to do.

    I've seen others complain about similar issues. What gives?

    http://wordpress.org/extend/plugins/cdyne-call-me/

  2. esmi
    Forum Moderator
    Posted 2 years ago #

    Contact plugins[at]wordpress.org.

  3. You did it wrong.

    http://plugins.svn.wordpress.org/cdyne-call-me/tags/1.0/

    That should have ALL your files: Screenshots AND the .php and .txt.

    Ditto http://plugins.svn.wordpress.org/cdyne-call-me/trunk/

  4. H.O.W.D.Y. Media
    Member
    Posted 2 years ago #

    Thanks, that took care of it immediately.

    Unfortunately, the guide provided isn't exactly clear. It would be great if there was a 'when you are done, it should look like this' section with a block like the following:

    + branches (empty)
    + tags
      + 1.0
         plugin.php
         readme.txt
         screenshot-1.png (optional)
         screenshot-2.png (optional)
    + trunk
      plugin.php
      readme.txt
      screenshot-1.png (optional)
      screenshot-2.png (optional)

    Is there a way to prevent adding the screenshots to the plugin when downloaded? They are wasted space for the end user.

  5. esmi
    Forum Moderator
    Posted 2 years ago #

    Why not host them on your own site instead? That's what eShop does.

  6. H.O.W.D.Y. Media
    Member
    Posted 2 years ago #

    I'll have to look in to that as the readme documentation doesn't mention what syntax is used for adding images.

    What about the assets folder? Why can't the screenshots be kept there if they will be static? I understand that the screenshots may change with each version, but only one set of screenshots will be shown on the WordPress plugin page at any time.

  7. H.O.W.D.Y. Media
    Member
    Posted 2 years ago #

    Ah, eShop simply directs the user to a website to see the screenshots. I prefer having them visible right on the plugin page, so I suppose they will have to endure the burden of a few kilobytes of wasted space.

    Oh well.

  8. esmi
    Forum Moderator
    Posted 2 years ago #

    eShop has about 20 or more pages/panes, so it's not really practical to bundle them all in the plugin. Plus we tend to prefer videos to screenshots. :-)

    Frankly, I don't think that users are going to complain about a few optimised png files.

  9. H.O.W.D.Y. Media
    Member
    Posted 2 years ago #

    Of course, it is transparent to them, most will never open the folder to see what is inside. I was thinking about factoring concerning WordPress. Most code can fit easily in to a small image, a single screenshot can be several times the size of the code itself, so logically it would be best to make it so these files are not packaged. It would probably cut the bandwidth total from plugin downloads in half at least.

    I realize WordPress isn't hurting for bandwidth, but I come from the days of programming with only 4K of memory, and a large chunk of that is reserved for video and OS (Commodore Vic-20, anyone?). I have learned to code while keeping things concise and just as powerful without unneeded bloat. I miss the days when your OS fit on a floppy or even just within a few megs, but those days are gone now. Still, I persist on making tight code and reducing resource usages.

  10. esmi
    Forum Moderator
    Posted 2 years ago #

    If it ever does become an issue, I suspect the whole plugin section will need to be over-hauled.

    I come from the days of programming with only 4K of memory

    I hear you! In the distant past, I had to use MUMPS which allowed a whole 2k for a module/program. I still tend to pare down my code too. :-)

  11. Unfortunately, the guide provided isn't exactly clear.

    FWIW, the guide isn't telling you how to use SVN. And that problem is common to people who've never used SVN or other, similar, code management tools.

    Is there a way to prevent adding the screenshots to the plugin when downloaded? They are wasted space for the end user.

    On the to-do list. There's poking around being done to move them to assets.

  12. H.O.W.D.Y. Media
    Member
    Posted 2 years ago #

    I've used SVN in the past, but forget the details of it. Plus I was using Zend Studio to manage it, but there was a certain issue with something that required doing something like setting a path for it to work properly. I switched to NetBeans, tried it there, but NetBeans (7.0) was being impossible and refused to update or work regarding SVN. I wound up using TortoiseSVN to make things easier.

    On the to-do list. There's poking around being done to move them to assets.

    Excellent!

  13. RavanH
    Member
    Posted 2 years ago #

    Hi, hope you don't mind me breaking into this thread since I am seeing the same thing with one of my plugins: http://wordpress.org/extend/plugins/highlight-search-terms/

    The texts on most of the tabs there use very old readme text and do not get updated for some reason. I even deleted all the old readme.txt files in older tag directories leaving only the current stable one and the one in trunk... Ran the content through the readme validator but got no errors.

    Still the plugin page on WP Extend keeps showing these texts that do not even exist anymore. Very strange.

  14. RavanH - We do mind (this topic is RESOLVED, that's a hint to make a new one ;) ). Make your own topic.

    Also read http://wpdevel.wordpress.com/2012/04/19/nginx-migration/

    Recent changes may be acting ... Odd.

  15. RavanH
    Member
    Posted 2 years ago #

    Ipstenu, my sincere apologies and thanks for pointing me in the right direction. The problem seems to have been taken care of by now :) (and excellent news about the move to Nginx)

Topic Closed

This topic has been closed to new replies.

About this Topic