Title: Problem after 2.5.0 update
Last modified: August 30, 2016

---

# Problem after 2.5.0 update

 *  Resolved [davispe](https://wordpress.org/support/users/davispe/)
 * (@davispe)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/problem-after-250-update/)
 * After updating to 2.5.0 the emails, custom fields and options tabs are blank.
   I’ve tried deactivating all other plugins etc but nothing changed. Any ideas?
 * [https://wordpress.org/plugins/order-tracking/](https://wordpress.org/plugins/order-tracking/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Contributor [etoilewebdesign](https://wordpress.org/support/users/etoilewebdesign/)
 * (@etoilewebdesign)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/problem-after-250-update/#post-6690657)
 * Hi Davispe,
 * Thanks for bringing this to our attention. It looks like something was overlooked
   in our latest update, which brought about a huge overhaul to the email system.
   For now, it may be best for you to revert to a previous version.
 * We will issue an updated release as soon as possible, so keep an eye out.
 * Sorry if you’ve experienced difficulties,
 * EWD
 *  [pareet](https://wordpress.org/support/users/pareet/)
 * (@pareet)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/problem-after-250-update/#post-6690794)
 * Hi, wondering why did you switch from native SMTP e-mailing to using the pluggable
   wp_mail function? It was working beautiful earlier!
 * I would much rather revert to earlier version. How can I do that?
 * Also, the email template now sends everything in one paragraph without using 
   any line breaks. This really makes the emails look ugly..can you please have 
   a look?
 *  [Jason Hendriks](https://wordpress.org/support/users/jasonhendriks/)
 * (@jasonhendriks)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/problem-after-250-update/#post-6690795)
 * **wp_mail** is the standard mail function for all wordpress plugins.
 * Now you can configure SMTP system-wide with a single [smtp plugin](https://wordpress.org/plugins/postman-smtp/).
   _Order Tracking Plugin_ doesn’t have to keep up with new SMTP extensions like
   OAuth 2.0.
 * And if you run plugins that use the standard wp mail filters (like an email log):
    - wp_mail_from
    - wp_mail_from_name
    - wp_mail_content_type
    - wp_mail_charset
 * now they will be compatible with this plugin.
 * Isn’t that better?
 *  [pareet](https://wordpress.org/support/users/pareet/)
 * (@pareet)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/problem-after-250-update/#post-6690796)
 * Noted, thanks.
 * Please look at the email formatting though.
 *  Plugin Author [Rustaurius](https://wordpress.org/support/users/rustaurius/)
 * (@rustaurius)
 * [10 years, 9 months ago](https://wordpress.org/support/topic/problem-after-250-update/#post-6690842)
 * Hi all,
 * You can revert back with the version prior to this update here: [https://downloads.wordpress.org/plugin/order-tracking.2.4.9.zip](https://downloads.wordpress.org/plugin/order-tracking.2.4.9.zip)
 * As for the breaklines, you can insert </br> to create them.
 * Best regards,

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Problem after 2.5.0 update’ is closed to new replies.

 * ![](https://ps.w.org/order-tracking/assets/icon-128x128.png?rev=1803956)
 * [Order Tracking - WordPress Status Tracking Plugin](https://wordpress.org/plugins/order-tracking/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/order-tracking/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/order-tracking/)
 * [Active Topics](https://wordpress.org/support/plugin/order-tracking/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/order-tracking/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/order-tracking/reviews/)

 * 5 replies
 * 5 participants
 * Last reply from: [Rustaurius](https://wordpress.org/support/users/rustaurius/)
 * Last activity: [10 years, 9 months ago](https://wordpress.org/support/topic/problem-after-250-update/#post-6690842)
 * Status: resolved