#25678 closed defect (bug) (fixed)
Automatic Update Email Error
| Reported by: | markmcwilliams | Owned by: | nacin |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.7 |
| Component: | Upgrade/Install | Version: | 3.7 |
| Severity: | normal | Keywords: | has-patch commit |
| Cc: | Focuses: |
Description
FYI, absolutely loving the automatic updates, and emails saying it's been done! :)
The latest email I received though, has a little error in it, saying that WordPress 3.8.1 was available (see the attached image which may help better explain). I wondered if I'd missed something, lol!
If I can find the problem, I'll get a patch submitted if nobody does it quicker than me!
Attachments (3)
Change History (12)
#2
follow-up:
↓ 3
@
13 years ago
- Milestone Awaiting Review → 3.7
Seems that only = '3.8.1' need to be removed.
#3
in reply to: ↑ 2
@
13 years ago
Replying to markoheijnen:
Seems that only = '3.8.1' need to be removed.
I don't think it's that simple; however, I have attached a patch reflecting your suggestion.
Unfortunately though, I'm unsure how to test this feature (perhaps I've missed a blog post explaining this), and if it's possible to force an email when a background update is made, so please forgive me!
#4
follow-up:
↓ 5
@
13 years ago
- Keywords has-patch commit added
Both of those lines are test code. See 25678.2.diff.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Looking back, I can see the reference to 3.8.1 was introduced in [25873]. I feel this should be a variable, but I'm unsure if one exists or not? To me, looking at the email, it's just confusing, especially someone who could be new to WordPress.