Post By Email weekly update

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.

This week, I finally released the Post By Email 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 into the official repository, which inspired me to do a lot of incidental cleanup (readme files, test instructions, etc.).

I finished updating the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. deprecation patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. for 3.7 — it’s in the plugin repo and will be submitted back to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. once my mentors get a chance to review it. (Comments and feedback welcome!)

I also powered through the remaining infrastructure tasks. The latest version is 0.9.9 (look how close that is to 1.0! SO CLOSE) and includes the following:

Improved error and status logging
Scheduled mail checks via wp_cron
Prettified settings page (with stuff like consistent date/time display)
Autoloading of Horde library files (HT to ryanmccue for the example)

If you happen to have access to an unsecured POP3 mail server and want to test this and see what breaks, I’d love to hear about it. (Be sure to patch Core with the deprecation patch first to avoid weird behavior.)

The 1.0 release will include IMAP and SSLSSL Secure Sockets Layer. Provides a secure means of sending data over the internet. Used for authenticated and private actions., at which point I will start requesting betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. testers in earnest.

I just spent the last few hours tracking down 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. in my clear_log function, which turned out to be caused by the Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. validation function being triggered when an AJAX function (called from the settings page, but not with a form submit) called update_option. I worked around that, but haven’t yet figured out why it’s happening at all — any insights would be appreciated.

#post-by-email, #weekly-update

pescadito01 7:51 am on August 30, 2013

Nice!
Can i apply as 1.0 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. tester?
Best Regards, Pescadito
Konstantin Kovshenin 9:14 am on August 30, 2013
Oh hey there!

The thing is that once you register_setting with a sanitize_callback argument, WordPress adds a filter on sanitize_option_{$option_name} which runs every time an option is updated, via an adminadmin (and super admin) page, or front end, or XML-RPC, etc., or as in your case – an AJAX handler. This means that your post_by_email_validate will run every time update_option runs, regardless of the context.

Your hack during the validate function:
```
$options['log'] = $input['log'];
```
I haven’t tested it, but it looks like somebody can easily write anything to that log by hi-jacking the settings form. I may be wrong though.. In any case, taking the log out of the main options array may be a better idea, since you don’t want to autoload it on every request anyway – logs can get big over time. Also note that logging in that fashion can cause some race conditions because of the way the object cache works with options.

I don’t know what your end goal with logging is, but I’d suggest looking at PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher’s error_log which can easily be written to wp-content/debug.log in WordPress.

Hope that helps!
- Kat Hagan 4:46 pm on August 30, 2013
  
  That’s exactly what I was missing, thanks!!! I knew the hack was terrible but I honestly just needed to check something in last night so I could write this post. 😛
  
  The log originally started out as a separate option, but George recommended adding it in to the main settings array in an earlier code review. Maybe he can weigh in on this?
  
  The log is meant to be user-facing (i.e. not just for debugging) — it’s a record of any errors that occurred but also status messages (like “Got 3 emails” or “No emails found” or whatever). So I’m not sure using error_log for that makes sense.
  - George Stephanis 11:14 pm on August 30, 2013
    
    Now I’m rethinking myself. As you’re not going to load the log on 99%+ of page views, it’d probably be better as a seperate option with autoload turned off. Save some bandwidth between the db server and wp, as well as avoid loading it all into memory.
Jen Mylo 2:26 pm on August 30, 2013

The deprecation patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. should be put on a tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. for community review rather than in the 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 repo (which I see isn’t really “the plugin repo” but your own githubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repo where your’e doing the work). Can you put it on a trac ticket? Thanks.
- Kat Hagan 4:41 pm on August 30, 2013
  
  Hi Jen, I didn’t really want to put the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. back into TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. until Justin and George got a chance to look it over, as I’m pretty sure there are changes that will need to be made. I’m hoping they’ll have a chance to review before our next meeting on Tuesday.
  
  The GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repo is actually a mirror of both the plugin repo and the GSoC repo, so, yes, it’s in the 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 repo too. 🙂

Comments are closed.

Welcome!

Communication

Share this: