Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By Anonymous (not verified) on
I've been working with Drupal since 2007 and this is an ongoing pain point so I'm curious – if Wordpress can do it, why can't Drupal?
Comments
Drush. Takes 30 seconds.
Drush. Takes 30 seconds.
Sure but that's for
Sure but that's for developers with command line access. I'm talking about normal site owners.
=-=
everyone has command line access. Perhaps not to the production server in a shared hosting environment but if you were following best practices you wouldn't be updating/upgrading the site directly in production.
lastly, it's not that the Drupal community couldn't develop it. Though, I venture for that developing core/modules auto updating ala wordpress isn't a priority of theirs. The wordpress feature is nice when all goes well. I've witnessed it go horribly wrong with more complex sites.
Re: Sure but that's for
martinjbaker, it's no use. They simply don't get it.
Unfortunately I think you're
Unfortunately I think you're right.
.
I've heard the reason we don't is that it is a security risk to allow a website to update its own codebase. I don't know how WP gets around that or if they even do but that's the reason I've heard.
And you don't have to be a developer to use drush.
No command line access here.
No command line access here.
a. read through release notes
1. Download the update as a tar.gz
2. Upload it using cpanel to a new directory on your site. Extract.
3. Put site in maintenance mode
4. Delete core and vendor directories
5. Copy new core and vendor directories
6. Delete old files in Drupal root directory (usually leaving htaccess alone), copy in new set of files
re-enable site. Check out config/reports
Whole thing takes under a half hour. Granted it's not 30 seconds. If my site was critical with a lot of users I'd have to add in backup steps at the beginning.
Once site is running a few days, delete the tar.gz and extracted files.
Relevant:#2367319: Implement
Relevant:
#2367319: Implement automatic background updates for highly critical security issues
Re: Relevant:#2367319: Implement
Dude said "easy" core updates -- not "automatic".
whats wrong with composer update?
I just run "composer update" from my webroot, how much easier can it get? Maybe consider getting a better host?
Hopefully never.
Hopefully never.
Friends don't let friends overwrite files on their production server. Composer + Git is how it's done.
You are maintaining a complex web application which requires regular security and bug fix updates. Best practices are not optional.
Re: Hopefully never.
Um, there's something called 'back-up' -- which most site-builders (remember them?) are aware of. We certainly don't need lessons on "security! security! security!" -- or at least claims thereof which traditionally have been used -- hey, I've been around for ages -- to suppress thinking about alternative options.
Not impressed.
New Branding for Drupal?
Judging by your response, I guess the _awesome_ new branding for Drupal is:
Hey, gotta face reality. Good luck!