Opened 16 years ago
Last modified 7 years ago
#16216 new enhancement
Hide core updater if running an svn checkout
| Reported by: | johnjamesjacoby | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Upgrade/Install | Version: | |
| Severity: | normal | Keywords: | has-patch needs-refresh |
| Cc: | Focuses: | ui |
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 (23)
#1
@
16 years ago
- Component General → Upgrade/Install
- Keywords 3.2-early added
- Milestone Awaiting Review → Future Release
#2
@
15 years ago
- Keywords 3.2-early removed
- Milestone Future Release → 3.2
What koop said.
Also, we should do the same per plugin/theme at some point.
#4
@
15 years ago
- Keywords ui-feedback added
I'd throw an ABSPATH in there at least. Someone else might like to weigh in on the wording.
#6
@
15 years ago
Wouldn't is_directory() be more appropriate?
Yeah, I suppose it would, have changed it.
#10
@
15 years ago
There we go. I thought about customising the string for SVN and Git, but it seems like overkill.
#11
follow-up:
↓ 12
@
15 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.
#12
in reply to: ↑ 11
@
15 years ago
Also, please don't replace patches -- just upload new ones.
Okay.
#13
@
15 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..
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
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.