Announcement

Collapse
No announcement yet.

PHP error suppression command?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
    dunefreak
    Senior Member

  • dunefreak
    replied
    It was a blank database as I just used it to test template changes. Should I just go in and delete the tables that it says already exist.

    Leave a comment:

  • G-man
    Senior Member

  • G-man
    replied
    Dunefreak,
    I have been down this road before. Do a data and structure dump to your local harddrive using your vadmin tools and then ftp that dumb in ASCII to your vserver root. In the Vadmin drop the test database you are working on then create a new database of the same name. In telnet type the following:

    mysql yourtestdatabase < nameofyourdump.sql

    Using this process you will be able to keep recreating your test database and keep trying the upgrade script and any variations of the upgrade script until it works.

    Also I highly encourage you place the error suppression lines in like Freddie said. This should get you to where I am right now and as soon as the Beta team figures a workaround we can go the rest of the way.

    Hope this helps,

    G-man

    Leave a comment:

  • Freddie Bingham
    Former vBulletin Developer

  • Freddie Bingham
    replied
    Your error is showing that the table 'privatemessage' already exists and can't be created. 'privatemessage' is a new table to version 2.0 so I would have to think you tried to run the upgrade script more than once. What happens if you do a database restore and then try the upgrade script. That is the error we need.

    Leave a comment:

  • dunefreak
    Senior Member

  • dunefreak
    replied
    Is there a problem with the script and vservers as I cannot upgrade. I am doing it on a test board so I am not as concerned, but would like to figure it out. The following is the tech e-mail sent.

    Code:
    Database error in vBulletin Upgrade: Invalid SQL: CREATE TABLE privatemessage (
    privatemessageid INT UNSIGNED NOT NULL AUTO_INCREMENT,
    folderid SMALLINT NOT NULL,
    userid INT UNSIGNED NOT NULL,
    touserid INT UNSIGNED NOT NULL,
    fromuserid INT UNSIGNED NOT NULL,
    title CHAR(250) NOT NULL,
    message MEDIUMTEXT NOT NULL,
    dateline INT UNSIGNED NOT NULL,
       showsignature SMALLINT NOT NULL,
    iconid SMALLINT UNSIGNED NOT NULL,
    messageread SMALLINT NOT NULL,
    PRIMARY KEY (privatemessageid)
    )
    mysql error: Table 'privatemessage' already exists
    mysql error number: 1050
    Date: Thursday 15th of February 2001 09:12:10 AM
    Script: /test/admin/upgrade1.php?step=2
    Referer: [url]http://www.offroadbb.com/test/admin/upgrade1.php[/url]

    Leave a comment:

  • Freddie Bingham
    Former vBulletin Developer

  • Freddie Bingham
    replied
    We don't have an answer for this problem at the moment.

    Leave a comment:

  • G-man
    Senior Member

  • G-man
    replied
    The saga continues...

    Leave a comment:

  • G-man
    Senior Member

  • G-man
    replied
    And step 5:

    Altering announcement table

    Creating moderator table

    Merging old moderators


    Warning: 0 is not a MySQL result index in ./db_mysql.php on line 120

    Warning: 0 is not a MySQL result index in ./db_mysql.php on line 120

    Next step -->


    Then it errors out at step 9

    Leave a comment:

  • G-man
    Senior Member

  • G-man
    replied
    Step 4

    Right here:

    Updating data in forum table


    Warning: 0 is not a MySQL result index in ./db_mysql.php on line 120

    Dropping category table

    Altering forum table


    Warning: 0 is not a MySQL result index in ./db_mysql.php on line 120

    Next step -->

    Leave a comment:

  • Freddie Bingham
    Former vBulletin Developer

  • Freddie Bingham
    replied
    What step gave you that error.

    Leave a comment:

  • G-man
    Senior Member

  • G-man
    replied
    Thank you for getting me past those darn errors but now it looks like I have other problems:

    Warning: 0 is not a MySQL result index in ./db_mysql.php on line 120

    Leave a comment:

  • G-man
    Senior Member

  • G-man
    replied
    Frankly I would like to hear from some of them because the text I posted was directly from their FAQ and was pointed out by a senior tech after 9 hours of trying to get your upgrade script to work.

    Leave a comment:

  • Freddie Bingham
    Former vBulletin Developer

  • Freddie Bingham
    replied
    I know there are other vB owners on Vservers who do not have this problem.

    Leave a comment:

  • G-man
    Senior Member

  • G-man
    replied
    Blame it on Vservers....

    Leave a comment:

  • Freddie Bingham
    Former vBulletin Developer

  • Freddie Bingham
    replied
    I told you what you could try in my last post..If your mysql implementation is how your host says it is than I think you would be the first vB user to ever have this problem as previous upgrades have used the ALTER command.

    Find every instance of doqueries(); in upgrade1.php

    Place $DB_site->reporterror=0; on the line before it. Alot of the queries don't ALTER but some code turns the error reporting off than back on so you need to do as I said to make sure the error reporting stays off for you throughout the script.

    Leave a comment:

  • G-man
    Senior Member

  • G-man
    replied
    Freddie, Ed,
    Don't forget me. I have 25000+ people waiting on the new version.

    Leave a comment:

Related Topics

Collapse

Working...
X