WordPress.org

Ready to get started?Download WordPress

Make WordPress Core

Updates from Lance Willett Toggle Comment Threads | Keyboard Shortcuts

  • Lance Willett 9:34 pm on December 3, 2013 Permalink
    Tags: , ,   

    Twenty Fourteen Project Update 

    Home stretch. Let’s polish.

    Finished

    • Launched the theme on WordPress.com (announcement, Theme Showcase page)
    • Many, many fixes to get ready for code freeze (see all commits since our last update): including RTL, IE, contextual help, layout, etc
    • Improvements based on feedback from core dev team (simplification, code readability and commenting)
    • Lots of activity at the WordCamp London Contributor Day

    A special thanks to everyone who participated in our “device testing and bug hunt” activity at WordCamp London, including but not limited to binarymoon, jartes, erichmond, janhenckens, sonjanyc, amistad18, iv.dimova, kdankov, robert olsen, iandstewart, chellycat, sixhours, cainm, blankthemes, thomasguillot, kwight, Frank Klein, siobhan, and defries. And all three of us on the Twenty Fourteen team were present: lancewillett, iamtakashi, obenland. [These are WordPress.org usernames.]

    Next

    • Wrap up final bug fixes: see open tickets
    • Make a Codex page for Twenty Fourteen help and tips—@siobhan to create the draft and kick it off

    Discussion

    What’s a pragmatic solution for detecting mobile and table devices? We’d like to use wp_is_mobile() but that seems designed for only admin use since it assumes no page caching. See notes at #26221.

     
    • Piet 12:46 am on December 4, 2013 Permalink | Log in to Reply

      Have a look at the Mobile Detect script (http://mobiledetect.net/). If I’m not mistaken it now also supports caching.

      • mbootsman 10:22 am on December 4, 2013 Permalink | Log in to Reply

        I use http://mobiledetect.net/ for some of my customers, seems to be doing the trick, and it is actively maintained.

        • serbanghita 4:35 pm on December 5, 2013 Permalink | Log in to Reply

          Thanks for recommending the class. Unfortunately it cannot use Mobile_Detect.class.php since that would require an extra plugin attached to the theme.
          It would have been nice to have a WordPress plugin that enhances wp_is_mobile() to use the Mobile_Detect logic.

    • George Stephanis 1:49 am on December 4, 2013 Permalink | Log in to Reply

      Possibly fire off a single ajax request that checks wp_is_mobile() and caches the result in localstorage?

    • Siobhan 11:39 am on December 4, 2013 Permalink | Log in to Reply

      First draft of Twenty Fourteen help for users: http://codex.wordpress.org/Twenty_Fourteen

      Feel free to edit or let me know if there’s anything you want me to add.

      • Lance Willett 4:24 pm on December 4, 2013 Permalink | Log in to Reply

        Thank you!

      • Nick 7:37 pm on December 11, 2013 Permalink | Log in to Reply

        Some quick specs would be great, like measurements in pixels:

        The standard content width for Posts and Pages is ????.
        Featured images should have a minimum / maximum width of ????

        Thanks!

    • Lorelle 10:43 pm on December 4, 2013 Permalink | Log in to Reply

      My college students decided on this Theme for their class magazine. They have a laundry list, one of which was reported immediately. We are going into finals this week, but I’ll have next quarter’s students rip this apart and hopefully contribute to the Codex doc as well.

      One immediate request from them is to fix the lack of author features. This is designed as a magazine site, so highlighting the authors is important. They would like to see the author description used on author pageviews, and the author description also at the bottom of the single post pageviews, something that is typical of most WordPress Themes designed for multiple contributors, and not.

      Thanks again to the entire team for such a great Theme. They had a blast digging into it – and have a lot of praises as well as whines. Love it!

    • Colleen 7:12 pm on January 30, 2014 Permalink | Log in to Reply

      What I really need is for the Full Width Page to really be full width. Just leaving off the widgets does not do anything to widen the page. I need to post a full month view of a calendar on our calendar page and it doesn’t fit. It seems we only have about 450 pixels to work with – even in Full Width View. Please expand it so we can use the full white part of the page.

  • Lance Willett 6:11 pm on November 12, 2013 Permalink
    Tags: , ,   

    Twenty Fourteen Project Update 

    Crunch time! We’re working hard to make sure everything’s ready for 3.8 release. We’ve listened to all your feedback, thank you—including lots from last week’s dev chat. We’ve made significant improvements in the last week.

    Many improvements

    Author widget

    Too late to get it into 3.8 dev? It’s fairly light and can merge right away.

    Last week at 3.8 features-plugin meeting we forgot to suggest this; we’d worked on it as a plugin first, see #24856: “Authors widget to highlight authors.”

    This is a new widget for any theme to use, but we’d planned to show it off with Twenty Fourteen because as a magazine theme it’ll feature and show off multiple authors.

    On our radar

    • Strategy for 3.7 and earlier non-MP6 handling #25906
    • Accessibility feedback on the slider
    • More work on contextual help and the user experience with Twenty Fourteen, maybe including user testing and research
    • Launching the theme on WordPress.com to get early feedback from real usage
    • Code review with core dev team
     
    • jeffr0 6:14 pm on November 12, 2013 Permalink | Log in to Reply

      Did you folks already have your meeting today?

      • Nick Halsey 6:18 pm on November 12, 2013 Permalink | Log in to Reply

        We’ve mostly just been looking at a few remaining things casually, you could definitely jump in with any questions/comments/feedback now (in #wordpress-themes).

      • VenturaVan 6:50 pm on November 12, 2013 Permalink | Log in to Reply

        Can anyone tell me if there is any work being done on colorizing the menu system? I am sooo tires of having to pay for custom plugins that sometimes break to make my menu’s colorful. Top level one color, second level another, third level another, etc. etc and being able to change those per category or per page.

        • Lance Willett 7:12 pm on November 12, 2013 Permalink | Log in to Reply

          Colorizing the menu isn’t part of the scope for this theme. The Accent Color option allows to change from the default green hue, though.

    • Lance Willett 5:51 pm on November 20, 2013 Permalink | Log in to Reply

      Launching the theme on WordPress.com to get early feedback from real usage

      Soft launched on WordPress.com today: http://en.blog.wordpress.com/2013/11/20/twenty-fourteen/. Soft meaning we’ll make a much bigger and louder hullabaloo with 3.8 release in core.

    • Mads Konradsen 9:13 pm on November 20, 2013 Permalink | Log in to Reply

      So Twentyfourteen will first be released on wordpress.org/themes along with 3.8?

    • Bharat Karavadra 6:45 pm on November 23, 2013 Permalink | Log in to Reply

      Hi Lance,
      I was playing around with customising twentyfourteen and I noticed a slight issue with the CSS media queries when looking at the theme at resolutions as defined in the CSS as (min-width: 594px) and (min-width: 673px).

      The issue arises when the site-main background is customised to have an image (and probably also when coloured), where the padding on the entry-header and entry-content varies at the above resolutions producing an odd looking T shape block for the combined entry-header and entry-content.

      You will hopefully better understand what I am describing at a page I created with some snapshots and notes at http://www.karavadra.net/blog/2014-entry-padding/

      Thank you,

      Bharat

    • Bharat Karavadra 1:21 pm on November 25, 2013 Permalink | Log in to Reply

      Also, when logged into WordPress and the Admin bar showing on the user side, the horizontal black header drops down below the admin bar by 4 pixels at resolution widths over about 790px which causes the site description at the top of the left bar to be slightly cropped and the white background appearing above the horizontal black site header.

    • Bharat Karavadra 1:27 pm on November 25, 2013 Permalink | Log in to Reply

      I just noticed that the drop on the site-header is not happening on http://twentyfourteendemo.wordpress.com/ when loggef into wordpress.com but only on self hosted wordpress.

    • Bharat Karavadra 7:01 pm on November 25, 2013 Permalink | Log in to Reply

      Hi,
      The issue with site-header dropping about four pixels is only happenng when using wordpress 3.7.1 or later nightly builds. I just upgraded to wordpress 3.8 beta 1 and the 4 pixel drop is not happening.

      However the padding of the entry-header and entry-content remains inconsistent in the browser widths mentioned above.

    • Lance Willett 12:39 am on November 26, 2013 Permalink | Log in to Reply

      Hi Bharat, please see our open ticket list, we have these already added there.

      • Bharat Karavadra 12:19 pm on December 10, 2013 Permalink | Log in to Reply

        Lance,
        I have just installed 3.8 RC2 and the padding issues with the entry-header and entry-content that I commented on above on Nov 23 still remain and on looking at the tickets – these issues are not the opens ticket list and I haven’t used the ticket system before so I’m not quite sure how to document this.

        • Lance Willett 2:31 pm on December 10, 2013 Permalink | Log in to Reply

          Hi Bharat, the background color/image and “T” shape isn’t something we’ll fix in the default theme, but could be addressed on an individual basis for a child theme as needed.

          • Bharat Karavadra 10:25 am on December 11, 2013 Permalink | Log in to Reply

            Thank you for the reply. I will try my hands at DIY on this and perhaps submit it as a ticket as an prospective enhancement,,

    • Bharat Karavadra 1:50 pm on November 26, 2013 Permalink | Log in to Reply

      Thank you Lance, I thought there would be a more appropriate place to submit such issues but I couldn’t find it. I’ll take a look at the ticket list now.

    • dejudicibus 12:28 am on December 26, 2013 Permalink | Log in to Reply

      Lance, I am using 24 Theme just now. I have a TOP MENU as primary and a SIDE MENU A as secondary. Now, in TOP MENU I have two items: A and B. When I click on B I would like to change the secondary menu to SIDE MENU B. But how? Currently which menu is assigned to which location is selected by admin panel, and there is no way to change it in a dynamic way. Any hint?

  • Lance Willett 2:17 pm on October 31, 2013 Permalink
    Tags: , ,   

    Twenty Fourteen Project Update 

    Status

    We’re right on target—making lots of progress on the main features in the theme. Finishing up within 1-2 weeks, then switching gears to verifying and testing (things like device testing, RTL, older browser support, accessibility, and more).

    Finished

    • Implemented alternate slider view for featured content #25550
    • Implement featured content settings for authors to control which posts are displayed, and how many #25549
    • Used SVG images instead of CSS3 gradients for speed and responsiveness, more browser support, and vector-based scalability r25865
    • Allow any page to be set as front page #25685
    • Several passes at CSS code revamp to meet WP style standards and better organization and efficiency #25592
    • More accessibility fixes #25054

    Next

    • Accessibility feedback on the slider
    • Featured content options moved completely into Customizer (tag, display, count)
    • Accent colors: decide on keeping this feature in the theme #25563 #25580
    • Decide on pros and cons of creating an extra-large image size for full-width featured images #25758

    On our radar

    • RTL and IE fixes
    • Mobile and tablet device testing
    • “Breaking” the theme in every way possible

    Join us! Weekly office hours are Tuesdays and Thursdays at November 5th, 2013 17 UTC.

     
    • jeffr0 2:32 pm on October 31, 2013 Permalink | Log in to Reply

      When can I start asking questions about the final product? For example, is what I see on http://twentyfourteendemo.wordpress.com going to be the final layout of the theme? Or is the team still experimenting with different elements? All of that wasted space on the right bothers me as does not having the content area be wider.

      • Lance Willett 2:47 pm on October 31, 2013 Permalink | Log in to Reply

        Any time—why not join our office hours next Tuesday? The design is mostly final, won’t be changing much other than small tweaks for browser/device support and accessibility.

      • Lance Willett 12:35 pm on November 1, 2013 Permalink | Log in to Reply

        Hi again Jeffro,
        Here’s the relevant Trac ticket where Takashi (the theme’s designer) talks more about the decisions behind the content width: #25013.

    • LittleBigThing 3:45 pm on October 31, 2013 Permalink | Log in to Reply

      How can I download the theme to test it? Or is it too soon for that, do I have to wait till the beta release of WP 3.8?
      Sorry, I am obviously a rookie in contributing…

    • Nick Halsey 4:37 pm on October 31, 2013 Permalink | Log in to Reply

      I should have the featured-content-settings-in-customizer patch up on #25549 tonight. I’m running into a lot of the same issues there as with the accent color feature, so we should probably wait for the featured content stuff to get in to evaluate accent color further (ie, we may want to explore some core enhancements to simplify both).

    • jeffr0 7:58 pm on November 7, 2013 Permalink | Log in to Reply

      Can anyone explain how to actually use the Featured Content or get it to display? I can’t figure it out. Looks like it’s category based but when I created a Featured category and applied a post to it, nothing showed up.

    • jeffr0 5:19 am on November 8, 2013 Permalink | Log in to Reply

      I looked it up and 1700 UTC was 12 noon Eastern time so 3PM was already passed the meeting. Unless I’ve got UTC to EST all messed up?

  • Lance Willett 3:52 am on October 11, 2013 Permalink
    Tags: , ,   

    Twenty Fourteen Project Update 

    Things we’ve finished:

    • Many accessibility fixes: keyboard navigation for main menu, color contrast, Skip to Content links, remove all unneeded title attributes: #25054
    • Allow featured images to work on pages (not just posts), a better UX for index vs. single views, and better layout and handling when no featured images exist: #25325
    • Simplified sidebars to allow a wider layout: #25031, remove a confusing front-page only widget area: #25565—after a long discussion about the Ephemera widget and how it should interact with the main stream of blog posts: #25330
    • Myriad layout and style fixes

    Big things we’re working on next:

    • Deciding on whether or not the core Header Text Color feature should be disabled for Twenty Fourteen: #25540
    • Implementing “Plan B” for featured content: #25549
    • Building an amazing alternative view for front page featured content—yes, a slider! #25550
    • Triage all our open tickets for Twenty Fourteen.

    Join in the fun! We have weekly office hours, Tuesdays and Thursdays at Tuesday 17 UTC) as well as general “Bundled Themes” bug scrubs, Fridays at Friday 18 UTC.

    [Update: fixed the Trac links. I guess they can't be in parentheses.]

     
  • Lance Willett 11:10 pm on September 20, 2013 Permalink
    Tags: , ,   

    Twenty Fourteen project update 

    We’re continuing regular office hours on Tuesdays and Thursdays at Tuesday 17 UTC) as well as general “Bundled Themes” bug scrubs, Fridays at 18 UTC.

    Done since last time:

    • Accent color theme option added: #25220
    • Added a “Contributor” page: #24863
    • Lots of layout and style fixes
    • Fixing how Genericons are loaded: #25085

    In progress:

     
  • Lance Willett 7:49 pm on September 3, 2013 Permalink
    Tags: , ,   

    We’ve made lots of great progress over in Twenty Fourteen theme land.

    This update is long because it’s my first one since we kicked off. Subsequent reports will be shorter.

    Goals

    In short, make it an awesome default theme.

    1. Polish, “break”, and perfect the theme.
    2. Add enhancements and new features.
    3. Integrate with 3.8 plugin projects as we can.

    Who we are

    (These are WP.org usernames.)

    • Leads: lancewillett, obenland, and iamtakashi
    • Many patches have come in! Thanks to: cainm, celloexpressions, DrewAPicture, eherman24, Frank Klein, georgestephanis, iamtakashi, Jayjdk, jeherve, joedolson, Jonnyauk, kovshenin, Kuzmanov, MikeHansenMe, nofearinc, obenland, rickalee, sabreuse, and SergeyBiryukov.
    • Many other contributors have joined the fun, including but not limited to: cfinke, chellycat, jazzs3quence, johnbillion, karmatosed, McGuive7, nacin, nhuja, paolal, RDall, rmccue, taupecat, trishasalas, and shaunandrews.

    You can get still get involved in any of these activities:

    • Putting up new tickets for bugs or enhancements (plus a patch if you can).
    • Review and test patches on existing tickets, add comments to the ticket.
    • Join the 3.8 plugin projects like Featured Content.
    • Help with theme breaking: IE, RTL, accessibility.

    Big things we’re working on now

    So far we’ve seen 38 related tickets in Trac opened, closing 24 already. View all open tickets.

    • (Possible) removal of Custom Header Image support: #25094
    • Accessibility review and fixes: #25054
    • Adding a “Contributor” page: #24863
    • Allowing color customization for “accents”: #25220

    The removal of the header image, along with which customization options to allow and support, has been a very healthy discussion. See #25094 if you want to read along.

    Big things we’ve already tackled

    • Updating to use HTML5 markup from core for search, comment form, and comment list.
    • Added missing archive templates.
    • Many usability fixes.
    • Lots of code cleanup.
    • Added Editor Styles to enhance the visual editor.
    • Sidebar improvements: widgetizing special Post Formats display, making right sidebar optional, and more.

    One thing I wanted to highlight was removing the Social Links options from the theme. Instead inserting the search form and the search form toggle through filterable template tags, so that a plugin could hook in and add that feature back in. (Full chat log.)

    Related plugin projects

    Work continues on Featured Content and the Authors widget: #24856.

    Office hours and Trac triage

    We’ve had regular and very productive office hours on Tuesdays and Thursday at 17 UTC (In your time zone: 17:00 UTC). Thanks to everyone who’s joined us, your input is very valuable.

     
    • Lance Willett 8:30 pm on September 6, 2013 Permalink | Log in to Reply

      Schedule note: no official office hours next Tuesday, September 10th, as several of us will be offline.

    • Jean-Pierre Michaud 2:26 pm on September 15, 2013 Permalink | Log in to Reply

      can you keep us updated on this please? there is not much developped right now or it is minimal to disable the main features of that theme — which i thought was the illogical path, but hey, i can handle…

  • Lance Willett 5:06 pm on August 9, 2013 Permalink
    Tags: , ,   

    Twenty Fourteen theme project kick-off 

    Are you interested in contributing to the new default theme?

    Twenty Fourteen example

    We’ll kick off office hours for 3.8 cycle next Tuesday August 13, 17 UTC, in #wordpress-dev IRC. Covering goals, scope, and how best to split up tasks. If time allows we can jump into tickets.

    Then throughout the 3.8 cycle making the office hours a habit on Tuesdays and Thursdays at 17 UTC.

    Don’t worry if you can’t make it every single chat—we’ll be posting here with the twentyfourteen tag to keep you updated—and you can follow commits and tickets via Trac.

    For a bit of background on the Twenty Fourteen theme, see notes in #24858 and the already-growing list of open tickets. Let’s get to work!

     
  • Lance Willett 5:15 pm on May 9, 2013 Permalink
    Tags: , ,   

    We’re getting very close This week focusing on… 

    We’re getting very close.

    This week focusing on RTL again, especially concerning :before and :after and Genericon placement, see #24287. Turns out we’ll need flipped versions of lots of the glyphs—which Joen is now working on. After Joen completes the Genericons font updates are ready we’ll sync them into Twenty Thirteen.

    Next is another quick pass at editor styles, including RTL support there.

     
  • Lance Willett 4:25 pm on April 23, 2013 Permalink
    Tags: , ,   

    Twenty Thirteen project update, April 23, 2013 

    The focus for Twenty Thirteen right now test, test, and test. Polish, polish, and polish. The IEs, RTL, testing with lots of popular plugins. Getting things working smoothly with the new core post formats functionality.

    Priorities

     
  • Lance Willett 6:37 pm on April 8, 2013 Permalink
    Tags: , ,   

    We love testers

    We’d love more people to install Twenty Thirteen, with special emphasis on trying out all the new Post Format features.

    Also, if you have access to Windows with various versions of Internet Explorer we especially need help testing out some IE8 and IE10 issues (see Trac list link below).

    Priorities

    • Address open tickets in Trac, fix bugs and make improvements
    • More browser, device, RTL, and i18n testing
    • Post formats testing. For example, looking at the output from post_formats_compat(), making suggestions like Image should use wp_get_attachment_image() there for filters and correct core class attribute values in the resulting HTML.
    • Review and possibly refactor the js/functions.js JavaScript file, going to all procedural/functional or moving to a new architecture—the key is to be consistent with it within the file. We can also look at namespacing the events.
    • Ask Joen to do another design audit, checking versus his design vision for things like spacing, colors, and post formats.

    Office hours

    We’ll get back to office hours in #wordpress-dev IRC over the next few weeks, Tue and Thu at 17 UTC.

     
    • celloexpressions 1:40 am on April 9, 2013 Permalink | Log in to Reply

      Can’t make it to the office hours, but want to point out a couple more IE 8 issues that may or may not be ticket-worthy. The headings are displaying in Georgia font, but Bitter should work for IE 8. It’s fine on 9 and 10.

      Also, the header image is zoomed in in IE 8. See both issues in these screenshots (emulating 8/9 with 10): http://celloexpressions.com/nh/twenty-thirteen-fonts-ie8.png, http://celloexpressions.com/nh/twenty-thirteen-fonts-ie9.png.

      By the way, is IE 7 supposed to be supported/should it be tested?

    • ziegenberg 3:00 pm on April 9, 2013 Permalink | Log in to Reply

      Here’s a WP 3.6 with (slightly altered – just colors) Twenty Thirteen. Working great so far!

      http://zubau.at

      • Lance Willett 9:53 pm on April 10, 2013 Permalink | Log in to Reply

        Thanks for the link—cool color scheme! I’m seeing a few bugs in the comment form layout, though. Will need to debug and fix soon.

    • lisafirke 2:20 pm on April 15, 2013 Permalink | Log in to Reply

      Love the brave new look of TwentyThirteen– I’m working on a child theme for my personal blog… (It’s live but on the QT so I’m not too worried about glitches at this point).

      A few issues I’ve seen… with the fixed navbar, the header image I hacked/inserted into the masthead overlays and hangs below the bar. I know I can turn this behavior off by commenting out the JS but it may be an example of a use case that your more dive-into-the-code users will encounter. (I wanted that image to scale, which is why I inserted it as I have…)

      Other notes: I couldn’t get the JetPack carousel to work with the gallery post format as it does on the demo. Not sure if I just missed a step or if it’s not hooked into the theme correctly.

      The Status post format looks odd with an image floated left on the post… I nixed the background dotted line, but the Genericon (or whatever is producing the horizontal bar glyph in place of the title) is kind of distracting, too.

      Here’s the link: http://lisafirke.com/blog

      Looking forward to rolling out the finished version with much fanfare…

      • Lance Willett 5:38 pm on April 15, 2013 Permalink | Log in to Reply

        Hi there, and thanks for your notes. The fixed navbar + inserted HTML image isn’t a bug we’ll fix in the core theme—that’s a great example of child themes adjusting and changing how the core theme works.

        We’ll investigate Jetpack Carousel and the Status post format left-aligned image a bit more.

        • Lance Willett 5:29 pm on April 16, 2013 Permalink | Log in to Reply

          Lisa: can you give more info on the Jetpack Carousel issues you had? I couldn’t repeat—seems to be working normally with all the various “types” of galleries in Jetpack.

          • lisafirke 9:12 pm on April 16, 2013 Permalink | Log in to Reply

            See my notes below. I think it’s a jquery/Jetpack glitch of some kind, because others are reporting similar issues with Jetpack.

            The main thing is, with Jetpack enabled, I’m still not seeing any formatting options for the carousel–I only have the ability to toggle from slideshow to grid on a gallery post.

            • Jeremy Herve 10:29 am on April 17, 2013 Permalink

              You’re probably right. We know of some conflicts between jQuery 1.9.1 and Jetpack Carousel, and we”ll get this fixed before 3.6 ships.

              See this ticket for more details about the conflict.

      • Lance Willett 4:40 pm on April 16, 2013 Permalink | Log in to Reply

        Hi again Lisa, to get rid of the horizontal bar glyph for Status posts, look for:

        .format-status .entry-content p:first-child:before
        

        And either change or comment it out in your child theme.

      • jrbeilke 5:28 pm on April 16, 2013 Permalink | Log in to Reply

        lisa was there a specific browser that you were having trouble with the JetPack carousel?

        I’ve got 3.6 beta on my blog and loaded up a carousel post with JetPack slideshow ok.

    • lisafirke 7:25 pm on April 16, 2013 Permalink | Log in to Reply

      I’m using Safari and the latest beta build. I fixed a javascript error that was preventing the slideshow from running, but I don’t see any way to enable a full-screen slideshow. Here’s my test post: http://lisafirke.com/blog/2013/carousel-test/

      • lisafirke 7:29 pm on April 16, 2013 Permalink | Log in to Reply

        I’m thinking the problem lies with Jetpack and not with TwentyThirteen?

        • lisafirke 8:18 pm on April 16, 2013 Permalink | Log in to Reply

          I disabled my test, so don’t bother clicking through. Only the background color and exif field data items are getting displayed as configuration options–and in the media ui no choice of carousels or any other configurables beyond “slideshow” versus “grid”.

    • Ipstenu (Mika Epstein) 8:02 pm on April 16, 2013 Permalink | Log in to Reply

      There are posts in Alpha/Beta about 2013 – http://wordpress.org/support/forum/alphabeta

      (look for the ones that aren’t resolved)

      • Lance Willett 8:55 pm on April 16, 2013 Permalink | Log in to Reply

        Thanks, triaged 3 of the unresolved ones (1 was not related to Thirteen specifically).

        • Ipstenu (Mika Epstein) 9:58 pm on April 16, 2013 Permalink | Log in to Reply

          Shirley :) Is there a good way to report them or flag them for you? I don’t know enough about what is and isn’t a theme decision (seriously, I hate debugging themes!) to feel comfortable raising tickets.

          Also if you’re not a forum mod, I’ll make you one so you can resolve those posts too ;)

    • Jeremy Herve 10:37 am on April 17, 2013 Permalink | Log in to Reply

      As discussed yesterday during office hours, I tested 2013 against Jetpack Trunk, and found 2 issues, that we will have to fix in Jetpack before 2013 is released.

      Infinite Scroll seems to work fine, whether you use footer widgets or not. All widgets seem to be displayed properly, although I haven’t tested in IE.

      No problems with post formats either. There were some conflicts between Jetpack Shortcodes and the new Audio shortcode, but it was fixed in r696694-plugins.

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