Opened 2 years ago
Last modified 2 years ago
#16216 new enhancement
Hide core updater if running an svn checkout
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Upgrade/Install | Version: | |
| Severity: | normal | Keywords: | has-patch ui-feedback |
| Cc: |
Description
The logic with this patch is if you are running an svn checkout, do not display the core updater code and instead display a reminder.
Attachments (5)
Change History (20)
johnjamesjacoby — 2 years ago
comment:1
koopersmith — 2 years ago
- Component changed from General to Upgrade/Install
- Keywords 3.2-early added
- Milestone changed from Awaiting Review to Future Release
- Keywords 3.2-early removed
- Milestone changed from Future Release to 3.2
What koop said.
Also, we should do the same per plugin/theme at some point.
solarissmoke — 2 years ago
comment:3
solarissmoke — 2 years ago
- Keywords has-patch added
How does this do for a simple warning?
- Keywords ui-feedback added
I'd throw an ABSPATH in there at least. Someone else might like to weigh in on the wording.
comment:6
solarissmoke — 2 years ago
Wouldn't is_directory() be more appropriate?
Yeah, I suppose it would, have changed it.
comment:8
solarissmoke — 2 years ago
Everyone's allowed to make that mistake once, right? :P
comment:10
solarissmoke — 2 years ago
There we go. I thought about customising the string for SVN and Git, but it seems like overkill.
comment:11
follow-up:
↓ 12
nacin — 2 years ago
If we are to offer Git checkout detection, which I'm not inclined to do, I'd rather not combine the string.
Also, let's spell out "Subversion". My take: <strong>Warning:</strong> It appears that you are running Subversion checkout of WordPress. You may wish to keep WordPress up to date using Subversion instead.
Also, please don't replace patches -- just upload new ones.
solarissmoke — 2 years ago
comment:12
in reply to:
↑ 11
solarissmoke — 2 years ago
Also, please don't replace patches -- just upload new ones.
Okay.
comment:13
dd32 — 2 years ago
If we are to offer Git checkout detection, which I'm not inclined to do
I agree here, Support the VCS we're using, we can't support every single VCS out there..
comment:14
dd32 — 2 years ago
attachment warning.jpg added
- demo of 16216.3.diff for UI feedback.

Having some sort of svn-specific behavior is definitely something we should do, but disabling the core updater entirely seems error prone. It should just be a warning.