Author Topic: Problem with upgrading 1.77 -> 1.8  (Read 1581 times)

paul1

  • Posts: 3
    • View Profile
Problem with upgrading 1.77 -> 1.8
« on: June 29, 2005, 01:41:21 am »
I have a problem, upgrading version 1.77 into 1.81.
I've uploaded all files.
I am starting listmail and below the loginbox I see this:

Upgrade detected! running..
Your Version: 1.77  New Version: 1.8
Please wait..

After a while I get the message:
13Table 'dbasename.lm_custom' doesn't exist

When I look ad the database this table doesn't exists. Why not? Did I miss an upgrade? I also can't find in the code the sql of this table.
There is an string $vtable = "lm_custom"; in admin.php. But in editconf.php this string is only used on a table drop on rows 1006 and 1007.

What do I have to do? Where can I find the sql for this table?

Thanks

DW

  • Administrator
  • Posts: 3787
    • View Profile
    • https://legacy.listmailpro.com
Problem with upgrading 1.77 -> 1.8
« Reply #1 on: June 29, 2005, 11:21:07 pm »
I'm really not sure what happened as noone else has (yet) had this same problem.  Please submit your server information into a new support ticket (along with some notes such as those in your post) and let me know when you've done so.  I may need to make some repairs to your database.

Regards.
Dean Wiebe
ListMailPRO Author & Developer - Help | Support | Hosting

paul1

  • Posts: 3
    • View Profile
Problem with upgrading 1.77 -> 1.8
« Reply #2 on: June 30, 2005, 12:53:59 am »
To see if this table was created. I made a fresh installation. After this fresh installion I get the following result:

Creating config database table lm_config - Inserting example config data.
Creating link database table lm_links - Inserting example link data.
Creating followup messages table lm_follow
Creating mailing list table lm_lists - Creating example list.
Creating user database table lm_users - Adding example user to list.
Creating saved messages table lm_saved - Inserting example saved message.
Creating hit tracking table lm_hits
Creating sent messages table lm_sent
Creating message codes table lm_codes - Inserting default global codes.
Creating scheduled messages table lm_schedule
Creating outbox queue table lm_sendq
Creating selection table lm_saved
Creating selection rules table lm_selectd
Creating custom HTML table lm_chtml
Creating custom HTML data table lm_chtmld
Creating error message table lm_error
Creating error message data table lm_errord


The table lm_custom is not made.

When I start ListMail the login screen shows a message:

Upgrade detected! running..
Your Version: 1.77  New Version: 1.8
Please wait..


After a while I get de error message:

13Table 'mail.lm_custom' doesn't exist

I guess, this error line comes from upgrade.php line 619
Code: [Select]
mysql_query("ALTER TABLE $vtable CHANGE list list SMALLINT UNSIGNED DEFAULT '0' NOT NULL") or die('13'.mysql_error());

$vtable = 'lm_custom';

But this lm_custom doesn't exists. My guess, I only need to add the sql structure for this table to my database.

DW

  • Administrator
  • Posts: 3787
    • View Profile
    • https://legacy.listmailpro.com
Problem with upgrading 1.77 -> 1.8
« Reply #3 on: June 30, 2005, 11:28:53 am »
The lm_custom table was removed for v1.8.  The update processes the entries and moves them to new tables, lm_chtml and lm_chtmld.

I wonder if you have some v1.77 files and some v1.8 files.  Did you make sure to overwrite ALL of the files with the v1.8 ones?

Regards
Dean Wiebe
ListMailPRO Author & Developer - Help | Support | Hosting

paul1

  • Posts: 3
    • View Profile
Problem with upgrading 1.77 -> 1.8
« Reply #4 on: July 01, 2005, 01:14:57 am »
Quote
The lm_custom table was removed for v1.8. The update processes the entries and moves them to new tables, lm_chtml and lm_chtmld.


This was the tricker. After I uploaded all the files form v1.8 I started ListMail for the first time. But I didn't realise it was upgrading en I stoped this process. I think the script finished half. The next time I started ListMail the script start updating. But some parts of updating where allready finished. For example the table lm_custom was removed.

To solve this problem I have removed all 'or die( )' parts from the update.php file en let the updating script begin. Of course there were a lot of mysql errors, but I think it's upgraded now. I have tested and it looks like the script is working correctly.

I wil be more careful the next upgrade. Maybe I will start the next upgrade with a fresh installation.

Maybe you should remove the login box when updating is in progress. In that case, people like me, will see that something different hapens.

Thanks for all your help. This script and all your support is really great.