WordPress.org

Ready to get started?Download WordPress

Forums

[closed] What Should 2011 Hold for WordPress? (159 posts)

  1. mrjonwhite
    Member
    Posted 3 years ago #

    • A significant simplification (e.g., with some built-in, ready-to-go GUI/front-end elements) of the functions.php protocol for creating, and CPT-associating, Custom Fields meta boxes, of various types. Right now it's so easy, and so lean, to hand-register Custom Post Types and Custom Taxonomies. The third piece of that WordPress-as-CMS trinity -- meta keys/values -- are still too prohibitively verbose & cumbersome to write, practically, without the help of a Plugin (like Verve or MagicFields). At the end of the day, no one's using CPTs without also the need to throw at least one (or twenty) custom fields at it, too. Custom Taxes can only cover so much.
    • An oldie but a goodie: The out-of-the-box ability to assign arbitrary one-to-many Post (of any Post Type) relationships. The table infrastructure is so close, and the stopgap Plugins that fake it now are so thin. It's the one missing piece that makes WP-to-clients evangelism so....tricky.
    • Not a request, but a comment: You guys are the best. Thank you for keeping this rolling so intentionally.
  2. Daniel_Immke
    Member
    Posted 3 years ago #

    I would like WordPress to stop inserting its own CSS in wp_head, also class names for functions like wp_list_pages could include the slug, that would be incredibly helpful.

    I know there's a ton more stuff, I've just forgotten it all. I will start keeping a list.

  3. Mike Schinkel
    Member
    Posted 3 years ago #

    At this point I'm pretty happy with WordPress so all the features people mention would be great but few if any stand out as a lot more than any others to me.

    However, may I ask some of the others to elaborate on some of the things they suggested? I'm unclear on some requests (maybe others are unclear too?) Can the people who suggested these please elaborate? Thanks in advance:

    • Standard Pagination (what specifically?)
    • Improve the Taxonomy API (how?)
    • Simplify the Taxonomy Table Structure (that scares me; how do you envision this?)
    • Improve the Import/Export System (what do you envision here?)
    • More Intuitive Menu System (how? what (about it) is not currently intuitive?)

    Again thanks in advance to everyone for helping me (and others) understand what these requests mean.

    BTW Jane, if I had to pick I think you should have 3.2 be the version that is "All-about-Media". I know it's been something you've wanted for several years. Why not go ahead and focus all effort on a world-class revamp of the media handling in WordPress for the next version after this one?

    JMTCW.

    -Mike

  4. Tuxman
    Member
    Posted 3 years ago #

    +1 for Core Plugins. I want my WordPress to be my lightweight blog system, not my media management console...

  5. Mayur Jobanputra
    Member
    Posted 3 years ago #

    WordPress is reaching a level of maturity now where even novice end users are using it to create lightweight business websites. Often a web designer will do the setup, and then hand off the keys to business owners.

    The problem is that the admin interface, as good as it already is for the advanced user (typically a web designer or computer-savvy person), still has too much for the novice user that just needs to perform less than 10 functions.

    I would love to see an even simpler interface for the admin system. I know plugins and themes exist, but they tend to fail or conflict whenever WordPress is updated.

  6. rajuru
    Member
    Posted 3 years ago #

    Hi,
    I am expecting a few things that may need much work :P.

    1. It should go full OOP!
    2. review system for plugins
    3. centralize bug reporting (using trac) for plugins! I mean we can report bugs for any plugins on plugin repository rather than third party site or support forum!

    Thanks

  7. Alok Sharma
    Member
    Posted 3 years ago #

    Ability to store custom fields in wp_post table and functionality to store, recall or display them.

    I am working on a project which will have 10,000,000+ posts (which makes around 30,000,000+ entries in wp_postmeta table) assuming if each post requires a minimum of 3 custom fields.

    I believe that many people are looking for this type of functionality.

  8. moshthepitt
    Member
    Posted 3 years ago #

    +1 for this from mrjonwhite:
    A significant simplification (e.g., with some built-in, ready-to-go GUI/front-end elements) of the functions.php protocol for creating, and CPT-associating, Custom Fields meta boxes, of various types. Right now it's so easy, and so lean, to hand-register Custom Post Types and Custom Taxonomies. The third piece of that WordPress-as-CMS trinity -- meta keys/values -- are still too prohibitively verbose & cumbersome to write, practically, without the help of a Plugin (like Verve or MagicFields). At the end of the day, no one's using CPTs without also the need to throw at least one (or twenty) custom fields at it, too. Custom Taxes can only cover so much.

    Also:
    I would love the ability to have content type single page templates. Meaning that we should have the ability to create post templates or custom post templates much the same way that we can create page templates. This is especially true for custom post types.

  9. equalmark
    Member
    Posted 3 years ago #

    I would like to see some sort of meta box system for custom fields. Perhaps that can be defined similar to custom post types and custom taxonomies. This would help making WordPress into a great CMS.

  10. Milan Dinić
    Member
    Posted 3 years ago #

    @rajuru There is a Trac for plugins. Problem is that very low number of developers are using it.

  11. Andrés Sanhueza
    Member
    Posted 3 years ago #

    Summarizing stuff I have proposed elsewere:

    —A better approach to post formats, like something that actually simplifies the UI with only the needed fields instead of letting the theme do calculations of how interpret it, as I explained better here: http://wordpress.org/extend/ideas/topic/a-better-approach-to-post-formats
    —Add a 'question' post format. This is very nit-picky, yet I suggest it because post formats are a fixed thing by now and it's actually used in some micro-blogging systems. I try to explain it better here (including replies) http://wordpress.org/extend/ideas/topic/add-a-question-post-format
    —Consider upgrading the Blicki plugin.
    —Consider upgrading the self-hosted VideoPress framework (I think is considered for the 3.2 release, but still).
    —Convert the links feature into a custom post type. By now it looks like something like a plugin should do, so instead of removing it, it could be better make a post type to harmonize better with the rest of the system and maintaining all the current features.
    —Allow the taxonomies to hold metadata. This by itself may solve a lot of problems that by now have to resort to proprietary workarounds.
    —Fix a great bunch of bugs with the shortcode API that are still waiting in the trac.
    —In general, instead of adding to many nitpicky stuff for each release that's hardly extensible for the users, try to make the API even more flexible and trying to get an approach similar to CCK in Drupal. Drupal has the problem of having a ridiculous learning curve, but it actually much more flexible in terms of how can you play with fields, views and stuff. For example, you may allow to put some of the default metaboxes more than once in a custom post type (if that's already possible, don't worry), and give more flexibility to the options of the default metaboxes, even if they aren't used in core by default (something like, allowing something like a "post thumbnail" metabox that can hold any kind of file from the library, not just images and maybe more than one per page).

  12. McGarityDotMe
    Member
    Posted 3 years ago #

    @MikeSchinkel I made the comment about "Improve the Import/Export System" because recent versions of WordPress moved this out of core and into something akin to a plugin (e.g. that you install it), but the quality of the exports broke. It no longer works as well as it used to, and some with multi-site have complained about its functionality. I'd like it to work once again, plus offer some better options for importing (ex: ability to select specific posts, versus editing the XML manually, etc.).

    @Jane One core feature would be the ability to queue posts, but only there is interest in stealing thunder from Tumblr (which Custom Post Types somewhat do).

    +1 on Andres's suggestion for simpler Custom Post UI OOTB

  13. Simon Blackbourn
    Member
    Posted 3 years ago #

    I'd like to see a continuation of the process of introducing new features then seeing if/how they're used by developers before they get fully developed (as was done with custom post types). This is a great way to democratise the development process, prevent unneeded bloat and minimise UI revisions.

    There has been (very) partial support for custom post statuses up until now, I'd love to see more support for these so developers can start to use them: Trac ticket 12706.

    A taxonomy meta system (as mentioned by @AndrésSanhueza above) would be great too. There's currently the possibility to add fields to taxonomies in the UI, but no standard system for saving them in the database.

  14. saqwild
    Member
    Posted 3 years ago #

    hi,
    everyone else has already spoken about main features in details.

    my short and quick thought is
    1. simplify the use of custom field
    2. by default custom field grouping/duplicating/recalling
    3. read more/view all link for category and tag (display first xx followed by the link same as "Read More"
    4. default search option for search by post/post_type/tag/category etc

    thanks

  15. stanzl
    Member
    Posted 3 years ago #

    I'd love to see WP in OOP!
    I know this is a lot of work, there'll be compatibility issues with Plugins ans Themes, but think of all the great possibilities with oo code in place (not to mention grandchild-, great-grandchild-themes etc.)
    You could skip a release cycle or two (or three), like you did for wordpress.org and REALLY be poetic! :)

    P.S. Until you're there: Core Plugins would be awesome!

  16. Erlend Sogge Heggen
    Member
    Posted 3 years ago #

    All plugin activities in one place

    The mirrored listing of compatible WordPress plugins on BuddyPress.org is very handy. The fact that BuddyPress.org members can interact with any “mirage” by voting, reviewing and even discussing is plain wrong, since it splits activity. Figure out where you want the plugin’s activity to go down and make every “mirage” nothing more than a reference to the real thing.

    Looking at how BuddyPress deals with plugins, I’d say it would easily make the perfect plugin directory (by applying BP to wp.org). One great feature yet to be utilized is RSS feeds. By allowing plugin authors to add their own RSS feeds to their plugin listings, users would have a much easier time keeping up with external blog- and forum posts. The only thing missing is a proper bbPress integration which would allow for more flexible use of forums, the same way WordPress.org currently uses them.

  17. Justin Tadlock
    Member
    Posted 3 years ago #

    My suggestions:

    • Continue streamlining code, getting rid of cruft, and improving inline documentation of the code. I woulnd't mind seeing an entire major release focused solely on this.
    • Put new features to "wow" users in core plugins rather than core itself (example: admin bar) and keep core lightweight.
    • I'd love for dynamic sidebars to behave more like nav menus. Themes register "theme locations" and users assign custom-created sidebars to these locations. This would make things such as contextual/dynamic sidebars much easier and users wouldn't lose sidebars when switching themes.

    +1 to other suggestions:

    • Term meta table or some way to add metadata for terms.
    • Some way to handle post-to-post relationships.
    • Centralized way to handle unit tests.
    • PHP 5.2+.
    • Drop IE6 support.
    • Establish a consistent API for front-end and admin Ajax interactions.
    • Build a better API for plugins to extend the nav menus, specifically adding new menu item types.
    • Finish custom post statuses (#12706).

    -1 to other suggestions:

    • Grandchild Themes: If you need these, your theme author is doing it wrong.
    • Post type / meta box UI: These things are custom. A UI will never be able to handle the complexities involved. Improve how meta boxes are done if needed.
  18. mguillau
    Member
    Posted 3 years ago #

    I would like to have the possibility to attribute different menus to different pages.
    This would be especially interesting for multilingual sites.

  19. Malcjohn
    Member
    Posted 3 years ago #

    But i want to say one thing. It’s very, very important. I will not criticise the “production of next version”, but i will tell you the truth.
    As far as i know : somebody says “the next realse will be on 15.7.20xx ” and the major improvements are …….
    Afterwards, admin make a timetable and tickets starts to be doing.

    So from this moment its a bad start to close tickets. Nobody should says when the next release will be published. It’s better to say : “we will close 250 tickets, doesn’t matter which one” (look in the trac, some tickets are should be closed in 2009 <<< something is wrong !) and only then realese a new version.
    -We don't need a huge improvments, "but be with the time"( for example : HTML5,CSS3 etc., or just to maintain the hole WP, thought bugs etc. )

    Also i must tell,
    -that there isn't any marketing for devs.
    Of course, some WP sites publish arcticles (for users only), but we have to make marketing also for the developers !!! Only they can help us to make WP better.
    -We have less people working on it and everybody (matt, jenne) has to convience devs and just normally people to work on WP in trac. It should be prestige to work for WP, as the same for HTML5 in W3C.

    So my recommendations are :

    -complettly change the release plan (dev cycle). Start thinking hard on a change for pre-production of next WP.

    -make a lot of marketing for devs, some bonus for them. NOT MONEY, but something which matt and jenne must made up. (some small gifts). Just make WP valuable to contribute

    I really like WP and a huge thanks to nacin and other people who make it. But we have to change our habbits and start a new period of WP

    John from Prague,

    I edit the post from p2.

  20. AlexLakes
    Member
    Posted 3 years ago #

    1.) Custom permalinks for custom post types - the ability to set a different permalink structure for each different custom post type. For example, user submitted recipes with the 'recipe' custom post type, might use domain.com/post-id/post-name. But for regular posts and pages, just domain.com/post-name.
    2.) Far futures image naming. This is a dream item. Probably best as a plugin. This would add a hash of the file upload date and timestamp onto the end of each file name of all sizes for that particular image (e.g. christmas-tree100x100-34j2flj5d.jpg), such that no two image file names are *ever* exactly the same, thus allowing use of far-future browser caching for images like on Facebook, and much faster site loads.
    3.) Better testing on installs with properly renamed/moved plugins and wp-content directories. Two issues that seem related to this, a.) the media uploader doesn't find or display previously uploaded images when wanting to add existing images to a new post and b.) attempting to update plugins from the new update tab (beneath the Dashboard) always fails during the update yet these same plugins update properly when doing this from the main Plugins listing page.

    +1 for:
    Core plugin - BBPress
    Better media handling
    Cleaning out the cruft

  21. riskiii
    Member
    Posted 3 years ago #

    I would like to see some UI love extended to the backend widget area. It would be very nice if you could setup multiple columns for the widgets on the right hand side of the page. A large percentage of WordPress themes are now utilizing widget areas, and it is easy to get > 20. This makes it hard to navigate, unless you are fortunate enough to have a 30" screen.

  22. Justin Sainton
    Member
    Posted 3 years ago #

    First, a huge thanks to Jane and all the other team leads and core leaders in WP. Speaking personally, I make a fantastic living developing WordPress projects for clients, so I'm incredibly grateful for all your hard work.

    Huge +1 on Media overhaul. Both in terms of UI and in the available hooks/filters for plugin developers. This is a super interesting proposal for the UI - http://www.markdotto.com/wp-content/uploads/2010/12/wp-uploader-after.png

    Huge +1 on meta table for taxonomy/terms.

  23. Rami Yushuvaev
    Member
    Posted 3 years ago #

    1. login template file
    2. built in site map
    3. bbpress plugin for wordpress
  24. toscho
    Member
    Posted 3 years ago #

    Many good ideas are already mentioned, so I can mostly just repeat.

    • Remove Hello Dolly and Akismet from core.
    • Make the backend more accessible.
    • Move Post revisions into a separate table.
    • Allow IDN-E-Mail-Adresses
    • Export user without posts.
    • More flexible meta data for taxonomies.

    Oh, and a big THANK YOU to all contributors. What you have done so far is just great! :)

  25. Xenaco
    Member
    Posted 3 years ago #

    • Complete Content Scheduling Built In

    WordPress currently provides ability to schedule posts and pages so that they can be published at a later date. I would suggest built in support for unpublishing posts and pages at a specific time and date in the future. This would enable better control over scheduled content.

    There are currently plugins designed for this purpose but their performance is not reliable or consistent. Build in scheduling for unpublishing content would round out WordPress.

  26. Gary Bairead
    Member
    Posted 3 years ago #

    Inbuilt SEO - custom titles and meta descriptions.

    A uniform way of storing this info would make switching themes and plugins easier.

    The SEO Data Transporter makes the technical fix easier, but still doesn't take care of the fact that people switch themes and simply forget about things like these.

  27. Anointed
    Member
    Posted 3 years ago #

    BTW Jane, if I had to pick I think you should have 3.2 be the version that is "All-about-Media". I know it's been something you've wanted for several years. Why not go ahead and focus all effort on a world-class revamp of the media handling in WordPress for the next version after this one?

    ++1

  28. Richard Tape
    Member
    Posted 3 years ago #

    I'd love WordPress to really focus on becoming even more developer-friendly than it already is. By this I mean a really big push on the codex docs with up-to-date, best-practice examples as well as ensuring that all of the old WPMU-related bits and bobs have been updated for MS.

    On top of that, I'd kiss the person (on the lips, if they so desired) who introduced taxonomy meta. I know there are plugins out there, but, as it stands (and as far as I understand it), taxonomies are the only 'limited' content within WP at the moment. Different plugins have implemented different ideas, most use a new db table (which is probably the 'right' thing to do) but, as such, may cause problems if the core team decide to implement this in the future (please, please do).

    There's a million and one 'new features' that every Tom, Dick and Harry will want, but I honestly believe WP should take a breath, consolidate, ensure everything is 'up-to-date'. mrmist's idea of a PHP4 code cleanup is a good example of what I mean. Set yourselves up for adding a plethora of new nicknacks by getting everything you currently have both easy-to-use and up-to-date.

    Other random things that I will +1 to are:

    • Remove inline CSS Styles
    • Making the admin area easy to skin
    • 'built-in' SEO - custom titles, meta descriptions and keywords

    Whatever you folks do will be brilliant, useful and be done with best intentions so I will genuinely be happy with whatever you do (as long as it's Taxonomy Meta. *ahem* ;) )

  29. skromta
    Member
    Posted 3 years ago #

    1. Better support for images in for clients using xmlrpc, for example getting info about the resized images
    2. A complete re-work of the wp iphone client.
  30. Joel Williams
    Member
    Posted 3 years ago #

    I'd like to see:

    • Better/easier language support
    • Easier WPMU/network setup
    • Standardization of terms - i.e most options have an Add new except Themes which has an Install themes and a different navigation option.
    • Better TinyMCE functionality particular around it stripping out things it doesn't like, such as empty divs or iframes.

    Thanks!

Topic Closed

This topic has been closed to new replies.

About this Topic