WordPress.org

Ready to get started?Download WordPress

Make WordPress Core

Updates from Samuel Wood (Otto) Toggle Comment Threads | Keyboard Shortcuts

  • Samuel Wood (Otto) 9:12 pm on October 7, 2010 Permalink
    Tags: ,   

    WordPress.org now shows Gravatar Hovercards too. Should be active anywhere you see a Gravatar on the site.

     
    • Peter Westwood 9:13 pm on October 7, 2010 Permalink | Log in to Reply

      Thank you for the speedy service ;-)

    • Brad Williams 10:16 pm on October 7, 2010 Permalink | Log in to Reply

      Is the link to the plugin author profile on the plugin detail page gone for good? I liked that users could click through and see all of the plugins I’ve released.

      • Matt 12:29 am on October 8, 2010 Permalink | Log in to Reply

        There’s an API where the page can add additional stuff to the hovercard, so we could actually put # plugins and # of themes linked directly to those pages in the hovercard… next version. :)

      • Beau Lebens 6:13 pm on October 8, 2010 Permalink | Log in to Reply

        The current implementation of the hovercards overrides the A tag (if there is one) wrapping the Gravatar. If that tag were split out so that there was one wrapping the image and one wrapping the text/name, then the name could be linked directly to the profile page.

        We currently have a pretty basic callback system in place so that you can do things to cards as they are generated (one card, per profile on a a page). You can hook into that by creating a callback method (called profile_cb) on the Gravatar object, before calling attach_profiles(). That might look something like this:

        <script type='text/javascript' src='http://s.gravatar.com/js/gprofiles.js?ver=1'></script>
        <script type='text/javascript'>
        jQuery(document).ready(function($){
        	Gravatar.profile_cb = function( hash, dom_id ) {
        		// do stuff here
        	};
        	Gravatar.attach_profiles();
        });
        </script>
        

        hash = the md5 hash of the email of the user
        dom_id = the DOM id=”” of that hovercard (you can use this to isolate a jQuery selector within that card)

        From there, you can use some DOM magic to inject things into the card wherever you want, just take a look in Firebug or something similar to see the structure of the HTML that’s created and you should be able to figure it out ;)

        You might need to bump the ver=1 part once in a while, because we’re still tweaking things a little bit, so you won’t get the latest version unless that increments (CDN will be caching the old version).

        • Mark Jaquith 9:14 pm on October 8, 2010 Permalink | Log in to Reply

          Otto, can you use that callback to keep the link pointing to the WordPress.org profile?

          Also, when someone doesn’t have a hovercard (which many people don’t, because they’re using a secondary Gravatar addresss), it removes the link. Go to one of my plugins, hover my name, and watch the text go from blue to grey and unclickable.

        • Otto 1:38 pm on October 9, 2010 Permalink | Log in to Reply

          Fixed the name link. The image now links to the gravatar profile, the name points to the profiles page.

    • Erlend 10:10 pm on October 8, 2010 Permalink | Log in to Reply

      Hovercard appears with the info alright, but the edges are rugged and just don’t look good. I’m guessing it’s just a browser thing (I’m on Ubuntu 10.10 Chrome 6.0.472.63). There should really be some kind of fallback, or just hold back the unnecessary advanced feature that is the tilt. Just the zoom would be awesome enough ;)

    • Mrmist 9:14 am on October 9, 2010 Permalink | Log in to Reply

      Some of the hovercards don’t seem to be working – mine for example, and Esmi’s – the little loading spiral just goes round and round infinitely. Is there some requirement that makes the card work?

  • Samuel Wood (Otto) 2:36 pm on October 1, 2010 Permalink
    Tags:   

    WordPress.org single sign on has been fixed for most of the various sections. Themes still needs an upgrade, and the codex plugin needs to be modified for the new cookie structure, but most of the main bits are working now.

    For you moderators, this change will very likely have invalidated your admin area cookies. So if you find you can’t access an admin screen that you should be able to access, log out then log back in before trying anything else. This should only be required once, to get the cookies to reset themselves to the correct names.

     
    • Ron 4:56 pm on October 1, 2010 Permalink | Log in to Reply

      Does that include BuddyPress trac as well?

      • Andrew Nacin 5:09 pm on October 1, 2010 Permalink | Log in to Reply

        Doubtful, as that’s another domain. I think Otto was referring to Themes/Codex/Plugins/Support/Ideas, which spans two or three versions of bbPress, MediaWiki, WordPress, and the like. Doesn’t look like the BuddyPress profiles component is sync’d up in that though.

        • Otto 5:11 pm on October 1, 2010 Permalink | Log in to Reply

          Profiles, themes, and codex are not yet on the SSO. Working on codex, themes needs a bbPress upgrade first, profiles will be done eventually.

        • Ron 7:48 pm on October 1, 2010 Permalink | Log in to Reply

          I forgot that would require cross domain login.

    • Peter 4:57 pm on October 1, 2010 Permalink | Log in to Reply

      That’s Awesome! I think…. well… actually, what does that mean exactly. Where can i read more about what the SSO plan is?

  • Samuel Wood (Otto) 8:37 pm on September 7, 2010 Permalink
    Tags: , , ,   

    The WordPress.org support forums now have subscribe by email, to tags.

    To use, login, then view any single tag page. At the bottom of the page, sorta hidden on the left side, you’ll see a link called “Subscribe to Tag via Email”. It’s a toggle.

    Note: If you subscribe to heavily trafficked tags, you’re likely to get a LOT of emails. I suggest you use this sparingly, or get an email system that can cope.

    Note the second: I fully expect there to be bugs. This is new. Expect fixes when I find them.

     
    • Alex M. 8:41 pm on September 7, 2010 Permalink | Log in to Reply

      Sweet! I’m personally going to stick to tag feeds, but I’m sure this will be handy for others! Well done!

      • Otto 8:43 pm on September 7, 2010 Permalink | Log in to Reply

        Yeah, me too. But subscribe by email is one of those things that is continually asked for. The main reason for this is to give plugin authors a way to more easily see topics posted about their plugins.

    • Mike Schinkel 9:03 pm on September 7, 2010 Permalink | Log in to Reply

      NICE! I will definitely use this. It will be especially handy for plugin authors too.

    • Milan 10:00 pm on September 7, 2010 Permalink | Log in to Reply

      It’s great that you listened to my suggestions. Will you release code somewhere so that it can be used on other bbPress forums too?

      • Otto 10:03 pm on September 7, 2010 Permalink | Log in to Reply

        I need to clean up the plugin first and work out any bugs, but yes, eventually.

    • Simon Wheatley 8:52 am on September 8, 2010 Permalink | Log in to Reply

      Nice work, this is going to be super handy!

      Currently it’s not possible to subscribe to a tag which has no posts. Any chance of allowing preemptive tags?

      • Jive 8:39 pm on September 15, 2010 Permalink | Log in to Reply

        Seconded. Email subscriptions for tags without posts would be very useful so that devs can be notified when the first forum post is made.

        • Otto 9:17 pm on September 16, 2010 Permalink | Log in to Reply

          No plans to add this, but there is a quick workaround: Add the tag to one of your own posts, subscribe to it, then remove the tag.

        • Milan 5:29 pm on September 29, 2010 Permalink | Log in to Reply

          If you followed my advice and used built-in functions, this wouldn’t be a problem.

          Why you actually created completely new functions?

    • kyle 12:26 pm on September 8, 2010 Permalink | Log in to Reply

      I’m so happy you turned this on. I’m a much higher contributor to topics now.

      Thanks,
      ~Kyle~

    • Mike Schinkel 3:48 pm on September 8, 2010 Permalink | Log in to Reply

      Some suggestions after a day of usage:

      1.) HTML UNencode the content.
      2.) Include the message which is being replied to like this site does.

      #2 is a nice to have, #1 is a must have…

      Thanks.

      -Mike

    • Mike Schinkel 7:50 pm on September 8, 2010 Permalink | Log in to Reply

      Another tiny suggestion. The wording is a little unclear, especially for unsubscribe:

      – Subscribe to Tag via Email
      – Unsubscribe to Tag via Email

      Maybe?

      – Subscribe to Emails for this Tag
      – Unsubscribe from Emails for this Tag

      Clearly people will figure it out as it but it caught me off guard for a second when I decided to unsubscribe a high-volume tag.

    • Michael Fields 8:17 am on September 9, 2010 Permalink | Log in to Reply

      Loving this functionality! I think that this feature is really going to help out with the quality of support at wordpress.org. One suggestion that I have is to add the ability to subscribe to a thread without replying to it.

      • Otto 8:27 am on September 9, 2010 Permalink | Log in to Reply

        You already can subscribe without replying. Look on the right hand side, under “About this Topic”. There’s a subscribe/unsubscribe link there. Click it.

    • Mike Schinkel 9:07 pm on September 10, 2010 Permalink | Log in to Reply

      If you are looking for enhancements that would be highly appreciated two that would be are:

      1.) Preview-As-You-Type – I’ve been using a preview-as-you-type system on http://wordpress.stackexchange.com/ and find it greatly reduces the effort required to produce a nicely formatted reply and it really cuts down on the save-edit-resave cycles.

      2.) A wiki-like syntax – Generally I hate wiki syntaxes and would prefer to see sites going with pure HTML as the WordPress Support site pretty much does but after a month of working with http://wordpress.stackexchange.com/ I have to say their wiki language gets it right; it’s much less effort to format answers on their site than on any other site/forum that I’ve used before.

      Something to consider anyway?

  • Samuel Wood (Otto) 9:29 pm on August 30, 2010 Permalink
    Tags: , ,   

    Email subscriptions are now enabled for individual topics on the support forums.

     
  • Samuel Wood (Otto) 9:32 pm on August 27, 2010 Permalink
    Tags: compatibility, ,   

    New for Extend/Plugins:

    If a user clicks the “Broken” link, it will record the click as usual, but now also redirect them to the start a new topic support form, and nicely ask them to leave a new topic explaining what’s broken. Hopefully, this will make the broken button more useful.

    Note: if you want to test this, feel free, but realize that you’re marking the plugin as broken by doing so, whether you leave a new topic or not. So please, go back afterwards and change your vote to “works” if it really does work.

     
    • Ipstenu 10:14 pm on August 27, 2010 Permalink | Log in to Reply

      Sweet!

    • Ofer Wald 11:40 pm on August 27, 2010 Permalink | Log in to Reply

      How about doing the same for the dreaded single star vote?

    • Denis 11:56 pm on August 27, 2010 Permalink | Log in to Reply

      Is there an RSS feed that plugin authors can use to grab all of these forum threads? If not, it would be even more useful… Especially if advertised.

      • Otto 12:33 am on August 28, 2010 Permalink | Log in to Reply

        Every forum thread made via this manner gets tagged with the plugin’s slug. So you can subscribe to a plugin’s topic list that way.

        Example: http://wordpress.org/tags/simple-facebook-connect has an RSS feed on it of http://wordpress.org/support/rss/tags/simple-facebook-connect .

        Email notification hopefully coming soon.

        • hakre 7:33 am on August 28, 2010 Permalink | Log in to Reply

          Feedburner offers Email Integration for RSS.

        • Denis 9:45 am on August 28, 2010 Permalink | Log in to Reply

          That’s not good enough. It’s fine when you’ve a plugin or two. But when you’ve dozens, it becomes a lot of feeds to track.

          Moreover, these tags point to multitudes of support requests that are related to WP bugs and incompatibilities introduced by third party plugins — stuff that I don’t even want to be reading.

          What’s needed are two unified feeds. The first should lead plugin devs to all open threads related to his plugins, regardless of tags. The second should lead plugin devs to the subset of these threads that were opened by the broken button.

          Using tags for any of these two feeds is not an option unless the community spirit and attitude have improved dramatically. When I was answering support requests in the WP forums, the tag I was using got dropped in a hostile effort to move it out of the hot tags page.

        • Otto 6:22 pm on August 28, 2010 Permalink | Log in to Reply

          Better ways of notification are coming as well. Email notification is next on my list, followed by handling tags better.

          One step at a time, man.

        • Denis 6:42 pm on August 28, 2010 Permalink | Log in to Reply

          Personally, I don’t read emails any more than Knuth:

          http://www-cs-faculty.stanford.edu/~knuth/email.html

          I do subscribe to RSS feeds, however. So if anything, that works better. :-|

        • Otto 10:12 pm on August 28, 2010 Permalink | Log in to Reply

          It’s a combo deal. Emails come first, because though I use RSS and agree with you, the majority want the emails. Emailing an existing feed is simpler than emailing a non-existent one.

        • Matt 4:21 am on August 29, 2010 Permalink | Log in to Reply

          Denis, I’m sorry it’s not good enough. it’s better than before. And it’s being worked on.

    • Chip Bennett 3:19 am on August 28, 2010 Permalink | Log in to Reply

      Next step: change the vote not to record until a new forum topic is posted. :)

      (Either way, very cool stuff, Otto!)

      • Rich Pedley 7:20 am on August 28, 2010 Permalink | Log in to Reply

        oh yes that would be nice. Then add automatic changing of vote to works once thread is marked resolved… Oh sorry I think I just saw a cuckoo in the clouds.

    • hakre 7:34 am on August 28, 2010 Permalink | Log in to Reply

      Yeah, nice! I’ll play a bit with it and let you know :)

    • Denis 9:52 am on August 28, 2010 Permalink | Log in to Reply

      Adding to my last comment… Isn’t there a risk that end users report plugins as broken when they run into a WP bug or some incompatibilities introduced by their theme or other plugins?

      • Pross 1:19 pm on August 28, 2010 Permalink | Log in to Reply

        Maybe the author should verify its broken?

      • Devin Reams 2:06 pm on August 28, 2010 Permalink | Log in to Reply

        Are you really suggesting that doesn’t already happen?

      • Otto 6:20 pm on August 28, 2010 Permalink | Log in to Reply

        They were doing that already. Now they have a chance to report the problem.

        Ignoring their vote because they refuse to explain it would be rather unfair. The number of people who think it doesn’t work is valid data, regardless of why they think that. This isn’t ebay, where one negative means nobody trusts it.

        • Denis 6:35 pm on August 28, 2010 Permalink | Log in to Reply

          I believe you’re misunderstanding the question. On occasion, users report things as broken when it really isn’t. For instance:

          http://wordpress.org/extend/plugins/sem-admin-menu/

          One reports CSS is loaded, always. Which is an enhancement at best…

          The next is an incompatibility with another plugin…

        • Otto 3:33 am on August 29, 2010 Permalink | Log in to Reply

          No, I understand just fine. However, if they’re reporting it broken, then that’s between you and them. What, we’re supposed to make somebody jump through hoops or make it harder or something?

    • scribu 5:05 pm on August 28, 2010 Permalink | Log in to Reply

      some info from the readme is missing: http://core.trac.wordpress.org/ticket/14719

      • Otto 5:42 pm on August 28, 2010 Permalink | Log in to Reply

        Not a bug, Matt told me to remove them.

        • Ipstenu 2:54 am on August 29, 2010 Permalink | Log in to Reply

          Otto, would that be why some authors don’t show up on their plugins? I don’t seem to be listed as an author on any of my plugins, and that …. Well, makes it hard for people to know how to get in touch with me for support :)

        • Otto 7:52 pm on September 2, 2010 Permalink | Log in to Reply

          Ipstenu: No, this was because your plugin didn’t have your correct wp.org username in the Contributors: line in the readme.txt. Caps count there too.

          I’ve just modified this to show those author listings correctly. Although, if it can’t find you as a valid user, you get no gravatar and no link (because there’s nothing in profiles to link to). This will at least prevent the link weirdness we once had on the authors listing.

        • Stephen Cronin 12:48 am on September 6, 2010 Permalink | Log in to Reply

          As a plugin author, the more links to my site the better! :)

          But that’s not important. What’s important is this:

          As a user, I’ve found that *most* plugins have extra information, comments, etc on the plugin home page on the authors site. The removed link to the plugin home page is something I clicked a lot.

          I take Matt’s argument that this link can be added to the content area, but a) the vast majority of plugins aren’t going to have this and b) those that does will have it in a slightly different location.

          End result, instead of having a *consistent place* on *all* plugin pages where I can easily find this link, I have to search for it and in many cases it won’t even be there. There’s a term for that sort of thing:

          Usability fail

          The link to the author’s site is less important, but the link to the plugin’s homepage (on the author’s site) should remain (in my opinion) – because that makes the site more usable for the users.

      • scribu 5:51 pm on August 28, 2010 Permalink | Log in to Reply

        An explanation would be nice. Spamming can’t be a valid reason, since you can insert links directly into the description.

        • Otto 5:57 pm on August 28, 2010 Permalink | Log in to Reply

          Dunno. You’ll have to ask him. Anyway, I don’t think the design there is final yet, so they may make a comeback. We’ve basically just been playing with it, to see what looks and works better. Eventually I hope to have some useful stats for authors as well, for example.

          Bringing any of this up on trac is probably premature. Email me directly if you have concerns, I read them all and respond to most. otto at ottodestruct.com

        • Denis 6:44 pm on August 28, 2010 Permalink | Log in to Reply

          I fail to see any incentive to write a free plugin if you don’t even get some web traffic as a result.

        • Alex M. 8:42 pm on August 28, 2010 Permalink | Log in to Reply

          If that’s the only reason you’re writing plugins, then I feel sorry for you Denis. :)

        • Otto 10:18 pm on August 28, 2010 Permalink | Log in to Reply

          I gotta say that I think those links drive very little traffic. Matt said at #wcsav that I remember (because we used my plugin to do it), that something like 20% of his ma.tt traffic now comes from his facebook links (which are auto-published by SFC). There’s better ways to drive traffic back to you. Developing is generally done to fill a need, not to drive traffic.

        • scribu 11:57 pm on August 28, 2010 Permalink | Log in to Reply

          As a counter-example, about 20% of my referrall trafic (10% overall) come from wp.org

        • Otto 3:34 am on August 29, 2010 Permalink | Log in to Reply

          If it’s that big a deal, put your links in the description of the plugin. You can put links there, you know.

        • Matt 4:25 am on August 29, 2010 Permalink | Log in to Reply

          Plugin links are a little redundant now that each plugin has a page on the directory. If someone has a page on their own site as well easy (and more effective) to link from the main content area.

          Author links only work for single-author plugins, for multiple author plugins (which we want to encourage) it’s broken so better to build it off the commit list, so each author gets credit.

        • Alphawolf 3:00 pm on August 29, 2010 Permalink | Log in to Reply

          Well, if it remains like this, we have a useless profile field “Website URL ” then:

          (which funnily enough sais “Give yourself some link love.” :-) )

          It’s useless if the website URI neither shows up on the profile pages nor on the plugin pages anymore.

          On a side note, the wp.org repository would be the only plugin repository I know that doesn’t link back to the dev’s website at least. Personally I found some really nice blogs worth subscribing through the plugin pages (such as Viper’s, Ozh’ etc.).

        • Matt 3:11 pm on August 29, 2010 Permalink | Log in to Reply

          Our goal is to drive even more back to plugin authors than we do now, but give some time for the iterations to finish up.

        • scribu 5:24 pm on August 29, 2010 Permalink | Log in to Reply

          Thanks for the explanation Matt. Makes sense now.

          Michael H. asks to move the author info back to the top:

          http://core.trac.wordpress.org/ticket/14725

        • Matt 10:14 pm on August 29, 2010 Permalink | Log in to Reply

          That’s nice, but not really useful at this stage. If you have something you really want on that page maybe just send me an email.

      • scribu 5:27 pm on August 29, 2010 Permalink | Log in to Reply

        Speaking of developer site links, I think we can all agree that it makes sense to show them on profiles.wordpress.org (they were there, but vanished at some point)

        • Matt 10:14 pm on August 29, 2010 Permalink | Log in to Reply

          Definitely — not sure what’s up with those pages. The URLs are wrong too.

      • filosofo 8:33 pm on August 29, 2010 Permalink | Log in to Reply

        With profiles.wordpress.org being pushed into greater prominence, can we either fix or remove the activity stream? For example, it shows my last core trac activity as having occurred in March.

        I will volunteer to make the fix.

    • John James Jacoby 6:07 pm on August 29, 2010 Permalink | Log in to Reply

      Nice work Otto! Like the changes so far and know it will only improve as you iterate.

      • Otto 9:12 pm on August 29, 2010 Permalink | Log in to Reply

        Thanks! I think a lot of people aren’t getting the “iteration” concept here. :)

        • Alphawolf 1:27 pm on August 30, 2010 Permalink | Log in to Reply

          I’m sure you are aware already, but just for the sake of completeness, the short description above the tabbed navigation doesn’t convert Markdown currently. But that’s just a minor minor issue that came to my eyes. :)

        • Otto 3:28 pm on August 30, 2010 Permalink | Log in to Reply

          The short description should be text only. Markdown is not allowed there.

        • Alphawolf 3:40 pm on August 30, 2010 Permalink | Log in to Reply

          Sorry, my fault then. ;-)

  • Samuel Wood (Otto) 7:02 pm on August 25, 2010 Permalink
    Tags:   

    Gravatars are now shown on the plugin listing page. It’s a minor thing, but people like pictures and clicking on pictures. Clicking on somebody’s picture will take you to their plugin profile, showing all their plugins.

     
    • Michael Torbert 7:04 pm on August 25, 2010 Permalink | Log in to Reply

      Awesome!

    • Glenn 7:09 pm on August 25, 2010 Permalink | Log in to Reply

      Nice touch!

    • Andrea_R 7:20 pm on August 25, 2010 Permalink | Log in to Reply

      Very very way cool.

      On multiple-author plugins, are the gravatars supposed to be stuck together, or do you think they’d look better with a wee bit o’ padding?

      • Otto 7:25 pm on August 25, 2010 Permalink | Log in to Reply

        I stuck ‘em together intentionally cause I liked the way it looked, but I’m open to suggestion on layout there if somebody has a better one.

    • Ipstenu 7:25 pm on August 25, 2010 Permalink | Log in to Reply

      padding 1px ;)

    • Rich Pedley 7:46 pm on August 25, 2010 Permalink | Log in to Reply

      Wouldn’t it make sense to add the gravatar to this page as well: http://wordpress.org/extend/plugins/profile/ ?

    • Rich Pedley 8:11 pm on August 25, 2010 Permalink | Log in to Reply

      and on my final note, will it be added for themes as well…

      apologies for my poor speeling today, one of those days again.

    • kyleabaker 8:20 pm on August 25, 2010 Permalink | Log in to Reply

      I think you should add something like this to the avatars:
      border: 1px solid #999;
      padding: 1px;

      It looks great like this with 4 avatars per line, but the text-indent is forcing 3 per line on every row after the first. If you could get these to all line up correctly then it would look great!

    • Alex M. 8:50 pm on August 25, 2010 Permalink | Log in to Reply

      Is the second line of Gravatars supposed to be indented?

      http://wordpress.org/extend/plugins/akismet/

    • Utkarsh Kukreti 11:35 pm on August 25, 2010 Permalink | Log in to Reply

      I’d suggest adding authors name as the title attribute of the link, so the name shows up on mouse hover.

    • Ron 12:45 am on August 26, 2010 Permalink | Log in to Reply

      Saw this earlier today. Love it.

    • hakre 8:57 am on August 26, 2010 Permalink | Log in to Reply

      the sidebar get’s crowded. Maybe placing into main content under authors?

      • Otto 2:45 pm on August 26, 2010 Permalink | Log in to Reply

        Some other changes are coming to the sidebar soon, actually, so it won’t be as bad.

    • Matt 3:23 pm on August 26, 2010 Permalink | Log in to Reply

      I expected the gravs to be smaller, and inline with the “Authors:” list.

      • Otto 3:26 pm on August 26, 2010 Permalink | Log in to Reply

        What, just like a tiny picture on the left of each name in the list? Seems like that’d look strange to me. Easily changed though.

        • Matt 3:27 pm on August 26, 2010 Permalink | Log in to Reply

          Let’s try it out, and axe the sidebar one. Like how avatars show up on Trac.

        • Otto 3:37 pm on August 26, 2010 Permalink | Log in to Reply

          Trac uses 24 px icons. If I make them that big, it looks pretty strange. But if I make them smaller at 16, then they’re almost too small to see.

    • Otto 5:42 pm on August 26, 2010 Permalink | Log in to Reply

      After some review and such, this whole thing is getting changed much more extensively. Expect gradual updates over the next day or two.

      • Alex M. 11:10 pm on August 26, 2010 Permalink | Log in to Reply

        A link to the plugin’s homepage is missing. :)

        • James 7:22 am on September 16, 2010 Permalink | Log in to Reply

          Are there any plans to bring back to “Plugin URL” and “Author URL” links that used to be near the top right of the page?
          Thanks

        • Otto 9:18 pm on September 16, 2010 Permalink | Log in to Reply

          James: No. If you want to link back to your homepage, add the link into your description area. The markdown for links looks like this: [http://example.com](link text).

    • w3prodigy 6:08 pm on August 26, 2010 Permalink | Log in to Reply

      Not sure if this is a bug, or you guys doing your thing – (going based off of my plugins) if a plugin does not have a readme file then no author name shows up

      • Rich Pedley 7:27 am on August 27, 2010 Permalink | Log in to Reply

        If the plugin doesn’t have a readme, why is it there? I thought it was a requirement for the plugins to have a readme?

        • Jay Fortner 12:55 pm on August 27, 2010 Permalink | Log in to Reply

          “To make your entry in the plugin browser most useful, each plugin should have a readme file” – I always took “most useful” as a recommendation to create a readme file, not a requirement.

          Since the plugins would still function without a readme, I generally don’t create the readme file until my plugin reaches a stable version – this is a better development cycle for me… clearly though, if the plugin directory is changing and now explicitly requiring a readme to display properly, I’ll add it. I was simply noting the differences between the previous way the plugin directory functioned and how it functioned after the recent changes.

        • Otto 1:30 pm on August 27, 2010 Permalink | Log in to Reply

          Several things probably have to be clarified but:
          a) Readme’s are not really optional. All plugins must have a readme.txt.
          b) The Contributors line in the readme should contain a list of the authors, using wp.org usernames only.

          This is how it’s going to be. If you give it bad input, you’ll get bad output.

        • Jay Fortner 1:50 pm on August 27, 2010 Permalink | Log in to Reply

          Thanks for the clarification Otto, looks like I have some readme’s to write.

        • Otto 2:46 pm on August 27, 2010 Permalink | Log in to Reply

          It’s been pointed out that I should clarify the above.

          A plugin will go into the repo just fine without a readme.txt file. However, without the readme, then several pieces of the plugin’s webpage won’t display. The authors (contributors) is one of these pieces. So is the description and everything else. That listing in the plugins page is built mainly off the readme.txt file.

          So while’s it optional in practice, it really should be there. The plugins/about page makes it a point to say that you should upload your plugin with a readme.txt file.

        • Otto 9:17 pm on August 29, 2010 Permalink | Log in to Reply

          @Jay:
          I’ve noticed that a lot of people aren’t putting valid author info in the readme file (they should be wp.org usernames, but many are not), so there’s a change I’m working on for that.

          Still, you should have a readme. It’s not needed for WP, but it is really needed for a good plugin page entry.

    • Otto 3:10 am on August 27, 2010 Permalink | Log in to Reply

      Like I said, after my conversation with matt and the upgrades, lots of things are changing. Gimme a day before suggestions, because what you see now is temporary. :)

  • Samuel Wood (Otto) 6:47 pm on August 16, 2010 Permalink  

    Registration on the support forums has been broken slightly since the bbPress update there. This is now fixed and it should give useful errors to users trying to register with bad info.

    Big example: People have been trying to register with an email address that was already registered. Now it will tell them that instead of simply giving them no feedback and having them wait for a registration info email that’s never going to come.

     
  • Samuel Wood (Otto) 6:09 pm on August 12, 2010 Permalink  

    Matt asked me to go through the Showcases on wp.org and check for sites not running WordPress. Of those, I found 36 sites (out of 543). Here’s the list:

    (More …)

     
    • sillyandrea 6:16 pm on August 12, 2010 Permalink | Log in to Reply

      This one:
      http://wordpress.org/showcase/wannanetwork/

      is listed under BuddyPress and WPMU, but shortly after reverted to a single WP blog.

    • Mike Schinkel 6:48 pm on August 12, 2010 Permalink | Log in to Reply

      I’ve wondered about that before when I’ve been looking for showcase sites for WordPress. Good job.

    • Rich Pedley 7:20 pm on August 12, 2010 Permalink | Log in to Reply

      wow that must have taken a while, well done.

    • Mr Mist 8:16 pm on August 12, 2010 Permalink | Log in to Reply

      How were they determined in the first place? The submission form looks like it would be a manual process of addition.

      • Otto 9:33 pm on August 12, 2010 Permalink | Log in to Reply

        Dunno, but yes I think they were submitted manually by somebody at some point in time. I suspect most of these sites once used WP and then either died or changed to something else.

        A few of them are using Expression engine, a significant number were using ASPs and such. About a third are simply dead/gone.

      • Matt 10:58 am on August 13, 2010 Permalink | Log in to Reply

        Would be nice to know where people are going.

    • Peter Westwood 9:34 am on August 13, 2010 Permalink | Log in to Reply

      Would be great if we could maybe run an automated check once in a while using something like http://ismyblogworking.com/ to flag up ones which need reviewing as they look like they are no longer WordPress sites.

    • Douglas 3:25 pm on August 13, 2010 Permalink | Log in to Reply

      Thanks Otto. This was very helpful. I went through and took all of the listed blogs out of the Showcase.

      Some quick observations: I did notice that quite a few of the blogs on the list were dead or the company looks to have been acquired or something like that, so that’s a good sign (for WordPress, at least). What’s also interesting is that we lost a few blogs tagged with “Innovative” (a pretty selective tag, with only about 28 sites tagged Innovative), which to me says that some people are trying WordPress for advanced things and then perhaps giving up and moving to something else later if it does not work out the way they want.

    • Sara Rosso 9:45 pm on June 6, 2011 Permalink | Log in to Reply

      Reviving this old Showcase thread –

      I thought a good idea might be to create a “Flag this site” function for each showcase page so people could let us know when sites have errors or are redirecting.

      Also, one thing the showcase can’t take into consideration is some sites are microsites and temporary which means those sites are short-lived, i.e., the Lexus Darker site:
      http://wordpress.org/showcase/lexus-darker-side-of-green/
      which now redirects to the main Lexus site.

      Also this site gives a 404:
      http://wordpress.org/showcase/x3-studios/

      I think a 404 or directory denied from mshots should be something that can set off some kind of alert?

      • Andrew Nacin 8:43 pm on June 8, 2011 Permalink | Log in to Reply

        When a site gets submitted, we now check what version of WordPress they’re running. We should probably set up a periodic crawl for 404s or redirects, and validate that those redirects are still WordPress sites. We can couple this with checks as to whether they’re running the latest version of WP, which would be an interesting stat.

      • Sara Rosso 9:39 am on June 9, 2011 Permalink | Log in to Reply

        Also, for sites that then we remove from the Showcase, it might be a good idea to redirect the URL to the main Showcase page instead of showing 404s.

  • Samuel Wood (Otto) 6:20 pm on August 3, 2010 Permalink
    Tags: boolean, filter, ,   

    Theme filter searching now has an all/any selection box, for people who didn’t like it being exclusively boolean AND. See it here: http://wordpress.org/extend/themes/tag-filter/

     
  • Samuel Wood (Otto) 1:25 pm on July 22, 2010 Permalink
    Tags: , , resolved,   

    Plugin authors can now change the “Resolved” status on support topics made about their plugins on .org.

    Note: This only works when the topic is made from the plugins area, using the “Got something to say? Need help? Write a new topic.” link at the bottom of the plugins screen. Topics that are simply manually tagged with the name of the plugin won’t work.

    Mods and higher can still change the resolved status on any topic, as always. So you may not be able to see this change easily. :)

     
    • Ipstenu 1:33 pm on July 22, 2010 Permalink | Log in to Reply

      WOOT! This is awesome! Yay for upgrades!

    • scribu 1:47 pm on July 22, 2010 Permalink | Log in to Reply

      Diving in now :D

    • Rich Pedley 2:24 pm on July 22, 2010 Permalink | Log in to Reply

      I get the same on this thread:
      http://wordpress.org/support/topic/413925
      trying to change the status from ‘not a support question’ to ‘resolved’ it remains as ‘not a support question’
      (Using that thread as a test.)

      • Otto 2:32 pm on July 22, 2010 Permalink | Log in to Reply

        Hrmmm.. Okay, I’m looking into it. Seems there’s something I missed.

        • Otto 2:44 pm on July 22, 2010 Permalink | Log in to Reply

          Yep, there was. It’s a bit hard to test this sort of thing when I already had the ability to change that status. Testing as myself bypasses the specific piece of code I was trying to test.

          Still, should be working now. I think. :)

        • Rich Pedley 2:49 pm on July 22, 2010 Permalink | Log in to Reply

          Looks like it is – excellent work, thanks Otto.

          Now all we need is a way to seeall threads for all our plugins on one page ;)

        • scribu 2:54 pm on July 22, 2010 Permalink | Log in to Reply

          @Otto: yep, works now.

          @Rich Pedley: I don’t think that’s a good idea. Popular plugins have 1000s of threads.

        • scribu 2:55 pm on July 22, 2010 Permalink | Log in to Reply

          Oh, you mean combined. Yeah, that would be nice.

        • Rich Pedley 3:03 pm on July 22, 2010 Permalink | Log in to Reply

          yes combined, and paginated of course. I’ve only got a few and I’d find it useful, I dare say others would as well.

    • JLeuze 3:22 pm on July 22, 2010 Permalink | Log in to Reply

      Awesome, I resolved all of the support topics for my plugin and it worked perfectly!

      Thanks, this will be a really helpful addition. While you’re tweaking the forums, is there an easy way to exclude the sticky posts from the No Replies view?

    • Pat 1:33 am on July 23, 2010 Permalink | Log in to Reply

      Is there another way to tell when a topic is made from the plugins area?

      There are a suspiciously large number of my plugin’s support topics that I cannot change the “Resolved” status for, and their titles take the same form as topics where this feature is actually offered to me. :) Just want to make sure this is working as intended. Thanks Otto!

      • Otto 2:44 pm on July 25, 2010 Permalink | Log in to Reply

        Well, yes. If you can change the resolved status, it was made from the plugin area. :D

        Seriously, when you use that link to make a new topic, some metadata gets added to the topic on the back end which marks what plugin the topic is about. I use that meta info to do a lookup on the plugin and determine who can adjust the resolved status.

        But, if somebody makes a topic and just makes it look similar, with tags and the title and such, then it will still show up in the list of topics about that plugin (as that uses tags), but not have the hidden meta info.

        I intentionally did not use the tags, because anybody can adjust them.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel