Suggest agenda items for January 21, 201…

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

steph 10:35 pm on January 15, 2010

There needs to be a decision on how private content should work. There’s a cluster of tickets involving get_posts/get_pages, private post queries, and performance.

#4711 is the root of the problem: private posts aren’t included in get_posts or get_pages.

#4711 has two major side effects. #8592:
private pages aren’t available as parents in the edit dropdown, and #6939: private pages aren’t shown in menus even if the user is logged in and has permission to read them.

There are two proposed solutions: making private posts accessible only from the adminadmin (and super admin) screens (#11697), and allowing admins to disable the feature altogether to get around the performance issues (#11375). (Personally, I’m not a fan of either. I’d rather see #4711 fixed.)

Comments on private posts/pages are also problematic. They show up in comment feeds (#11695) and the recent comment list on the Dashboard (#9144) regardless of the current user’s read_private* capabilities.

I’m sure Denis will chime in with anything I’ve missed, as he’s been heavily involved in all the tickets.
TobiasBg 10:17 am on January 16, 2010
Just so that it doesn’t get lost:
- classix: apply of the coding styleguides on all the code, hakre
as it was postponed
- hakre 7:27 pm on January 18, 2010
  
  Thanks. I put a blogpost online regarding “WordPress Coding Standards – How to go on?” and to gather some feedback previous to the meeting this week. Open to everyone who want’s to throw in some thoughts about the issue.
Mark Jaquith 2:53 am on January 18, 2010

• Discuss options for pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/theme repository disputes. Right now, plugin/theme authors don’t have a recourse when something is suspended or rejected. Perhaps a forum only for plugin/theme devs to discuss administrative issues?
Shane 6:29 am on January 18, 2010

jQuery 1.4 came out during this cycle. If we add it now before we get to far we can try to remove all the bugs, but I suggest holding it off till. Twitter is starting to get the ‘How to use jQuery 1.4 with WordPress’. No idea if any errors will happen, but what is going to be the official stance.

I can’t make it.. again.. so you’ll have to just get my input from here.
- wpmuguru 5:16 pm on January 27, 2010
  
  I believe 1.4 is in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. already.
  
  Nevermind / off by a week.
Pingback: jQuery 1.4 and WordPress 3.0 | the rabbit hole
arena 1:51 pm on January 22, 2010
About “WordPress Coding StandardsWordPress Coding Standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook.
May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards. – How to go on?”,
Has the way of building adminadmin (and super admin) pages been adressed ?
This is more a code architecture subject than a coding standards subject.
In standard WordPress, for admin, if you take a look at how code is organized, and try to follow the building of an admin page from top to bottom :
- there are a lot of files to open,
- some items are registered (scripts and styles) out of context (script-loader.php should only load generic js and css) ,
- some files are loading code out of context (e.g. wp-admin/includes/template.php),
- some code is duplicated n times for each admin page (e.g. the ‘action | action …’ code),
- etc …
I personnally tried to solve this in my pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party MailPress (requires PHP5 but this code architecture can be implemented for PHP4 & PHP5):
- Admin pages are classified as single or list pages.
- list page is an extension of single page, of course.
- All admin pages are defined in a class called MP_AdminPage extending a single or a list class.
As WordPress admin is going bigger and bigger, isn’t it time to reorganize this part of WP, to gain in
- code readability,
- less ressources required
- more code being re used by plugins,
- …
Peter Westwood 6:24 pm on January 27, 2010

I don’t think a big re-organisation will help anyone.

It is just a lot of work for not a lot of improvement.

We are gradually trying to remove code duplication and make the code more re-usable. The work that has been done on custom post types for 3.0 already removes a fair amount of code duplication and make it easier to maintain.
kelebek 2:22 am on April 3, 2010

I believe 1.4 is in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. already.

Comments are closed.

Welcome!

Communication

Share this: