[lug] web site advice needed

karl horlen horlenkarl at yahoo.com
Wed Sep 11 10:22:05 MDT 2013

question for current wordpress users that do updates

when i used to do drupal updates in the past (about 3 years ago probably the last one), iirc i'd go through the process of backing everything up and perhaps making a dup of the site and running the upgrade on the dup in case the update didn't go smoothly.  i think this was b/c it wasn't easy to back the update out once the it ran and changed the db.   i used wordpress a lot less but i think i did similarly.

so with wordpress these days, is it TRULY as simple as go to the admin console and update OR do you / are you supposed to backup and dup your site and run the update on the backup in case of failure.  which is another way of saying if you apply an update to your production instance of wordpress and the update fails, can you SIMPLY back it out on the original instance to get back to square one or are you screwed?

when also combined with the required updates of drupal module and wordpress plugins, updating and updates to either of these cms just always seemed to be a lot more work than i wanted them to be.  iirc, wordpress plugin updating was a little better / more reliable? / less cumbersome than drupal module updates but maybe only b/c most drupal sites require more modules than wordpress does plugins.  that was my experience anyway.  

note that if you only have one site, the maintenance isn't as bad but if you have to maintain a lot of them, it becomes a pita.

any thoughts on how wordpress updates play with wordpress plugin updates and conflicts today greatly appreciated


> From: Michael J. Hammel <mjhammel at graphics-muse.org>
>To: lug at lug.boulder.co.us 
>Sent: Wednesday, September 11, 2013 9:24 AM
>Subject: Re: [lug] web site advice needed
>On Wed, 2013-09-11 at 08:36 -0600, Quentin Hartman wrote:
>> It depends on how you have the permissions setup. The "normal" way
>> these days is to have the installation writeable by the web server
>> user, and it uses http via php to download the update and then
>> installs over itself. That in itself introduces some risk, so the
>> recommended practice is to have stuff locked down during the normal
>> run of things, then relax the permissions only when you want to
>> update.
>Interesting.  I just checked my site and it doesn't look like the old
>ftp requirements are there anymore.  I'll have to give the automated
>update a try, after making appropriate backups of course.  :-)
>Michael J. Hammel                                    Principal Software Engineer
>mjhammel at graphics-muse.org                           http://graphics-muse.org
>Bumper Sticker: Heart Attacks... God's revenge for eating His animal friends.
>Web Page:  http://lug.boulder.co.us
>Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20130911/7bc98a04/attachment-0001.html>

More information about the LUG mailing list