I disabled all the modules se the user to default admin and set the theme to defaults theme

I though upgrading will just be done in 1 click, but not it wants my database, database user and database password

Is that ok?

I also had problem overwriting old setting.php file, so I renamed it and then and copied the setting.php from 6.3 to the new directory

Is this upgrading ok? or is there something wrong?

Comments

garfy - blocked for being foulmouthed and rude to others’s picture

wow, I got a mess!!!!

here is the link http://www.optimizacijadesign.com/

vm’s picture

with regards to your first question:
you will need to alter settings.php manually
specifically $db_url so that it has the correct DB information in it.

with regards to the second question:
did you run update.php ?

garfy - blocked for being foulmouthed and rude to others’s picture

I got a lot of errors and I run update, now everything seems fine, I had to set the setting.php to true and now I can not set it back to false.

I cant delete setting.php file or edit it in any way

do you know how to do it?

Server does not allow me to change nothing, to overwrite it or edit it
Thanks

UPDATE

I fixed it, the whole folder was 555 instead of 755

works!!

garfy - blocked for being foulmouthed and rude to others’s picture

But I have problwem with fck editor

I cant use it!!

here is the error I got

* user warning: Table 'altermed_optimizacija.fckeditor_settings' doesn't exist query: SELECT name FROM fckeditor_settings WHERE name<>'FCKeditor Global Profile' LIMIT 0, 1 in /home/altermed/public_html/optimizacijadesign/modules/fckeditor/fckeditor.module on line 467.
* user warning: Table 'altermed_optimizacija.fckeditor_role' doesn't exist query: SELECT rid FROM fckeditor_role in /home/altermed/public_html/optimizacijadesign/modules/fckeditor/fckeditor.module on line 475.
* No FCKeditor profiles found. At this moment, nobody is able to use FCKeditor. Create new profile below.
* user warning: Table 'altermed_optimizacija.fckeditor_settings' doesn't exist query: SELECT * FROM fckeditor_settings in /home/altermed/public_html/optimizacijadesign/modules/fckeditor/fckeditor.module on line 585.

It has to do something with tables

vm’s picture

did you get the D6 version of the module ? after replacing the D6 version of the module run update.php ?

garfy - blocked for being foulmouthed and rude to others’s picture

I dl the lates version and ran update

and I get

* user warning: Table 'altermed_optimizacija.fckeditor_settings' doesn't exist query: SELECT * FROM fckeditor_settings in /home/altermed/public_html/optimizacijadesign/modules/fckeditor/fckeditor.install on line 182.
* user warning: Table 'altermed_optimizacija.fckeditor_settings' doesn't exist query: INSERT INTO fckeditor_settings (name, settings) VALUES ('FCKeditor Global Profile', 'a:0:{}') in /home/altermed/public_html/optimizacijadesign/modules/fckeditor/fckeditor.install on line 235.
* user warning: Table 'altermed_optimizacija.fckeditor_settings' doesn't exist query: SELECT * FROM fckeditor_settings WHERE name != "FCKeditor Global Profile" in /home/altermed/public_html/optimizacijadesign/modules/fckeditor/fckeditor.install on line 247.

What if I dlete all the tables from the database for fck editor? and install it from scratch
I mean fck editor works fine on new 6.2 drupal sites with no errors, so it seems like tables for fck editor are missing
Am I right?

mike211175’s picture

Garfy, I would be very interested to know how you fixed that because I am having the same problem

Regards

vm’s picture

which problem? the upgrade problem with core or the fckeditor problem?

mike211175’s picture

Sorry, I should have been more clear

In his 20:28 post on July 14 garfy said that he got a set of errors when trying to run fck. I am getting those same errors after I upgraded my drupal site from 5.8 to 6.4. I deleted the fck editor before upgrading, and then installed the fck module for version 6 after the upgrade (along with the latest version of fck editor itself). Now it seems that the the drupal 6 version of fck cannot use the tables which must be the remnants of what was used by the fck editor in version 5. I have run update.php in version 6 but that did not help.

garfy suggested deleting the fck tables and then reinstalling from scratch - that sounds like a good idea, but I have no idea how to delete the fck tables from the database. I guess this would be done in phpmyadmin, but I am paranoid about deleting the wrong tables!!!

Any help would be much appreciated.

Regards

vm’s picture

garfy is no longer part of the community, as such he can't answer.

an option:
reimport your old DB (before upgrade)
"uninstall" fckeditor using the uninstall tab in adminsiter -> modules. doing so should remove the db entires it made during installation.

you can then upgrade without fckeditor getting in the way and upgrade fckeditor after the core upgrade.

mike211175’s picture

Thanks for that advice, I may have to resort to that, but hopefully not i.e. I have done quite a bit since the upgrade

Regards

vm’s picture

The only other option I can think of then is removing the tables manually.

if you have a back up of the old db, use a test site to accomplish then run a diff on the before and after exports to see what was removed and remove the same things manually.

mike211175’s picture

Thanks for your advice VM, but I managed to fix it.

What I did was to run the uninstall script (on the modules page) for FCK and also for subscriptions, another module that was having a similar problem.

When I ran it for the FCK module I got some red error messages saying that there were some tables that the uninstall script did not recognize. I did not get any error messages when running the uninstall script for the subscriptions module. Anyway, after I had done that I turned the FCK and subscriptions modules back on and they seemed to work.

I expect that there are some stray bits of table that should not be there for the FCK module in v6. Also, not all is well for the subscriptions module because it has forgotten which users had subscribed to what - but at this point that is just too bad - if they really care they will notice that they are not getting what they subscribed to and can log in and check the box, will be a kinda interesting test really.

This is what happens when someone with no formal training fumbles through web stuff by pushing buttons and not knowing php or mysql.

At some point I will have to pay someone to look at my mysql tables and clean them up for me - do you know where I might find someone who offers such services?

Regards

vm’s picture

The paid services forum would be a place to request such a task.

mike211175’s picture

In case anyone is having a similar issue - I can confirm that I rebuilt my D5.3 site on a test site to see if in fact there was an "uninstall" script on the "modules" page that I should have run for the FCK editor when uninstalling the D5 version of FCK editor and upgrading to D6.4.

For the version of FCK that I was running (fckeditor-5.x-1.1) there was no uninstall script. So although it was a good suggestion by VM, running the uninstall script and then comparing the before and after tables to see what tables were deleted by the uninstall script would not work. But my FCK editor is working ok now in D6.4 - although I suspect there are still some stray tables that are not being used and should be deleted, I guess I could fiddle with the database for the test site.

vm’s picture

1.1 isn't supported anymore according to the project page and if 2.2 doesn't have the uninstall routine then that should certainly be filed as a feature request with the developers of the fckeditor module.

however, in the meantime another method would be that one can compare a clean install of drupal with an install that has fck editor installed. Doing a diff of those should get you what you need.

as a side note, if you have a live site using 6.4, I'd certainly upgrade to drupal 6.6

tlangston’s picture

~teetree

There are two new tables with v.6 that did not install. fckeditor_roles and fckeditor_settings. These were missing. I simply logged onto a v6 site database and exported the sql queries for these two tables and ran it on my upgrade sites database and the errors discussed here were all fixed.