Recent Updates RSS Toggle Comment Threads | Keyboard Shortcuts

  • Jane Wells 7:15 pm on June 13, 2012 Permalink | Reply  

    WordPress 3.4 is released! No dev chat today. Resuming next week.

     

    • Brad Dalton 7:30 pm on June 13, 2012 Permalink | Reply

      Awesome!

    • Kevin McCarthy 12:53 am on June 14, 2012 Permalink | Reply

      great news. just installed on my local and the performance boost is fantastic (even with only about 15,000 posts):

      3.3: Home page (cache):
      345 queries, 0.486 seconds, 11871368 peak mem
      345 queries, 0.505 seconds, 11871368 peak mem
      345 queries, 0.425 seconds, 11871368 peak mem
      345 queries, 0.545 seconds, 11871368 peak mem
      345 queries, 0.443 seconds, 11871368 peak mem

      Ave = 345 queries, .480 seconds

      3.4: Homepage (cache):
      240 queries, 0.437 seconds, 11905952 peak mem
      240 queries, 0.465 seconds, 11883280 peak mem
      240 queries, 0.452 seconds, 11877344 peak mem
      240 queries, 0.403 seconds, 11877344 peak mem
      240 queries, 0.480 seconds, 11877344 peak mem

      Ave = 240 queries, .447

      Outcome:
      30% reduction in queries to homepage, 6% decrease in mysql working time.

      FYI: I’m using mysql query cache and w3 total cache via xcache (both with low memory limits)

    • herzcthu 11:44 am on June 14, 2012 Permalink | Reply

      Excerpt field is missing in page edit screen. Is it a featured of 3.4 ?

  • Jane Wells 10:45 pm on June 10, 2012 Permalink | Reply
    Tags: , ,   

    Updated Credits 

    Each release cycle, we try to recognize those core contributors who’ve made the greatest impact, ramped up the quickest, and/or been the most reliable.

    In the Contributing Developers category, mainstays Sergey Biryukov, Dominik Schilling (Ocean90), and Cristi Burcă (Scribu) are joined by Aaron Campbell and Helen Hou-Sandi. Aaron has been contributing for several years, but his work this cycle on improvements to custom headers stood out. Helen, who was a Recent Rockstar in 3.3, stepped up with improvements to the theme screen, UI/CSS fixes, and general helpfulness as fixes of all sorts were made through the later stages of the cycle.

    The Recent Rockstars section is mainly aimed at recognizing newer contributors and/or contributors who’ve been around for awhile casually but have recently increased their involvement. In this category, Amy Hendrix worked (with Aaron Campbell) on the improvements to custom headers with great success. George Stephanis worked on css and improving the mobile experience. Stas Sușkov contributed to the thinking behind HTML captions, a feature that has been waiting patiently on Trac for years. Max Cutler and Marko Heijnen both worked on updating aspects of XML-RPC, and Kurt Payne contributed to dozens of tickets including the refactoring of admin-ajax.php.

    Thank you all for your increased efforts, and congratulations on having your picture in the credits!

     

  • Andrew Nacin 2:35 am on June 7, 2012 Permalink | Reply
    Tags: , field guide   

    WordPress 3.4 Field Guide for Developers 

    WordPress 3.4 Release Candidate 2 due to drop any moment, and we’re aim to do a final release of 3.4 early next week. Developers, this is your last pre-release opportunity to test your plugins and themes.

    For 3.3, I wrote up a field guide of things developers need to know. For 3.4, I get to crowd-source it:

    Custom Headers and Backgrounds. Chip Bennett posted a great summary of the API changes on the make/themes blog. Amy Hendrix posted about flexible custom headers. If you are a theme developer, I would strongly suggest you follow the make/themes P2.

    Live Previews (The Customizer). You’ll want to read Otto’s definitive post on the subject, How to leverage the Theme Customizer in your own themes.

    New WordPress XML-RPC API. If you’re interested in the new APIs for custom content types and taxonomies, check out the Codex page, put together by Max Cutler. Max also recapped the bug fixes, test coverage, and other changes on his blog.

    Internationalization/Localization Changes. There’s a document on the translators P2 that outlines the numerous changes here.

    That’s all we have for now! If there’s something we missed that deserves a writeup for developers, leave a comment and I’d be happy to make sure it gets written up here (under the field guide tag).

     

  • Jane Wells 3:57 am on June 5, 2012 Permalink | Reply
    Tags: , ,   

    What’s Your Name? 

    It’s that time in the release cycle, folks… credits! Here is a recycle of the post telling you to update your name for the credits screen. :)

    Did you have at least one props on a commit in 3.4? If so, you’re listed on the Credits screen in the WP dashboard.* In the listing, your name links to your wordpress.org profile. Some people are shown as their real names, while others show as their trac/.org usernames. Now, if you’re all about the alias and you go by your trac/irc handle everywhere and want to keep it that way, that’s fine. But, if you would like people (curious users, colleagues, potential clients or employers, etc) to see your real name, all you have to do is add it to your profile.

    Note 1: You may say, “But my username is my name, just without spaces and capital letters/a last name.” You’re still on the list, because it’s in username format.

    Note 2: You may say, “Yes, I would really like people who google my real name to find my WP profile, but within the community, everyone knows me as my username. Quandry!” Not really. Take a page from some of the other people in your situation and put your username in parenthesis after your last name. In the coming year we’ll be making improvements to the profiles section, and having an optional way to display your username will hopefully be added.

    Below is a list of everyone is the 3.4 credits that is listed by username rather than regular name. If you see your username on this list, click on it to go to your wordpress.org profile. Log in. Edit links will appear. Click the one in the top section that controls name and description, put your real name in the Name field, and save it. Voilà, your real name will show up on the credits page.

    082net,
    akshayagarwal,
    ampt,
    Andrea_r,
    Barry,
    BenChapman,
    Billy (bananastalktome),
    camiloclc,
    casben79,
    Caspie,
    ceefour,
    cheald,
    chellycat,
    Cyapow,
    daniloercoli,
    deltafactory,
    demetris,
    dllh,
    ebababi,
    edward-mindreantre,
    emhr,
    Empireoflight,
    garyc40,
    Gautam,
    hearvox,
    insertvisionhere,
    Ipstenu,
    Japh,
    jaquers,
    jeremyclarke,
    Justin,
    Kuraishi (tenpura),
    Lardjo,
    Latz,
    linuxologos,
    Marcus,
    mattonomics,
    mgolawala,
    mrtorrent,
    Name.ly,
    norocketsurgeon,
    npetetin,
    Otto,
    pavelevap,
    pishmishy,
    prettyboymp,
    pw201,
    Rami Y,
    Rarst,
    redsweater,
    RENAUT,
    roscius,
    russellwwest,
    sirzooro,
    sksmatt,
    soulseekah,
    Stephdau,
    tamlyn,
    The Z Man,
    TobiasBg,
    transom,
    wonderslug,
    zx2c4

    We haven’t updated the photo sections of the credits screen yet, if you go looking.

     

    • sillyandrea 1:25 pm on June 5, 2012 Permalink | Reply

      Funny. I had my name typed in as Andrea_R. :D

    • Stephane Daury 1:38 pm on June 5, 2012 Permalink | Reply

      Done.

    • Mika Epstein (Ipstenu) 1:47 pm on June 5, 2012 Permalink | Reply

      Which profile? http://wordpress.org/support/profile/ipstenu or http://profiles.wordpress.org/ipstenu ?

      Cause last time I updated my profiles. info and it’s still not being picked up :)

      • Jane Wells 7:15 pm on June 5, 2012 Permalink | Reply

        profiles. Maybe check with @otto to see if something is up.

      • Andrew Nacin 7:32 pm on June 5, 2012 Permalink | Reply

        The props names are freshed every 12 or 24 hours on the WP.org side. In an individual install, it’s every 7 days. So two layers of caching you mean you need to wait for WP.org to refresh, then clear the transient in core. (Upon update from 3.3 to 3.4, the transient is immediately refreshed.)

        • Mika Epstein (Ipstenu) 11:29 pm on June 5, 2012 Permalink

          I changed that months ago. It’s not picking my name up. At all. Didn’t last cycle, didn’t now.

          My only guess is that since my forum profile says Ipstenu, the way I do that is borking something. I go back and flip that display name back after I edit at profiles. If I edit on profiles it pushes out to the forums etc.

        • Andrew Nacin 1:26 pm on June 6, 2012 Permalink

          All you’re doing is editing the same field back and forth. :)

        • Mika Epstein (Ipstenu) 7:10 pm on June 6, 2012 Permalink

          Except notice how on profiles it says ‘Mika Epstein (Ipstenu)’ and on the forums it says ‘Ipstenu’?

          So … are we saying “When you edit your name on the forums, it changes it for the list we pull from for the credits page, even though it never actually changes the display on the profiles page?”

          Cause I’ll live with being Ipstenu if so. I really don’t want to fiddle around and change my name on the forums after being ‘Ipstenu’ for over a decade ;) It would confuse more people than it would help.

        • Andrew Nacin 5:05 am on June 7, 2012 Permalink

          BuddyPress ignores “display name” and instead builds a name using the first name and last name fields. So that’s why you’re seeing two different things.

          I can look into tweaking the API to allow for special cases.

        • Mika Epstein (Ipstenu) 1:38 pm on June 7, 2012 Permalink

          As you like :) I’m not particularly hung up on it (google Ipstenu, you find me anyway ;) ), just insatiably curious as to how I broke things this time.

    • Bill Erickson 2:12 am on June 6, 2012 Permalink | Reply

      Hmm, why am I not showing up in the list of contributors? Here’s two props in 3.4 commits:

      https://core.trac.wordpress.org/changeset/20075
      https://core.trac.wordpress.org/changeset/20901

      • Jane Wells 2:17 am on June 6, 2012 Permalink | Reply

        If you read the post, the list here is ONLY people who have not added their real names. Your real name is already listed in your profile, so you’re not here on the ‘add your name’ list. Look on the credits screen and there you are, plain as day. :)

  • Jane Wells 1:24 am on May 24, 2012 Permalink | Reply
    Tags: community summit   

    Apparently not all contributors follow the official wordpress.org announcement blog. A) That’s crazy. B) If you’re one of those people you missed http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/ and should go read it now. I’m leaving open the nomination/application form an extra day for the people who missed it.

     

    • Aaron Brazell 1:26 am on May 24, 2012 Permalink | Reply

      Ha. FWIW, I do… I saw this. Buts it’s been a terribly busy month so maybe not as closely. Though I’m sure I’m not the only one who wasn’t aware.

    • Mr. Roy Arellano 1:39 am on May 24, 2012 Permalink | Reply

      I nominate myself; I love Tybee Island, GA. LOL.

    • Japh 1:40 am on May 24, 2012 Permalink | Reply

      I saw it (of course I’m subscribed!), but sadly being located in Australia makes it difficult to attend.

      • Jane Wells 1:56 am on May 24, 2012 Permalink | Reply

        You can’t win if you don’t play! Depending on how much I raise in sponsorship $ there may be some travel scholarships available.

      • Andrew Nacin 1:59 am on May 24, 2012 Permalink | Reply

        Also, given that you do evangelist and development work for a WordPress-heavy business, it would certainly be in their best interest to sponsor such a trip if you are accepted.

        • Japh 2:01 am on May 24, 2012 Permalink

          You’re quite right, which is why the timing is also an issue. I’m trying to get approval to attend WordCamp SF in August. Two separate trips so close together could be problematic.

          As Jane says though, can’t win if I don’t play!

    • Mr. Roy Arellano 1:41 am on May 24, 2012 Permalink | Reply

      Japh, we should do a supplemental summit here in the Pacific; I’m in Tokyo. :)

    • arena94130 10:17 am on May 26, 2012 Permalink | Reply

  • Jane Wells 8:20 pm on May 23, 2012 Permalink | Reply
    Tags: ,   

    Pre-RC Dev Chat 5/23/2012 Live Blog 

    • #16079 Automatic excerpts don’t work well with Chinese txt (word counting): Nacin is handling. Westi closed for 3.4.
    • #20703 wp.getComments logs in the user (1 + #comments) times: Unit tests = fast track to commit. Ryan doing so.
    • #20699 AJAX Actions now pass the action name as an arg: reverting to 3.3 behavior, Ryan will handle it. Re-assess for 3.5.
    • #20448 Update Twenty Ten and Twenty Eleven to use 3.4 features: Koop and Nacin to review Lance’s patch.
    • #20554 3.4 Feature Pointers: Change position of the one on Headers to be side pointer. Jane talking to Ryan Ozz.
    • #19599 Localizations should not need to worry about the default secret key: Nacin’s top priority.
    • #8759 Word count function doesn’t work in several languages: Nacin is handling. Westi closed for 3.4, wants new tickets for 3.5 as needed.
    • #20737 Improve appearance of “choose from library” link for headers and backgrounds: Wait and standardize in 3.5.
    • #20507 3.4 Preview/Customize page “Return to Manage Themes” link doesn’t work as expected: Koop says nacin is handling.
    • #20600 Customize and display_header_text(): Koop will fix, patch needs some more love before committing. (Don’t we all.)
    • #20692 Handle unsaved changes in the customizer: change to button style per Jane’s comment on ticket. Helen will try patching.
    • #20736 Move customizer to wp-admin/customize.php: Nacin.
    • #20582 Theme Customizer: IE 8/9 compatibility: @ryan‘s top priority
    • #20733 Theme customizer doesn’t order sections based on order added: @dkoopersmith couldn’t reproduce, others could. Jane suggested punting, but Koop/Ocean90/Sergey looking and will fix if a simple one. Otherwise, a nicety that can wait for 3.5.
    • #20423 About WordPress page for 3.4: Closed. Reopen if any typos, credits will be updated from wordpress.org .

    Tally for remaining ticket assignments:

    • Nacin – 6
    • Koop – 3 + 2 reviews
    • Ryan – 3
    • Helen – 1
    • Ozz – 1
    • Ocean/Sergey – 1
     

  • Andrew Nacin 3:33 pm on May 21, 2012 Permalink | Reply
    Tags: ,   

    On Saturday, Matt posted to the WordPress Blog that the plugin directory has been refreshed.

    Also also posted to our new P2 at make.wordpress.org/plugins: what this means for developers. @otto42, @coffee2code, and I go through the changes in detail. They include:

    • The new Developers and Support tabs for plugins
    • Subscribing to commit emails (Hint: see the Developers tab)
    • Following and managing support threads
    • How the new support statics are calculated

    (Sidebar: We hope to use make.wordpress.org/plugins for announcements and resources for plugin developers. This blog will also move to make.wordpress.org soon. More to come.)

     

  • George Stephanis 5:19 pm on May 3, 2012 Permalink | Reply
    Tags: android, mobile, target devices, ui enhancements   

    We’ve had some terrific progress made in the realm of supporting touch interfaces and tablet UIs for 3.4!

    The main areas that we’ve focused on for this release were improving touch support in the user interface, resolving incompatibilities for our target devices, and enhancing the UI’s methods for adapting to more restrictive screen sizes.

    Target Devices

    Our target devices for the 3.4 release were the iPad and the Kindle Fire. The iPad stands as an obvious choice, and the Kindle Fire’s steep climb to over 50% of market share amongst Android tablet devices justifies its presence as well.

    Improving Touch Support

    For touch-supportive devices, we’ve added a fantastic jQuery extension to the core, jQuery UI Touch Punch. This has enabled ‘drag and drop’ support on mobile devices. Whether editing a post, customizing the dashboard, or modifying a Nav Menu, you’re now able to easily reposition items on a touch interface to your heart’s content, just as you would on your desktop browser.

    Caveat: Windows Phone Devices

    Windows Phone 7/7.5 phones are wonderful devices. Unfortunately, when Microsoft based the phone’s web browser off IE9, they didn’t add in any touch support. As such, there is no way to detect touch events in the browser — `ontouchstart` doesn’t exist. Dragging support does not work on Windows Phone 7/7.5 devices, but should on Windows 8 tablets and phones when released.

    Resolving Incompatibilities

    This boiled down primarily to the Kindle Fire. The version of WebKit used in the Kindle Fire’s native Silk browser doesn’t support the contentEditable attribute, so TinyMCE wouldn’t work! To accomodate for this, we added an override to test for the version of webkit that the client is using, and just disable the visual editor if the browser doesn’t support it. This patch should also cross-apply to older versions of iOS and Android as well.

    UI Enhancements

    In Ticket #20015, we migrated the dashboard and write screen columns to use primarily @media queries, rather than the JS that had previously been used. This should provide some performance optimizations in mobile browsers.

    The Tableteer team for 3.4 was comprised of Andrew Ozz, Zach Abernathy, and George Stephanis.

     

    • Isaac Keyet 6:27 pm on May 3, 2012 Permalink | Reply

      Great work guys, looking forward to everyone having this. Tablets are here to stay!

    • donnacha 6:47 pm on May 3, 2012 Permalink | Reply

      I am grateful that work is being done on touch UI, it’s definitely the future, but … the Kindle Fire at 50% of Android tablets? Seriously?

      It is disturbing to hear that scarce dev resources are been allocated based upon comScore figures, they are an industry joke and base their numbers upon a highly suspect interpretation of private page view data. Their MO has always been to drive forward their main business, which is essentially an extortionate racket against websites, by generating sensational headlines and anything Apple-related is a sure-fire hit.

      IDC today released their figures, based upon actual shipments: iPad is 68% of the entire worldwide market of 17.4m tablets, the Fire is 4% (around 15% of Android tablets) and is soundly beaten by Samsung in 2nd place.

      http://www.idc.com/getdoc.jsp?containerId=prUS23466712

      Again, I am grateful that this work is being done but you should wait until at least six months before anointing any new tablet as a sort of standard, especially as Amazon have not even revealed how many post-Christmas returns they received.

      It is also worth noting that the upcoming Fire 2 is rumoured to be radically different machine i.e. the first Fire was a rush job to catch the Christmas market, the 2 may follow a very different design philosophy and that would put your UI decisions back to square one.

      I’ve never seen a Fire or Samsung tablet in real life but I presume that Samsung are running a less proprietary and, therefore, more representative version of Android than Amazon, why not target that instead?

      • George Stephanis 7:58 pm on May 3, 2012 Permalink | Reply

        While we had the Fire and iPad as our ‘target’ devices, please don’t misunderstand this as stating that they are the only devices that we paid any attention to.

        All our work is based on coding web standards — building for the future of the web so that the work we do today is maintainable and will look just as good (if not better) tomorrow. When we say that something is a ‘target device’ it just means that these are the devices that we’re making the conscious decision to purchase and test thoroughly on. I can tell you that we’ve also done a great deal of testing in a number of other Android tablets, BlackBerry Playbook tablets, Android Phones, and Windows Phone 7/7.5 devices.

        The reason for the Fire being a target device was that it was more likely to need a bit of special attention to get it up to working order. The native browser that comes bundled with stock Android works beautifully, but the bundled Amazon Silk browser has some problems, to put it graciously, primarily due to running an outdated version of WebKit as the rendering engine. There’s also a lot of missing CSS3 properties. If anyone would like to contact Amazon, one of the people to speak with would be Jon Jenkins ( twitter: @jonjenk ) — he does a lot of work on their Silk browser.

        Regarding your IDC citation, I’d be very intrigued to learn what devices they are including in their tablet calculations — the significant bump for Samsung may very well be due to the release of the Galaxy Note, which could have been more aptly lumped in with tablets than phones.

        • donnacha 8:31 pm on May 3, 2012 Permalink

          Thanks for clarifying what was meant by ‘target’ George, I took the other meaning but, yes, I can see that you would need to target extra attention towards the quirks of the Fire and the unique nature of Silk, even if it is not the leading Android tablet.

          I’m not actually sure what product lines were included in the Samsung numbers, I’m only going on the press release that I linked to, but I agree that the term “tablet” should only really include screens 7″ and up, the Note at 5.3″ strikes me as more of an overgrown phone than a tablet.

          The distinction between comScore and more reputable operations such as IDC is, though, still important to bear in mind when you are making decisions. One conducts closed box surveys heavily skewed towards people dumb enough to waste their time on incentivised surveys, the other does it’s best to jigsaw together an accurate reflection of reality based upon available shipping data.

        • George Stephanis 8:37 pm on May 3, 2012 Permalink

          Just for reference, the target devices were decided at some point before January 11th, when they were announced at the weekly dev chat.

    • Emil Uzelac 7:04 pm on May 3, 2012 Permalink | Reply

      Great job indeed, fantastic stuff. Keep up the good work.

    • Dan 9:24 pm on May 3, 2012 Permalink | Reply

      just disable the visual editor if the browser doesn’t support it

      Big win, I’ve worked with a lot of users that were frustrated that the editor didn’t work on their older Android devices. Nice job!

  • Andrew Nacin 7:04 pm on May 2, 2012 Permalink | Reply  

    A change to api.wordpress.org temporarily broke the API that powers the plugin install screens in your WordPress dashboard. If you saw “An unknown error occurred during the API request” when going to Plugins → Add New, it was us, not you.

    Sorry for the inconvenience.

    I’ve created a bug report to improve the error message shown to users, in the very rare event that something goes wrong on wordpress.org. That should be included in WordPress 3.4 (and is hopefully an error message you will never have to see).

     

    • herzcthu 4:25 am on May 14, 2012 Permalink | Reply

      Many Plugins’ details page is broken. It says “Notice: Trying to get property of non-object in /…./wp-admin/includes//plugin-install.php on line …. ” when WP_DEBUG is true.

      • Andrew Nacin 4:50 am on May 14, 2012 Permalink | Reply

        You left out the most important part :-) — which line?

        • herzcthu 11:27 am on May 14, 2012 Permalink

          on line 264, 269, 349

        • herzcthu 11:35 am on May 14, 2012 Permalink

          Effected plugins :
          egoplayer-video-player
          contus-hd-flv-player
          fv-video-player
          ezwebplayer-wordpress-light-video-plugin
          cincopa-video-slideshow-photo-gallery-podcast-plugin
          post-rich-videos-and-photos-galleries
          post-rich-videos-and-photos-galleries
          video-player-fx
          simple-flv

  • Andrew Nacin 3:18 pm on April 30, 2012 Permalink | Reply
    Tags: ,   

    The plugin directory’s licensing guidelines have been updated. The guidelines will now allow code that is licensed under (or compatible with) version 3 of the GPL.

    The guidelines still encourage use of “GPLv2 or later,” the same license as WordPress. However, we understand that many open source libraries use other licenses that are nonetheless compatible, such as GPLv2 only, GPLv3, and Apache 2.0.

    Now may be a good time for plugin authors to review their plugins to ensure a license is specified. You can add License and License URI headers to readme.txt and the plugin’s headers. (You may also wish to include a copying permission statement.) For example:

    License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

    You can see this used in the sample readme.txt.

    This change brings the guidelines in line with the themes directory, which has for some time accepted GPLv3-compatible code. (Probably a good time to note that Creative Commons licenses are still incompatible with the GPL, and the theme and plugin directories.)

     

    • Mike Schinkel 6:31 pm on April 30, 2012 Permalink | Reply

      Kudos!

    • Alid 7:53 pm on April 30, 2012 Permalink | Reply

      It would be nice to have a list with (in)compatible licenses for users which aren’t familiar with this topic.
      Since it’s also a problem if your plugin is GPL but your are using an external lib which is incompatible and you didn’t know that.

    • John James Jacoby 8:01 pm on April 30, 2012 Permalink | Reply

      Do you recommend still packaging a license.txt with plugins, or is the link in readme.txt sufficient?

      • Andrew Nacin 12:38 am on May 1, 2012 Permalink | Reply

        It’s good practice to include a license.txt or COPYING file. At the very least, you should probably include the copying permission statement, which would state, “You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.” At worst, as long as it is specified somewhere in the readme or code, at least people know what your intent is.

        And, if it is in the readme, we will be able to show it on your plugin’s page in the future.

    • Herb Miller 9:56 pm on April 30, 2012 Permalink | Reply

      I used the readme validator twice today. it worked earlier this afternoon then failed this evening. I was expecting some explanation would surface eventually. Currently the validator has trouble with the License: lines – sometimes suggesting that the description is too long as well

      • Mika Epstein (Ipstenu) 12:28 am on May 1, 2012 Permalink | Reply

        I’ve seen the same issue with the readme. Adding in the license lines gets it pushed into the Desc.

        I tend to use the copying permission, with “This file is part of PLUGINNAME, a plugin for WordPress.” and then saying the license should have come with WP. But then again I release GPL2.

        • Andrew Nacin 12:39 am on May 1, 2012 Permalink

          I pushed some changes earlier to fix some issues with the validator for the License lines. Can you still reproduce?

        • Mert Yazicioglu 9:49 am on May 1, 2012 Permalink

        • David Decker 11:12 am on May 1, 2012 Permalink

          It seems to add now the License URL to the short description word counter… :) Some plugins with a real short description work correctly, some with a longer like the mentioned “WordPress Move” work not.

          I’d like to see this fixed, as the update with the 2 new license short tags in the header is really helpful – especially when this is displayed on the plugin page on .org! ;-)

          Another suggestion for the short description: What about taking another short tag like:
          Short Description: Here goes it…
          or:
          Intro: Here goes it…

          Seems to be a bit more self-explaining as a lot of plugin authors still mix it all up and use the same – long – description everywhere making it less readable for users.

          Just my 2 cents.

          Thanks for all your hard work with repo – much appreciated! You guys really ROCK!!
          -Dave :)

      • Andrew Nacin 5:03 pm on May 1, 2012 Permalink | Reply

        This was fixed yesterday, but a few plugins had pages generated before then. I went through and re-generated the data for the 12 plugins affected. Should be all set.

    • Herb Miller 8:16 am on May 1, 2012 Permalink | Reply

      thanks, now I have more work ensuring all my source files have both Copyright AND (currently missing from some) a statement of copying permission, saying that the program is distributed under the terms of the GNU General Public License.

    • ← Older posts

    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
    Follow

    Get every new post delivered to your Inbox.

    Join 1,117 other followers