Alright I have successfully upgraded to Drupal 7 on my GoDaddy.com hosting/domains. It really was quite painless to do for me, but then again I am also a software engineer with over 20 years in the IS and/or IT industry. So I was well aware of the installation and/or upgrade processes necessary for each of the required components. But with GoDaddy's domain controls for content and database control it proved to be rather easy. But I have to admit it took me using these tools to gather a set of information first such as database username/password/path information.
Once I gathered all of this information, I then backed up the entire site using the file manager and then downloaded the zipped file to a local directory. Then on the first attempt, I made the mistake of just copying the new files over to the appropriate directories leaving all other files in place, then copying over the new versions of the modules I had installed previously (minus those no longer needed since the core now handles the functionality) and then going to the domain name to have it install using the existing information in the database.
This resulted in the install functionality telling me that Drupal was already installed and then I clicked the administation page, only to find that there was no administration links on the page and no way to log in. In fact, it was a mashup of a bunch of my added content. Luckily I have a sense of humor and found it to be really funny that it simply pulled ALL my created content and promoted to the first page basically.
Having learned from this experience, I then deleted all the Drupal related directories and files (leaving all the other directories that GoDaddy installs alone) and dropped all the tables within the database (or you can simply create a new one), then went back to the page again to let the install/update functionality run again. This time it installed fine and runs like a dream.
So my advice for those on GoDaddy.com who want to use Drupal 7 before they come up with their installation script/profile is for them to install it new and fresh. While this will mean that they will have to add back all previous functionality manually, it will save them a lot of time from trying to get their previous functionality to function within their Drupal 7 site.
GoDaddy has promised to come up with a installation script/profile soon but are not sure when this will occur. But considering how hard this would have been on other domain hosting sites, I found it fairly easy to resolve but then again I am a software engineer and have been in the IT/IS industry for a while. So this might not have been quite so easy for the average end-user but I am quite sure that the support team would be willing to walk the user through the process.
GoDaddy has proved to be very supportive of Drupal and has helped me greatly whenever I have needed additional assistance. I have appreciated all their help and support and we as a community should make sure to applaud their efforts.
Comments
Didn't you follow the
Didn't you follow the "Upgrade.txt" or does GoDaddy cause problems with erasing nearly all the Drupal files, etc?
following the upgrade.txt
Yes I did indeed follow the upgrade.txt and that is why I did not initially just wipe everything and start over. I thought that it looked simply enough to just "upgrade" using these steps. I did everything I was supposed to according to the upgrade.txt and then gave it a shot. And to the naked eye it appeared to work without a hitch.
That is until I accessed the front page (node/1). It had all my custom content on it all at once (to spite having been disabled and/or uninstalled in some cases), like it was confused as to whether or not it should display certain content so it just defaulted to displaying it all. But the funniest part was that it showed everything but the administration functionality. Which it should not have done anyway if it thought I was an anonymous user. Not a problem right, just log in right? Well, easier said than done. the login page seemed to be missing and all attempts to access it failed no matter what way I tried to access it (alias or ?q= methods). Both appeared to be lost in the confusion created within the scripts used by the upgrade.
At that point I thought to myself, you know thanks to Drupal 6 all of this custom content had been a snap to create and all-in-all had taken me less than 1/2 the time it would have taken me any other way. And with Drupal 7 promising to make it even simplier than it had been in Drupal 6; I should just "start over" with a semi-clean install (only kept the database name, userid, and password but dropped all tables in the database) and re-create the content fresh.
It would give me a chance to really take the official Drupal 7release out for a test ride of sorts. And as promised Drupal 7 has proved to take even half the effort it took in Drupal 6 (for all your mathematicians out there, Drupal 6 took half the time and Drupal 7 is twice as easy and it is twice as fast to create content than in Drupal 6; this means for all intent and purposes Drupal 7 virtually takes 1/4 the time to do things as it does in other ways). So, while the upgrade did not go exactly as intended initially, I am very happy with my upgrade to Drupal 7 and my ability to run it on GoDaddy's hosting solution.
So whether it went exactly like the upgrade.txt or not, it was rather easy to upgrade to Drupal 7 but I did have to recreate custom content and re-do administration tasks. But I was surprisingly not upset with this fact, largely due to the fact that it was as easy as 1-2-3 to do so.
All in all, the Drupal project and community have hit a home run with this release in my eyes. I am truly impressed! And, I am not easily impressed...
This fresh start you're
This fresh start you're describing is very tempting. I'd like to get rid of php errors, D6 debris, and what not. I have over 400 nodes though. How long do you think it would take me to copy and paste, copy and paste, copy and paste... Drupal7 is faster to administer, true, but still, I'm dithering.
Fresh Start For Numerous Nodes
It is no doubt that Drupal 7 is much faster to create any sort of content but you are right 400 nodes would not be a small effort no matter how fast it is. I am not sure how many man-hours or resources you have to dedicate to the effort but one person working at least 8 hours a day I am sure would take the better part of a month to say the least. And, that is with all the content established and just has to be transferred and published.
But consider this, what will you gain with the upgrade? Easier administration, less clutter, fewer errors (especially as modules become deprecated), more advanced modules, and if you are a contributer then a chance to polish features before they are incorporated into Drupal 8.
But the best thing for me has been the Administration Menus and UI. I truly appreciate that so much time was put into these features because they make all the difference in the world when spending endless hours administrating a site.
So is it worth all the extra man-hours spent on converting? I would say yes, but I have no real idea what kind of content or the depth of the functionality you have within your installation of Drupal 6.
Same problem here
Well, I have written programs since '74 but it didn't help here.
I moved away all old files (inactivating non-core themes, modules, setting off line etc) and only kept the old database but the update script crashed.
http://drupal.org/node/1016848
I have been updating my Drupal on Godaddy since ver. 4.7 (3.5 yrs ago) and never had one problem.
I have never noticed GoDaddy is different from other servers.
I think I will wait until everything has been investigated properly regarding the v.6 to v.7 update.
Edit:
The only thing I come to think of that makes GoDaddy different is that it still runs Apache 1 for the webhosting. (You have to ask for special "gridhosting" to get updated Apache.) Apache 1 makes it impossible to install f.ex. Gallery 3, at least when I tried.)
I agree GoDaddy has good support.
Not working on Fresh Install
I followed all of the instructions in the install and was unable to get this going. I'm wondering if it was due to trying to install this on previewdns so I wanted to know if you were installing on non preview DNS.
Fresh Install Using?
Are you using the "File Manager" or the "FTP" tool? I found that I had to do a combination of the two to fully accomplish what I was trying to do. File Manager let me change permissions and delete files, but I had to use FTP to either transfer entire directories over or to create new directories and transfer files individually.
I did run into a few files that the GoDaddy script install made read only and I had to change the permissions in order to even uninstall them properly. But I did not use anything that gave me a "preview" of any sort that I could tell. So I am a little confused by the question a little.
Maybe if you clarify what "tool" you're using to accomplish this, it might be a little clearer to us what you are doing.
Installed
I was installing this using godaddy's previewdns.com so the url was www.mysite.com.previewdns.com It seemed to be the preview DNS that cause me grief. It works now so I'm just working out other bugs:).
Preview DNS
Actually that is a piece of funtionality at GoDaddy that I was not even aware of. I had to go and educate myself on it once you mentioned it. But you are in luck, in doing so I found that I know of a better and more Drupal friendly way to do what .previewdsn.com functionality was doing for you. In fact, it would add some functionality to boot.
If you download and install the "Demonstration site (Sandbox/Snapshot)" module from http://drupal.org/project/demo and you should be able to do the same sort of thing and even create a snapshot that you can go back to if installing a module "breaks" your site.
And while you are at it I would look into installing Devel from http://drupal.org/project/devel and Drush from http://groups.drupal.org/drush while you are at it. Drush is not truly a module per sei, so unless you have ssh control of your host server you might have to upload it into default/modules directory and then let the support folks actually install it, but it would be well worth the effort.
All three are well worth their weight in gold in helping to successfully maintain a site better. I am glad that you were able to at least get up and running but hopefully that is just the beginning.