Well, I guess that headline will get some attention.
But seriously, DO NOT attempt to update to 6.0 unless you are working on a cloned test server because you will almost certainly have issues. In fact I wouldn't even attempt an upgrade until V6 has been around for a while and gone through at least one upgrade itself, to iron out the major upgrade headaches. The system is just too complex to expect it to go smoothly at the outset.
I've always been able to upgrade easily and seamlessly within 5.X but this time even though I followed the new instructions perfectly it failed with unrecoverable errors, and I was not able to restore the old version and DB for unknown reasons (I had never attempted a DB restore before) - I got a really weird error.
See my previous post which so far has no replies - not surprising - it's a cryptic error problem which few can really decipher, and that's the whole problem here.
We are using Drupal because it supposedly obviates the need to know a lot about code and system administration crap. But the update process needs to be much more automated. It's really an extraordinary pain in the neck and fraught with difficulties - not for the faint of heart. Great strides have been made to simplify site admin and theming, for example, but this is the next big hurdle.
Just for example:
We are instructed to turn off all modules before upgrading. Well if you have a multi-site setup using a common code base and separate DBs it's a ton of work just to do that AND remember all the modules you had enabled for each site. You have to make several passes through the module list to turn them all off because of dependencies, and the same when re-enabling them all later. That process should be automated.
A script ought to see what old modules you had before, tell you that they aren't compatible with the new version and disable/uninstall them for you.
An install script should be able to backup your old files and install the new ones without you having to do it manually - just pick the appropriate file locations when asked.
Most of us can handle simple stuff like Unix commands and negotiating file structures and the like, but few can deal with MySQL databases beyond setting one up. So if I get a DB error when upgrading my site I'm absolutely lost.
One last suggestion - the video tutorials are cute but not very useful as they are often ad hoc, off the cuff attempts to guide us through complex steps and it's hard to follow them (not to mention often some really awful English that's hard to understand). There's no way to provide comments/feedback on the videos for improvement, as there is with a written tutorial (no one's going to redo a whole video if there are some errors). Stick with ordinary written tutorials please and add screen shots for visual clarity.
Just my 2 cents... Jeff
Comments
HEY! HEEEEY! PAY ATTENTION TO MEEEEE!
It will be many months before I can up to Drupal 6. It will cost the developer team I lead a few weeks of work. It's so unfair! Why does not Drupal automatically update its modules? Those evil core coders do not pay attention to MY neeeeeeeeeeeds!
(subject courtesy of Merlin)
--
The news is Now Public | Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile. |
--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
I'm sure...
... that there's a good reason that Drupal doesn't have an 'auto-update' or 'auto-disable' functionality for all modules.... it involves sites eating themselves during the process because they're dependant in some way on a module being enabled.
Never...
Never do such an upgrade *without* first doing it on a copy of your site. Never, never, never. This is standard practice. Copies are expendable.
Your previous post seems to have gotten at least one response with valid advice... importing another copy of the rows will only result in 'duplicate key' errors. Did you choose the 'Add DROP TABLE' statements when doing a database dump with PHPMyAdmin? If not, the old tables will not be deleted when importing over the old data, and so you'll have to do it manually if you don't want duplicate rows.
While I haven't updated any D5.x sites to 6 yet, if the process is anything like other CMSs I've used, upgrading between major releases of the software is not something to be taken lightly, and the difficulty of upgrading is directly proportionate to the complexity of the site being upgraded.
Always use a test site
"DO NOT attempt to update to 6.0 unless you are working on a cloned test server"
You start out good. That's good advice. Don't try a major upgrade without a test site and a good backup.
As for the rest, well, yeah, the installer could use work. It got better in 6.x and, if people step up to help, it will get even better in 7.x. Multi site is always going to be hard. That's why I don't use it for seperate sites, only for stuff like making a dev version.
Keep in mind that people donated their time to make those videos. If you don't find them helpful, fine, but others do. Once you've gotten your site up and running, perhaps you can do a proper video on how to upgrade when using multi site. Jump in and help where you can. That's how Drupal improves with each iteration.
Michelle
--------------------------------------
See my Drupal articles and tutorials or come check out life in the Coulee Region.
-----
Shell Multimedia - My sporadically updated mostly Drupal blog.
Does this accomplish anything?
Hello, Jeff,
I understand that you are frustrated. However, there are some statements in here that are not constructive -- these statements diminish the possibility that people will take your thoughts seriously.
For example: "not to mention often some really awful English that's hard to understand" -- Drupal is an international community. Many people within the community speak multiple languages, of which English is one.
Maintaining a web site takes work. While many things can be automated, and many of these aspects are automated, it still requires work to get things done. It sounds like you have some specific needs. To put these needs in a more constructive context, you could write a spec that outlined them, along with some ideas on how to implement a solution. This would be a starting point for getting these needs addressed -- possibly people within the community would have similar needs, and a solution could be reached via collaboration, or it could be that you would need to hire a developer.
With that said, there have been some pretty extensive conversations on these issues on the dev list stretching back several years. Googling through the archives would shed some additional light on the issue.
Cheers,
Bill
-------
http://www.funnymonkey.com
Tools for Teachers
-------
http://www.funnymonkey.com
Click. Connect. Learn.
Using Drupal in Education
Upgrade to latest 5.x before D6
For what it's worth, I tried upgrading a Drupal 5.x database (on my test server) to D6, and I got errors. After playing around for an hour or so, I found out that I needed to upgrade the test server (I think it was 5.2, 5.3, something like that) to the latest 5.x version of Drupal (5.7), and then Drupal 6 would update the database just fine.
5.7 to 6.0 upgrade
I had a really terrible time with the "upgrade" to 6.0. Everything showed up as an error.
Unlike every other upgrade I have done with Drupal, this was, to me, a disaster. Nothing worked right.
And, the steps to an upgrade seemed much more difficult than anything I experienced before. I am not a computer geek, don't understand half the lingo for doing these things.
So, I reloaded the 5.7 and things seem to work right again. Won't go through that again until this is simplified.
However, the "upgrade" did work on the 6.0 RC site I have. But that doesn't help a bit with the real site. Too bad since I really like the new ability of the 6.0.
Unless someone comes up with a simple method of upgrading I won't be upgrading the live site for some time, if ever.
The site is: http://64prn.com
If anyone comes up with an easy and surefire method to upgrade I would appreciate knowing what it is.
Bob
Thanx
Thanks all for the comments - points well taken.
But I'll just say this about videos and the forum as a means of teaching and disseminating information:
Videos have their strong points BUT they can't be commented on, easily edited, or updated because it's a lot of work to redo it. If someone does a video they should have a parallel written tutorial to accompany it that can be commented on and edited. The poor English benefits no one if it's in a video but if it's written it can easily be amended with feedback.
When someone posts an issue in these forums there's only a loose system of categorization. It is presumed and desired that everyone research their issue before posting to see if has been tackled elsewhere first, but this is not an efficient process. Sure someone could periodically read all of this and distill it into a common thread or section, or someone could manually sort it all out and write a comprehensive answer in the manner of a FAQ or something, but that's a lot of work and it doesn't get done. I've wasted hours poking around the forums looking for answers and eventually figure it all out, often because I was pointed to another relevant thread by someone else.
I'd prefer that questions be more formally submitted to a (large) committee and then distilled into a coherent question and answer forum. That would be far more efficient and beneficial to the community.
...
Never happen. There isn't enough skilled and knowledgeable people with the free time to form a committee to talk about this all day. If you have found a solution, then please add it to the Troubleshooting FAQ in the handbook as a child page.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
@occi64 wrote: I had a
@occi64 wrote:
Well, um, maybe if you want help, you could post some details on what exactly those errors are??? No one is going to be able to help you if you just say that "everything showed up as an error."
There are really only two possibilities:
1. You made a mistake somewhere when following the upgrade instructions.
2. You've found a bug in Drupal 6.0 that needs to be fixed.
It would only take you a few minutes to post this, and you stand to benefit from it. That's not much to ask, given the hundreds of hours of volunteer time that some people put into making Drupal 6 happen.
I've done a fair amount of testing of Drupal 6, and in my opinion, the upgrade instructions are well-written. But if you find them confusing or difficult, then maybe you can suggest ways to make them better and easier to understand? What specific parts were confusing to you? As someone who is not a computer geek, you can provide valuable input here, since most of Drupal was written by computer geeks ;)
Instead of just complaining, it's much better to offer constructive criticism -- I can assure you that the Drupal community will respond.
a terrible time
I'm sorry, I should have said it a different way. I followed the update instructions from the video. That wasn't what I meant about the terrible time. It was what happened afterwards. Nothing from the database came through, and all I had was a frontpage with the standard welcome, now post material, and administer, etc.
Right now I am slowly trying to redo the 5.7 site. I've uploaded the backup I did. That has caused formatting problems with amadou theme, i.e. side margins are now placed at the bottom of the page. But, when I log in, everything is in the right place. After reading some posts I guess the next step is to try and reload the backup of the database and see if that helps.
No problem... It does
No problem... It does certainly sound like you had a frustrating experience!
It might be useful to create a new forum post about your specific situation. (If you do this, just post the link here and I'll follow it and try to help you out.)
In the meantime, though, without knowing too many details, a couple things come to mind.
First, for getting your 5.7 site back: Yes, it does sound like you might have some leftover corruption in the database and that reloading your 5.7 backup is the way to go. The safest way to do this is to make sure that you reload the backup into a totally empty database -- i.e., delete all the tables in your Drupal database (and maybe make a second separate backup before you do that), and then reload your original 5.7 backup into the empty database. More details on this were mentioned in one of the posts above, I think. But this should definitely get your original 5.7 site back the way it was.
As for the upgrade to Drupal 6, that sounds very weird... it almost sounds like somehow a new copy of Drupal 6 was installed over your 5.7 site, rather than the 5.7 site being upgraded... I would need more details to help here (what video were you following?).
No problem...
Yes, you might be right. It looked on the frontpage as if 6.0 was in control, but when I logged in it was 5.7 in control. This is the first time I have had any such result with Drupal upgrades. Always in the past everything went off like clockwork.
I did create a new database and uploaded the backup. Plus, I reinstalled 5.7 and they both seem to work now just as before.
I haven't deleted the old folder with the 6.0/5.7 problem, and the old database is still there. Since I'm still learning how these things work, perhaps I can review them soon and see if I can determine what happened. However, I did notice one thing after checking the modules list, some of the modules listed were 6.0. I also noticed something in the old database that didn't make sense to me, but might be of interest/help to others on the list.
When I went into the mysqladmin there was a notice that said something like I was using a multichar set and that could cause problems. Well, I looked at the list in the database and some of the modules listed swedish, about 4 of them as I recall, and all the rest listed uft8, I may have the letters wrong, but I'm sure most know what character code the last is.
Anyway, for now I'm leaving the 5.7 site alone, and experimenting with a totally different 6.0 site that was installed over the RC versions. Now, that one works just fine so far, and I like how it's working. Just wish the upgrade had done as well.
The video was the one on upgrading from 5.x to 6.0 under tutorials on drupal.org.
Swedish?? ;) I'm pretty sure
Swedish?? ;)
I'm pretty sure that everything in Drupal (certainly tables created by Drupal core) should be UTF8. What were the names of the tables that were affected? It would be interesting to find out, to see if they're core Drupal tables or something installed by a contributed module.
Did you make absolutely sure to disable all contributed modules (i.e., ones that don't ship with the main Drupal distribution) before doing the upgrade? As mentioned in the original post in this thread, that can definitely cause problems... and I agree with the suggestion there that (for Drupal 7) it would be great to automate this process, because it's kind of easy to miss one if your list of modules is long (human error and all that ;).
Seeing as how you already seem to have a test area set up that you're experimenting with, I would recommend doing the following: Make a copy of your 5.7 site into a totally different database, totally different site, and try upgrading that to 6.0. That way if something goes wrong again, you can just delete it. I definitely agree that you should leave your live 5.7 site alone until you have this figured out. But trying the upgrade a second time will help figure out if what happened was a fluke or if there is a real problem there somewhere.
Swedish???
There were four files in the database with this listed. Three were from the autoresponder module, and I now forget which the fourth was, and I can't find out now since I deleted them from the database.
OK, thanks, I just took a
OK, thanks, I just took a look at the code for the autoresponder module, and it does indeed seem like that module's tables (it has 4 of them) are not being initialized as UTF8 when they are created, so that's probably where that mysqladmin notice is coming from (why it shows them as Swedish I have no idea, though). Seems like that's a bug with the autoresponder module.
However, unless I'm missing something fundamental here, that shouldn't be the cause of your overall upgrade problems. Just make sure you've disabled the autoresponder module (as well as any other contributed modules you have running on your site) before trying to upgrade to Drupal 6, and hopefully everything will go smoothly.
(As an aside, though, I saw on the autoresponder project page that there is no version of this module for Drupal 6 yet -- and no particular sign that there will be one soon. So if you want to be able to keep using this module on your site, you shouldn't upgrade to Drupal 6 now anyway.)
Good luck!
...
In the Getting Started guide, there is this section, Before you start.
In it, is a section on some Best Practices.
There are two articles I'd like to point out.
Use test sites
Version update considerations
Another article you seem to have missed but are important.
On backwards compatibility The reason you have to disable modules (per instructions) is because, well, the API's aren't compatible. This is a long standing practice you seem to have missed.
I am curious, where you got this idea that Drupal removes the need for having some technical skills or at least a plan to deal with issues. Drupal is a complex product that makes a lot of things easier, but that 'easier' is relative to something that is incredibly complex to begin with.
In the mean time, inflammatory headlines do tend to bring out the flame throwers. I n future I would suggest we all avoid that and try and stick with regular conversation eh?
Oh, and read my sig.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
I'm sure glad I'm not the
I'm sure glad I'm not the only one who thinks upgrading to 6.0 is a bad idea, even when the upgrade process eventually smoothes out, there's still the issue of no 6.0 ready modules which means its going to be a long time before anyone could upgrade their current site. It could take months before 6.0 is useable.
Two things Drupal should work on
1. install/upgrade (30 secs or less)
2. automated db update for modules
- wordpress plugins do not require any separate update system, plugins are easy to enable/disable how hard can it be, Drupal should use Wordpress as a model for easy CMS, powerful doesn't mean anything if its not simple
Also, multilanguage support in D6 is absolutely inadequate
Yes, Drupal 6 still lacks lots of modules that are really essential - first of all, Views and CCK.
Also, the multilanguage support functionality included in the core of Drupal 6 is absolutely inadequate for creating a multilingual site, while external multilang modules (Localizer and i18n) are either not ready at all for D6, or still at the alpha stage of D6-porting.
- wordpress plugins do not
I'm a WordPress plugin author myself. Plenty of WordPress plugins do require an update step. In WP, this must be handled either manually by the user, or within the plugin code itself. Drupal just handles the upgrade for all modules on its own. Frankly, I prefer it that way - there's one standard way of doing it all.
I'll be waiting on upgrading sites that depend on modules for which there isn't a 6.0 release yet. This should be obvious to anyone with half a brain. I'm starting new sites on 6.0, and it's generally going just fine.
Having had a complete CMS
Having had a complete CMS setup using Wordpress using a bunch of plugins 40+, not one plugin I used ever needed a separate update, other than downloading the new version and plug n play. Typically, by the time a new WP release was out most of my plugins were already updated like clockwork, it was nice. Perhaps older plugins or very specific ones require a separate update process. I had a gold mine of plugins, only switched to drupal because with WP I was merely pretending it was a CMS but really its just a blogging software and they really have no intention of being anything else. I hope Drupal adopts some of the WP simplicity.
Having all the modules updated prior to a release is good for everyone, had this taken place with 6.0, everybody would be downloading 6.0 instead of sitting and waiting for a very long time. There's nothing more annoying then downloading a new release and immediately having issues with it.
On the upside, Im looking at how I can not have to depend on so many modules in the first place, it would be great if out of the box Drupal would have everything you need without ever having to download more modules. It probably already has most things if you know how to make use of it but there are some things it just doesn't do without a plugin. What the world needs is a complete CMS solution out of the box no extra plugins necessary.
=-=
I don't know that what you ask for will ever be Drupal. Drupal core is meant to be small and powerful, not bloated with features not everyone will need or use.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
....
So you would have prefered for D6 to just sit there, ready to be relased, while everyone was off working on 7, and then release it in 6 months or so when all the modules are updated? Seems kinda silly to me.
"What the world needs is a complete CMS solution out of the box no extra plugins necessary."
Maybe your world. My world prefers to put the pieces I need together.
Michelle
--------------------------------------
See my Drupal articles and tutorials or come check out life in the Coulee Region.
-----
Shell Multimedia - My sporadically updated mostly Drupal blog.
From a recent blog post
Your definition of a complete CMS is probably not the same as someone else's definition so saying such things is sort of silly. It carries the assumption that everyone's needs are your needs. Drupal is a small flexible core that allows you to build on to obtain a site that is custom to your needs with less effort then building or writing your own
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
nice submiting
nice submiting
may the sun be on your back and Drupal in your face.
Having had a complete CMS
They had updates, WordPress just doesn't present a unified API for doing database updates. Each plugin has to handle it themselves, which is a pain in the ass for developers. I don't think going to update.php when you update a module is the massive barrier to entry you're making it out to be.
Not for the 1.x -> 2.x transition. WordPress, being a simpler system, doesn't update its API as frequently as Drupal does. Upgrading WordPress from, say, 2.1 to 2.2 is like Drupal 5.6 to 5.7 - something that requires no plugin updates - not 5.x to 6.0.
I'd rather have 6.0 out when it's ready, instead of artificially delaying it. After all, I've sites it works fine for, depending on what modules I've used.
Not possible, as everyone has their own needs. A complete CMS solution that has "everything you need without ever having to download more moudles" would be gigabytes of code and run like a sloth.
Talking apples and broccoli,
Talking apples and broccoli, like many complicated CMS software, Drupal is made for developers who like to play with code rather than produce something user-friendly and stable, only a developer type would prefer complexity over simplicity, developers live in the beta world and there's no denying this of course.
From an end user perspective, it's plain as day to see the same old issues and problematic areas that never seem to get addressed. For a sane person, it makes absolutely no sense, but then developers like issues, they like it when they have to piece it all together to them it's play time.
Since many users here are not developers who have valuable time to waste, it just makes good common sense to focus less on analyzing code and more on stability, user-friendliness and listening to many of the users here who bring up various issues. In plain english less headaches is good for everybody. Its funny how developers think in herds, like sheep, I tend to think outside the box about the end user experience.
Just my 2 cents for what its worth,
Re: WP as a complete CMS, look up "complete" at Wikipedia, what part of "complete" didn't you understand ? Sorry, I should probably have broken it down in tiny bytes for your brain to process :) I had a nice setup and was able to do anything Drupal could do only I had to do a lot of work to get it to do that, so I choose to use a CMS built for it, rather than a limited blogging software.
Drupal rocks don't misunderstand me, I'm only pointing out what many have already addressed here at Drupal, forget about developers vs newbies, being either or means absolutely nothing to me, I only see the End User and its no mystery that Drupal is made for code geeks.
=-=
The only reason it's apples and broccolli is because you are changing arguments midstream.
comments like this make me laugh and show a lack of understanding about many things concerning the process and the philosophy regarding Open Source software in general let alone Drupal.
You stick to that argument. While other people actually interested in pushing Drupal forward. Not just for their own development but for the beneift of the community, which actually includes YOU. They do this while you sit there, with your feet up talking about how much time you don't have but can find time to throw out posts like yours above.
Analyzing code, is exactly what produces stability & user friendliness. How else do you expect to get from A to B? just throw it together with no rhyme or reason?
Most of these types of uncontructive complaints (I understand constructive critisism) sound more to me like the whinning of a three legged dog trying to bury a turd on a frozen lake.
You just want what you want, using the words "many others" where it suits you to try and strengthen your point. Which is what exactly ? That you want Drupal to do more out of the box than it does.
Then you throw a bow on it all with two words. Drupal rocks.
Do you have any idea at all, how many core contributors there are?
The hours spent working on Drupal for the benefit of people like yourself? (and more grateful than people like yourself.)
The fast food generation amazes me. It really does.
The difference between people who contribute and those who don't is simple and can be taken into most any context.
for the fast food generation: a context that may make more sense.
A guy goes to get a free hamburger
The burger doesn't have any ketchup
The guy has three choices: The first one those many people you refer to choose even if they do one of the latter two.
bitch because his burger doesn't have ketchup
get ketchup himself
eat it without the ketchup.
What I've found in researching posts like this one, where by labels are thrown around, @ everyone but commenter and wild assertions made, is that the poster has no desire to learn and is easily frustrated by things they don't understand. Specifically the philosophy and concept behind that which they are choosing to be critical of. Ultimatly missing the entire point. To cover up for that they rattle on and on, and change arguments midstream exposing themselves as someone who would just prefer to pop the top and have everything they want handed to them without having to do any thing other then set a few settings in a UI. Anyone who deviates from this idea is worthy of being associated in some odd light with reagrds to trying to make things difficult on purpose, because they like to do it.
BAH! ... That's just crud.
now here's what I'll suggest to you, download the earliest version of Drupal you can find. See how far its come with the contributors of past and present, experience the enhancements between each verion. Maybe than you will be more grateful toward those same coders who give you drupal, those same people you haven't said much/if any good about.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Wow
That's the most insulting thing I've read in a while. You can keep your $.02. I'd say it's worth less that that.
I'm with VM.
Michelle
--------------------------------------
See my Drupal articles and tutorials or come check out life in the Coulee Region.
-----
Shell Multimedia - My sporadically updated mostly Drupal blog.
...
Now you are just saying silly things, calling names and trolling for no good reason. Please do stop calling names in the forums.
I do not know php. I am not a developer. I have used Drupal for more then 4 years without being a developer. This is Open Source software. Development occurs as people contribute to it. Things that users want get worked on as those who are interested in it do the work.
Work towards lowering the technical skill level required to implement sites goes into each versions. Note I said lowering. Implementing a good web site still takes technical knowledge and/or a willingness to learn. Making complex things simple is very hard. Very very hard. To pretend otherwise is silly or a deliberate suspension of belief.
Usability input goes into each version of Drupal. Sometimes it is more then others, it all depends on peoples willingness to get involved in the development cycle and discuss work flow, make mock ups at time when these thoughts can be discussed and implemented.
We (the Drupal community We) are not wasting our time. We are not wasting your time. We have not yet implemented press gangs to shanghai new members onto the good ship Drupal. Though it is an idea that may yet prove to have merit.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
I knew before posting that
I knew before posting that it would be like speaking on deaf ears (people who don't want to hear the truth) try reading the intent not the words and listen without making assumptions, there was no intended insults here just clear observations. I haven't said anything that wasn't already said before by others so don't take it as offensive. I think its funny how some bring up the troll word when something stated was not part of the quasi-religious-political-correctness or stated by a member of the herd, you prove my point (sheep) baaa, i'll end my input on this discussion before it becomes a flame war :)
locked
And you continue calling names.
Thread locked.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain