Dear god, please work on a UI for custom fields that's more friendly to the end-user (like Flutter)! Oh benevolent WP gods... Take a hint from Flutter, as buggy as it is, and integrate something like it into core. Make a simple admin settings page that lets us create custom post types and display them for the end user as write panels. That's all WP needs to make it a CMS.
[closed] Version 3.0 Features (186 posts)
-
djquinn
Posted 2 years ago # -
dholowiski
Posted 2 years ago #Wow that's definitely way too much for a single release. I would like to see a focus on the WordPress/WPMU merge since that will bring tons of features to users of the single user, and multi user wordpress platforms.
Also I think a focus on mobile (so the mobile admin page) and ease of use (so the admin bar, the welcome to wordpress guide, and the image editing) is important.
I would like to see the install process for WordPress MU made much easier, since that's not really something a 'normal person can do - but I hope that will come with the merge... -
Dan Cole
Posted 2 years ago #Picking your user name and password during the install process, #10396 would be a nice feature to add.
How To Do Project Development:
I think each version of WordPress could include more improvements if development was more organized. I would like it if the core team asked for feature requests and for feature developers before planning, then created all necessary tickets, assigned developers accordingly, and blessed the tickets. Then at feature freeze, any blessed tickets that have not made it to core due to lack of development get unblessed and all waiting tickets that are blessed get taken care of by committers within a day or two.I think more developers would pitch in with smaller tasks if things were more organized and more concrete. It seams that key features, major bugs, and insignificant details dominate over medium and small features and improvements, leading the later to get pushed back for years. By letting everyone know where every ticket sits in a particular release features, improvements, and bugs can be put in parallel (separate tracks) and "line cutting" will stop being an issue. Which, getting back to the first sentence of this paragraph, will attract more developers.
The amount each developer contributes looks like the "long tail" if it were graphed. The core developers are given too much work and the outer circle of developers have to take their own initiative if they want to contribute anything. Hopefully the next release will have improved development.
It'd be nice if someone with authority went through tickets and requested features and selected some for development, then asked developers outside the inner ring to develop them. This would be a lot more inviting than a free-for-all in trac, because it's hard to know where to start.
p.s. Thanks Jane for getting the development organized for 3.0.
-
Robert Chapin (miqrogroove)
Posted 2 years ago #> free-for-all in trac
Second only to patch punting, I would say the Trac workflow is definitely the next biggest ongoing problem with WordPress.
-
like many others here, I always customize wordpress because I use it as my base CMS. So I'm interested in everything to do with custom post types. Things which I think would be useful are:
- media upload UI redesign and photo albums
- custom content type UI and API
- canonical plugins! and a UI for displaying them
- better help tab and better online documentation
- more template tags
- easy linking to internal content when writing new content
- separate cms distro with canonical CMS plugins installed by default
- better excerpt and thumbnail features
- custom default image sizes (for page headers and magazine style layouts)I also think these features would make the WP experience better:
- built-in "Welcome to WordPress" guide for 1st time admin use
- front end comment moderation
- new default theme
- widget installer
- below post widgets
- better home template (easily allow page and posts together)
- default custom types (microblog, galleries, asides) -
Denis de Bernardy
Posted 2 years ago #I'll add a vote to getting the bug list squashed into oblivion.
-
Niteblade
Posted 2 years ago #Add or change as many features as you want; if WP becomes slower and/or demands more cpu time and ram for it to run properly, then all the "glitter" amounts to a hill of beans.
v3.0 Suggestions:
*****************
- Error log reporting service, also known as a "bug feedback service." When you guys release an update or new code, it looks for errors caused by the introduction of the update or new code and reports results back to you.
- Submission of the mySQL slow queries log & Submission of the mySQL slow queries log parsed with mysqlsla. -- So you guys know which queries are slow and need optimization.Only a certain percentage of people report errors to you; imagine all the information you'd have if "wordpress log reports" were sent to some information parsing site on a daily basis? You'd have semi-instant feedback on your changes to the code without user intervention.
This would help everyone, I believe.
-
laurenebacon
Posted 2 years ago #As someone who works with dozens of WordPress blogs & websites for my clients, I'd say the #1 feature from your list that would make *their* lives much easier is better menu management. Teaching non-technical users how to use sort order is a bit challenging, but moreover it's a feature that they use all the time and that's wildly inefficient at the moment. A drag-and-drop interface on the page management screen would be fabulous.
Other menu-related features that I often hear requests for from my clients include:
- Being able to link to a single page from two different sections of the site;
- Having the option to specify a navigation title that's different from the page title (e.g. for creating shorter menu links); and
- Hiding pages from the navigation from the back-end (i.e. without messing with template files -- we currently use a plugin for this).
Beyond menu management, image editing/cropping would make a lot of my clients really happy, as would easy linking to internal content. As a developer, I see a lot of proposed features in your list that make *me* really excited, but I know if I sent the list to my clients, they'd prioritize these basic functionality pieces.
Hope this is helpful. Thanks for opening this up for discussion!
-
Strategy Web Designs
Posted 2 years ago #The two main features I'd like to see is:
1) Canonical Plugins
2) A much more robust Custom Fields systemCanonical Plugins for me makes it to number one since I imagine it will allow for a lot more functionality that we can rely upon from upgrade to upgrade. It is extremely frustrating to have a new upgrade with old plugins that aren't yet upgraded. Particularly when we are building sites for clients.
In terms of Custom Fields - what I want is the ability to assign different field types for different types of content so that my clients can easily add the appropriate content without having to worry about messing up the code.
Along with this I would like to see as easy a possible a system for including those custom fields into our html/css/javascript code. Perhaps some sort of shortcode integration with html which is built into the backend.
Keep up the good work.
All the best,
Moshe
-
Posted 2 years ago #I would like to add that number three for me is improving the media center section - which means better and easier organization of media (let's say categories and tags) - as well as the ability to have galleries inside of albums.
With that said, the two choices I mentioned in the previous post take priority for me - but I really would like to see all three :).
Be well,
Moshe
-
Blix
Posted 2 years ago #This is probably beyond obvious, but the developers should definitely take a look at the Most Popular Ideas and in particular to the Trust me when I edit HTML idea. A lot of people are asking for a better HTML editor!
Personally I would like WordPress to move more in the direction of a general CMS. The creation of custom pages with or without dynamic content should become easier and better manageable with WordPress.
-
in addition to my first comment
(http://wordpress.org/support/topic/345127/page/2?replies=97#post-1327952)* no more PHP4 support
* folder mu-plugins ?
* which repository for WP 3.0 ? mu ? wp ? -
kilwag
Posted 2 years ago #The current image uploading process is painful. I'd like to see something like the Faster Image Insert plugin built into the core.
Also, the ability to use Slimbox or Lightbox without having to resort to a plugin. (or manually adding the code!)
I am super excited about merging MU!
-
Hannes
Posted 2 years ago #Better support for failed photo uploads would be nice. For example if I'm uploading 50+ photos to a post (to great a photo album) and a few photos aren't uploaded properly I need to upload those few photos again, but then they appear at the end of the album - out of order.
It would be cool if I could retry uploading a particular photo (attachment). Or maybe there is another solution to solve this problem.
-
fleece358
Posted 2 years ago #I really love the speed at which useful relatively bug free features are added to WP. For 3.0 my preference would be a focus on the WPMU merge. I look forward to the possibilities it might bring and would encourage you to look at the additional domains issue others have mentioned.
But if the dev team are looking for core blog features my vote is for, easier internal linking to posts and pages from the post editor (and page editor too I guess). As this would greatly encourage internal linking (which is good practice for user interaction and SEO). I would suggest also adding an option to ignore *internal* pingbacks.
This is one feature I think would make blogging easier and quicker. I think WP dev should not forget this even if we move to more CMS type functionalty.
-
Edified
Posted 2 years ago #I think it's pretty sad that realtime comments is still a theme/pluging realm thing. It seems like it should be well supported and documented in to core along with useful theming tools. People expect it- even facebook does it.
All comment posting should be AJAX. The core should support both polling intervals and long http ("comet" style) on any page with comments.
The core should also support multiple comment forms on the same page without ID conflicts.
Generally wordpress should be writing fewer ids and classes into the page
Cheers for a great release! -
Wisefaq
Posted 2 years ago #Denis-de-Bernardy: I'll add a vote to getting the bug list squashed into oblivion.
Agree with Denis. Get the house in order by squishing the existing bugs. Sure, as a developer, it's great to be working on sexy new features.
I had a look though Trac today, and there plenty of bugs with fixes, but they're been punted to 3.0.
And what about this (re-occuring) issue with wpautop:
Please close as wontfix. Fixing things will break other things and vice-versa. I do not know a single serious developer that wants to touch this.
-
Posted 2 years ago #Also somewhere in the scope of 3.0 to 4.0 we need to overhaul the backend to be a single html 5 web application that just loads dynamic data. Then we can scrap gears and turbo mode and just have standard user mediated resource caching- not to mention realtime updates and no full page loads.
It's where things are headed ;)
-
Stormhierta
Posted 2 years ago #A "choose language" option that essentially works like the plugins. I can search/choose language, it uploads and installs the new language. Perhaps a matching "hook" for the themes to use.
-
DeannaS
Posted 2 years ago #I'm voting for focusing on the merge and domain mapping being a part of the core.
One other thing that I've always thought should be core for WPMU is being able to set defaults on new blogs. I wrote a plugin to do it, but I'd much rather it be in core.
-
Jake Goldman
Posted 2 years ago #There's a lot on my WordPress wish list for the API, but I actually think 3.0 should be almost exclusively focused on WPMU merge. Let's do one big thing, and do it well, particularly since I think WPMU's underpinnings and API calls need some serious polishing.
I'll also go on record saying that a new theme is, in my view, a waste of time. There are plenty of extraordinary themes already out there, and anyone who is serious about their blog isn't going to stick with a stock theme anyhow. Rather than reinvent a wheel that's been "well-invented" elsewhere, I'd suggest a mechanism - during install or setup - to choose from a random series of 20ish of the best themes provided by the community. If we're worried about support for these themes, it's not unreasonable to hold the developers of those themes to a certain set of expectations or threshold of quality to remain on that premium list.
Once the MU merge is finished, I'd say there is a lot of backend / API maturity needed around taxonomies and custom post types before we start worrying about creating a glitzy UI for managing those.
The way custom, non-hierarchical, post taxonomies get handled should be the standard (well, permalink bugs aside). We should be able to define new hierarchical (category-like) taxonomies, and assign taxonomies to pages, and "all the magic" of automatically adding new menu items and new meta boxes appearing on the editing screen should similarly happen.
I envision a similar future for custom post types. Imagine integrating the "add menu" calls with new post type definitions. So that if we define a "news" type, a new menu items (a la Posts or Pages) gets created, with an edit and add new list.
Granted, I speak from the perspective of someone really trying to push the API to the limits (not just a blogger). But I think we really need to hunker down and grow the core API's ability to compete with the likes of Drupal on custom types and taxonomies before we worry about more UI polish, which (with a capable API) can be accomplished just fine with plug-ins anyhow (in most cases).
-
superwillyfoc
Posted 2 years ago #It would be great a 3.0 version with custom post types.
-
I've got a rather simple, yet logical request:
Seperate the content from the design.
Let the theme decide if it really needs all those auto-generated classes and ids. I simply hate it when I've got a good core, a lovely design but spend weeks to clean up and strip out the stuff wordpress spits out.
The pros would be:
- any doctype could be chosen.
- cleaner and smaller code.People will probably kill me for mentioning this... but there are thousands of bloggers that just don't dig "transitional" and rather use xhtml1.1 strict or even html5!
Too much work? No! You allready got a dozen or more functions allowing pre- and post-injection. Streamline them and add a tweak here and ther to allow a boolean. That would be all.
If you need a helping hand to take care of that, contact me. I'm a php/mysql pro with time on my side! I could also clean up the code where needed while I'm at it... just talk to me. I'm not only a friendly person, I'm also "useable". ;)
-
enailor
Posted 2 years ago #For me, there are 3 items of concern.
The first has to do with the WP + WPMU merge. The one bit of functionality I would love to see integrated with the merge is a stable and secure way to properly map domain names. WordPress.com does this so well, I would think this would be an easy thing to add, no longer requiring plugins that may or may not work or conflict with other plugins.
The second would be more CMS functionality, especially in terms of user levels and permissions. I know there are plugins that mimic this, but these can cause problems with other plugins and can be complicated. With the newer profile items, it would be nice to also be able to assign differing permissions as needed (or by default) per user.
Finally, my only other request is better documentation on the new features being added. Sometimes we have to search the web to find out information, particularly detailed information, on new features. This information can be hit or miss. In my opinion, these features should be very well documented for the community within the WordPress codex.
Above all, thank you WP developers for all you do in providing an awesome software package that really can do just about anything!
-
gargoyle3113
Posted 2 years ago #I would love to see:
- updated photo albums features since many of my clients use these a LOT. The ability to pull meta-data from uploaded images would be even better!
- New default theme
- Easy linking to internal content when writing new content in editor
-
Lloyd Budd
Posted 2 years ago #It's time for "Email me replies to comments" to be in core.
-
avenueverve
Posted 2 years ago #Definitely would like to see a robust custom fields admin UI.
We plan to release one in early 2010 that we've developed for clients as the existing plugins did not do what we wanted to do. Our plugin has an admin interface that allows for custom metaboxes, each configurable with any number of custom fields, including image and file uploads.
The custom fields are stored in postmeta and can be accessed and displayed using the current custom fields functions.
Anyway, stay tuned. We are hoping this code could helpful when you consider improvements to the custom fields admin UI.
-
Joel
Posted 2 years ago #Predicting massive growth of the WP community once the following are implemented:
- auto-taxonomy UI (hierarchical and flat custom taxonomies
- custom content type UI and API
Developers would swarm to WordPress if this functionality was available for their projects.
-
westonruter
Posted 2 years ago #I'd love to see script concatenation, minification, and optimization available for all scripts, not just those included in the distro.
I've built a plugin that does this using Google's Closure Compiler, but I think it is important that this not be in a plugin but rather be in core so that WordPress can be “fast by default”:
http://wordpress.org/extend/plugins/optimize-scripts/ -
Stephanie Leary
Posted 2 years ago #Better menu management would be great. Drag-and-drop reordering for sure -- the "janky" page numbering has been with us long enough -- and being able to exclude certain pages from the menu. (Easy way to achieve this: make the My Page Order and Exclude Pages plugins core.)
Along with that, private pages really need to be fixed. It's self-evident to me that logged-in users who have permission to see private pages should be able to see them in menus, but private pages don't appear no matter who you are. Users who can edit private pages should also be able to choose them as parents, creating a hierarchy of private stuff, but that's broken too. Fixing those two bugs would go a long way toward making members-only content work.
Topic Closed
This topic has been closed to new replies.
