Posted 3 years ago #
@DJAllyn - You could try bbPress for your forum?
@hpguru - I must make it my New Years Resolution to read better! I know what you mean though. This one would do the job, but having never used it I'm not sure if it would force a user to answer a question even if they've registered and are logged in.
@demetris - Sorry, I missed the link to your ordered list? ;p
Posted 3 years ago #
One thing I'd really like to see is a better back-end. Theme-able as well. My settings and tools tab are full of links from plugins. I'd really like them to be listed alphabetically rather than randomly by which plugins are installed first or however it does it now.
I really like plugin authors that put a link next to the activate/deactivate link for the settings/options. I'd like to make this mandatory for plugins that do have settings/options. Many times when I activate a new plugin I have to go on a Snark Hunt to find out where the settings and even the viewing pages are.
Would it be possible to have an API key for Akismet sent automatically for each install rather than forcing people to register at the website?
All minor changes but huge frustrations.
Posted 3 years ago #
@youngmicroserf - pulling data from multiple blogs? Yep, easier ways to do that in mu, currently via plugins.
Posted 3 years ago #
@lokrin2000: I agree that retrieval of API key for Akismet could be simplified - e.g. enter email and get your key (if you have one) or new one (if you do not have it).
Posted 3 years ago #
I have a saying. There's a tiny step from "feature rich" to "bloated". Simplify it, make it fastloading, implement more plugins (the ones that are the most used), remove features that are not used.
Keep the admin theme, don't change it (maybe small tweaks). Don't change what people are used to.
Posted 3 years ago #
Suggestion for now: set up an "i want" list on UserVoice!
Posted 3 years ago #
How about having an Incoming Links dashboard widget that actually works?
Releasing 2.9 with it not working was a bit rubbish, if you keep it in 3.0 and it still doesn't work it'll look as if you don't give a damn.
WordPress 3.0 Merge of WP and WPMU Christmas wishlist
A. Implementation of the top-requested feature in your poll way back - native photo gallery. My wish - set up with ability to enable or disable sharing album with other users of the installation so the latter can use photo in posts
B. Enable or disable multiple blogging system.
1. If some users would like to keep their current single blog set-up and hosting plan, there'll be no ripples.
2. If users choose to go multiple blogs with or without domain mapping, and/or with BuddyPress and bbPress - Highlight requirements or realities of multiple blogs in WP 3.0 installation in readme.txt and Codex, especially with respective Hosting Plans.
- Need to build a list of WPMU/WP 3.0 tested Hosting Providers - multiple blogs require higher bandwith and hard disk space among many others.
- installation of WPMU with GoDaddy requires upgrade to the Deluxe Hosting plan, purchase of a dedicated IP address, use PHP5 (which is good), adding a wildcard record to A (Host)for new blogs, among others
- Never heard of WPMU installed with Yahoo hosting.
- some more to follow
Posted 3 years ago #
I believe there was talk of this a for 2.9, but a better easier to manage in post/page gallery for pictures would be great. With features like drag and drop reordering and an easier way add photos to existing galleries would be excellent! I can make it work for my means but my clients find it rather cumbersome to use at times.
Posted 3 years ago #
A problem that has hovered over WPMU like a bad smell for years but which has never been satisfactorily resolved is MULTIPLE DOMAINS. Wave after wave of new user, upon discovering MU, have asked what seems to be a natural question: "How can I give each of my blogs their own domain, but still manage them from one central installation?" and, time after time, they have been told "That isn't what MU is for!".
That is true, MU was always been geared towards large organisations such as universities who want to offer blogs to their students, all under one domain, but that fact has not stopped tens of thousands of users hoping that it might be a solution to the ridiculous problem of having to manage and update multiple installations of WP.
Now that WP and MU are merging, that shining ideal, of using just one installation, is going to occur to even more people and the forums will be awash with desperate pleas for a solution that works. At the moment, they are forced to wade through an endless maze of ancient forum threads and contradictory blog posts, pointing to an array of half-working plugins and core hacks that haven't worked since 2.3.
Rather than continuing to bat these requests into the undergrowth, official multiple domains capability should be added to the core as soon as possible, ideally at the same time as the MU merge. The number of people using WP is increasing but it would also promote growth if it was easier for each user to run multiple WP sites (with the side-benefit that easier upgrading will decrease the number of insecure WP installations).
If Drupal and practically every other CMS can do it, surely WP should be able too?
Posted 3 years ago #
In 2010 default theme:
1. option for adding code for addsense, etc. (without the need for a plugin for plugins are generally not kept uptodate.).
2. option for two columns sidebar (without plugins).
I am really impressed with wp!
Posted 3 years ago #
Posted 3 years ago #
@donnacha: Hear, hear!
I, for one, have actually converted a few no-longer-in-use WordPress sites to static HTML just because I got tired of maintaining yet another WP installation just so I can continue allowing comments on old posts. I'd love to keep all this functionality alive but not at the cost of adding another installation to maintain. True multi-domain support in WordPress is long overdue.
Posted 3 years ago #
Getting the wp-login.php under theme will be of great help to all those who use WP as a CMS.
+1 for Multiple domain support in WP core (post merger with MU)
Posted 3 years ago #
oauth for Subscriber role using facebook or twitter credentials
so in short: social features by connecting people and making one's weblog as important as platform as twitter or facebook by connecting those platforms
Posted 3 years ago #
I would love to see customizable registration form in wordpress 3.0 where admins would be able to define whether new users can choose their own password while registering or not. Also give admins the ability to add custom registration fields and the data should be editable through the profile page. I know that this can be done using the register plus plugin but I think it's so important and necessary that it should be included in core, besides this plugin has some major bugs, for example the password reset function doesn't work any more for me once the plugin is active.
Posted 3 years ago #
BY FAR my #1 want is to have "Custom content type UI and API" which of course imply flexible URL routing for custom content types.
My #2 would be "Custom fields UI (possibly to be registered by themes or plugins for something to be displayed."
I'm working on a plugin for #1 and might be able to also implement #2. If inclusion of #1 and #2 would be based on having someone to do the work please ask. I feel strongly it will have most value once its in the core and theme and plugin developers can leverage said functionality.
Posted 3 years ago #
1. I have over 1100 posts in my blog. I would like a back end graphical interface that would allow me to organize them so I could determine whether there are better ways to present them thematically for readers. At present, my only method is to print them out and move paper around on a huge table.
2. I would like to be able to explore a new theme's back end and try it out without changing it for readers until I am ready.
@Demetris: I'm sorry you found the list frivolous. It's actually not my own list, it's the list that was generated at the core commit team meetup when we started talking about the roadmap. We wanted to make a list of all the things people have discussed doing over the next few releases so we'd be able to prioritize them in context before we tried to pick things for specific releases.
As for not making it an ordered/unordered list... I didn't want my post to be a million screens long, and since it was really just a braindump, I don't see it the same way as you, I guess. Putting them in a bulleted list implies a hierarchy that a sentence format does not, and my intent was to avoid introducing an implicit/biased ranking of features, so that people could jump right into their own opinions. I've never been offended by the way someone chooses to style their own text (except maybe all caps), as long as the words themselves are not insulting.
Hi,
thanks for your post, Jane!
I would definitely like the "Canonical Plugins" be introduced more with WP 3.0. This would an advantage that all other possible features discussed here could benefit from: They could be developed as a Canonical Plugin (if that is possible already, without further hooks, filters or other stuff).
This would be a great advantage in the future, because features that do not get voted to be worked on for a specific release then, could in parallel be worked on as a Canonical Plugin.
And a question regarding your post: You talk about "features" and "feature requests". How shall "enhancements" (i.e. small things like an additional hook/filter or function parameter, or ...) be handled? Do they also have to be agreed upon before the dev cycle?
Thanks and best wishes!
Tobias
Posted 3 years ago #
1. Custom Fields/Field types with an easy-to-use back end - currently you can have custom fields but it is too confusing for me to ask my clients to use it. A good example of what i mean is, a competitor, Brandon Kelly's FieldFrame for Expression Engine.
2. Easy to customize wysiwyg editor (so I can create custom styles that my client can then choose from a drop down)
3. Skeleton Default theme
4. Have the docs for the template tags easily findable (hard to miss) from http://codex.wordpress.org/Main_Page.
Thanks for the fantastic product!
* my first concern is about wp and wpµ merge and impact on ressources and performances (wp is going bigger and bigger...).
* my second choice is : fix the bugs first !
* my third choice is : An agenda sticking to this simple principles :
_ Three 'new features' release or version per year (april, september, december 15th), stick to these dates and postpone unstable new features.
_ all other intermediate releases for bug fixes only
Posted 3 years ago #
Suggestions:
define('EMPTY_TRASH_DAYS', 30 ); from admin settings pannel.define('WP_POST_REVISIONS', 3); from admin settings pannel.
Posted 3 years ago #
I think that the whole WordPress should be conceived as a framework. I love the flexibility of Drupal (given mainly by the CCK and Views contributed modules) but it has a high learning curve and some stuff is unnecessarily complex, so I would like to see more of the good stuff implemented under the easiness on WordPress (it can save the necessity of a lot of plugins, which creates custom types in unrelated ways), like making everything made as part of an preconceived API instead of creating too much features for each one. Like, by now the pages, posts and attachments are all "content types" but seems that each one is from an of independent nature. I think they all must share a same API so one can customize (or delete) them and create new stuff with all their fields from scratch (instead of just creating an API to make content types in a "post" sense).
Also, the fields must be conceived in a more "generic" way; I don't think is necessary to have a pre-built "post thumbnail" field to add to custom content types because that's too specific, but rather a generic "upload file" field that one can customize to have the same functions of the post thumbnail field or other potential uses (podcasting, etc.). Obviously, it should still appear as a "post thumbnail" field in the post content type with the default install, but you may get the idea.
Posted 3 years ago #
My only feature request is to make sure that the WP Mu -> WP conversion is smooth and that the new default is well tested and well coded before release. These are two very major additions to the software and should be given a much higher priority for development than anything else IMO.
Donnacha's suggestion sounds good too, although I suspect that might be a little too complex for 3.0.
Posted 3 years ago #
I'd love to see custom write panels to expand on the CMS ability of WP. Similar to the Flutter plugin, but factored into the core and without the bugs.
Posted 3 years ago #
Definitely a re-worked registration system. - Guys, we should really stop sending passwords in plain-text! And I double the thoughts for onboard spam-registration prevention. In other words, a WordPress 3.0 needs an overhaul of our registration system (secure and plugable).
Here are two example tickets that address these issues: 2870 (open since 2006 or WP 2.0.4) and 10006.
Another useful feature would be a mobile theme (not only for iphones, but also for other platform like e.g. Android) in the backend.
Posted 3 years ago #
I agree with donnacha. It would be great to see multiple domain support from the 3.0 merge. I currently have 3 domains I manage and it's a pain to maintain them all separately.
Now on to the requests.
1. Categories for "Pages".
2. Give an option for removal of the category base from the URL. Currently using the plugin "WP No Category Base".
3. Some sort of Loop Wizard would be nice. I use WordPress for a CMS and not for a blog. My home pages are always customized. Finding _quality_ themes with custom loops built-in is hard to do. Having a Wizard-like menu system to build a custom loop (and then copy/paste code to theme) would be a great addition.
Domain mapping - Donncha's WordPress MU Domain Mapping has been around for a while. Current version supports domain mapping for both subdomain and subdirectory WPMU installations. As for what can be done with your WPMU installation, you can be only limited by your imagination and I would say, by your server.
Posted 3 years ago #
Oh, I hope it'll be have downgrade for wordpress . If lastest version have some bug & problem , we can downgrade wordpress to previous version . I'm 60th comment , hihi
This topic has been closed to new replies.
