Recent Topics

1 Mar 20, 2018 21:20    

Additional information about this error:

MySQL error!

Unknown column 'hit_blog_ID' in 'evo_hitlog'(Errno=1054)

Your query:

ALTER TABLE evo_hitlog

CHANGE COLUMN hit_ID hit_ID INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,

CHANGE COLUMN hit_datetime hit_datetime TIMESTAMP NOT NULL DEFAULT '2000-01-01 00:00:00',

CHANGE COLUMN hit_serprank hit_serprank SMALLINT UNSIGNED DEFAULT NULL,

CHANGE COLUMN hit_blog_ID hit_coll_ID INT(10) UNSIGNED NULL DEFAULT NULL,

CHANGE COLUMN hit_response_code hit_response_code SMALLINT DEFAULT NULL,

ADD COLUMN hit_agent_ID SMALLINT UNSIGNED NULL DEFAULT NULL AFTER hit_agent_type

2 Mar 21, 2018 06:46

How did this error occur? What are the steps you followed to produce this error?
Please provide some background to how you arrived at this error.
Did you upgrade.
What version of b2evolution are you using?
Post a full screenshot of the error.

3 Mar 21, 2018 06:50

Upgrade from version 4 point something point something. I would be happy to provide screenshot. I did not see place to upload. How do I add screenshot

4 Mar 21, 2018 21:17

Maybe this will work?

6 Mar 21, 2018 23:28

K you re looking for more info but I really don't know what to add?

I was using version 4.X.X and the auto upgrade didn't work because it said my version was too old to auto upgrade reliable and to do it manual.

So I downloaded the latest stable version 6 point whatever point whatever and FTP'd it over.

Then I ran the install and this is the result.

I am not sure how to post a full screen because it doesn't all fit on one screen. I can post multiple screens with everything if you think that would help?

7 Mar 22, 2018 09:20

Hi
I imagine the database changes are significant and the new install can't cope?
Can you try setting up a new database to see id that works and then maybe update the database with data from the older one.
Alternatively you could try an incremental update, say to 5.2 and see if that works. I think I had a similar issue years ago and had to update the database bit by bit.

I imagine though that others with a better grasp will want to fix this from a straight upgrade

8 Mar 22, 2018 10:11

If I may ask, did you make a backup of your database before the upgrade?

From the screenshot / snippet you posted it seems that your database table evo_hitlog does not have a column named hit_blog_ID. The upgrade is trying to change the column name to hit_coll_ID.

Can you access your database table and check if it exists manually?

9 Mar 22, 2018 10:19

It could be that your table is corrupted try, log in to phpMyAdmin, select the table, evo_hitlog under the Operations tab, then "Repair Table" at the bottom of the list.

You could also log into your blog, go to the system > maintenance section and normalize / repair tables there and then try to upgrade manually again.

10 Mar 26, 2018 00:07

You are correct. I can find no hit_blog_ID.

I see a hit_sess_ID and a hot_agent_ID and other hit_xxxxx_IDs, but no hit_blog_ID.

How do I fix? :(

11 Mar 26, 2018 02:56

In order to easily fix that we'd need to see what happened above the error.


Form is loading...