Recent Topics

1 Nov 08, 2007 17:37    

My b2evolution Version: Not Entered

Hi all, (i 'll try to make this post in english=)

I've had a problem with b2evo update
I would like update b2evo 1.10.0 "Miami" (if i remember?!?)
to b2evo 2.1.0 "Las Vegas"

Big mistake!!!
The update rightly dont work..

So i've try to downgrade, and return to my old version but another error message :

This is b2evolution version 1.10.3.

You cannot use the application before you finish configuration and installation.

Database schema is not up to date!

You have schema version «9407», but we would need «9350».

In fact, i cant have the new version and return to my old version.
I've try to make new install and just restaure DB (catgégories, com., groups, posts, users) but another errror message et unfortunatly i cant see my possts and comments, bref..

If someone have an idee
Thx in advance,

PS: i havent make Backup of my DB at starting update.....[/code]

2 Nov 09, 2007 04:17

Now that is a major problem.
Unless you can read the database changes and do manual edits of your databse from 9407 to 9350, there is no possible way to downgrade.

As with any other software, especially for production sites, always make backups if it is a major version upgrade :)

Or at least, test it out first on your test-environment :) That's what I did when I upgraded from v1.10.2 to v2.0.0-alpha.

Your only option is to upgrade again. That's the only path I can see.

You haven't mentioned what does not work with 1.10.0 to 2.1.0. Is it the Skin? The upgrade proces failed? Or something else?

3 Nov 09, 2007 08:37

Just make sure you have uploaded all the files, and I mean all :)
Make sure you check your "conf" folder as I got the same message simply because of one file in that folder that wasn't updated.

4 Nov 09, 2007 16:26

John wrote:

Just make sure you have uploaded all the files, and I mean all :)
Make sure you check your "conf" folder as I got the same message simply because of one file in that folder that wasn't updated.

I've upload all the file, but it doesnt work...

and if i manually change the DB version, error message...

Do you know what part of the db can i restaure into a news insallation to have my post + comment + user again?

5 Nov 09, 2007 17:04

Downgrading is never done before, so don't go that way. In stead try to upgrade to the version you intended. Tell us where that goes wrong.

Good luck

6 Nov 12, 2007 03:52

I cant update my b2evo version.
My blog in B2evo "Miami" dont still work yet, i believe its make a half update so my DB is corrupted.

When i try to make new install, i cant restaure only my post and comment....

To see my site : http://pouark.free.fr

7 Nov 12, 2007 04:15

I don't see anything in the folder of your blog.

Normally the database doesn't get corrupted. It keeps track of the changes it has made.
Do try to finish the upgrade to 2.1. There is no reason why that shouldn't work if you had a 1.10 blog running.

Good luck

8 Nov 12, 2007 04:32

With my 1.10 Miami ->
I've only access to admin panel with this error message:

Notice: Undefined property: blog_default_skin in /mnt/152/sda/7/3/pouark/inc/MODEL/collections/_blog.class.php on line 170

Notice: Undefined property: blog_force_skin in /mnt/152/sda/7/3/pouark/inc/MODEL/collections/_blog.class.php on line 171

Notice: Undefined property: blog_default_skin in /mnt/152/sda/7/3/pouark/inc/MODEL/collections/_blog.class.php on line 170

Notice: Undefined property: blog_force_skin in /mnt/152/sda/7/3/pouark/inc/MODEL/collections/_blog.class.php on line 171

Notice: Undefined property: blog_default_skin in /mnt/152/sda/7/3/pouark/inc/MODEL/collections/_blog.class.php on line 170

Notice: Undefined property: blog_force_skin in /mnt/152/sda/7/3/pouark/inc/MODEL/collections/_blog.class.php on line 171

Warning: Cannot modify header information - headers already sent by (output started at /mnt/152/sda/7/3/pouark/inc/MODEL/collections/_blog.class.php:170) in /mnt/152/sda/7/3/pouark/inc/VIEW/_menutop.php on line 39

And when i try to access to my B2evo (not admin), i've this one :

Notice: Undefined property: blog_default_skin in /mnt/152/sda/7/3/pouark/inc/MODEL/collections/_blog.class.php on line 170

Notice: Undefined property: blog_force_skin in /mnt/152/sda/7/3/pouark/inc/MODEL/collections/_blog.class.php on line 171
L'habillage par défaut [] affecté au blog [=Pk Blog !=] n'existe pas. Il doit être correctement configuré dans les propriétés du blog ou dans le fichier stub. Contactez le webmaster...

I'll try to update to 2.1 and report the error message.

Thx a lot!

9 Nov 12, 2007 04:46

When i want to update from 1.10 to 2.1

I've this error message:

Vérification de la version du schéma BD... 9350 : OK.
Updating chapter url names...
Une erreur inattendue est survenue!

Si cette erreur persiste, merci de la signaler à l'administrateur.

Retourner à la page d'accueil
Informations additionnelles à propos de cette erreur:

MySQL error!

Duplicate column name 'cat_urlname'(Errno=1060)

Your query:

      ALTER TABLE evo_categories
        ADD COLUMN cat_urlname VARCHAR(255) NOT NULL

So i cant update...

And if i just retry (relaunch my url), i've this one:

Database schema is not up to date!

You have schema version «9350», but we would need «9500».

Thx in advance

10 Nov 12, 2007 05:01

Goto the cPanel or equivalent of your host and start phpMyAdmin (most likely to be found under MySQL databases). There find the column 'cat_urlname' under 'categories' and delete it.

or

Open ../blogs/install/_functions_evoupgrade.php and find lines 1692-1694:

$DB->query( '
ALTER TABLE T_categories
ADD UNIQUE cat_urlname ( cat_urlname )' );


and coment them out like:

/* $DB->query( '
ALTER TABLE T_categories
ADD UNIQUE cat_urlname ( cat_urlname )' ); */


upload the file and try again.

If you feel this is beyond your knowledge, you can PM (personal mail, see button under this post) me with login details of your acount (ftp or cPanel).

Good luck

11 Nov 12, 2007 05:21

Thx:

Still have :

Database schema is not up to date!

You have schema version «9350», but we would need «9500».

and now i have :

Vérification de la version du schéma BD... 9350 : OK.
Updating chapter url names... OK.
Updating Settings... OK.
Creating DB schema version checkpoint at 9406... OK. (Elapsed upgrade time: 0 seconds)
Moving general settings to blog settings... OK.
Upgrading blogs table...
Une erreur inattendue est survenue!

Si cette erreur persiste, merci de la signaler à l'administrateur.

Retourner à la page d'accueil
Informations additionnelles à propos de cette erreur:

MySQL error!

Can't DROP 'blog_force_skin'; check that column/key exists(Errno=1091)

Your query:

ALTER TABLE evo_blogs
              DROP COLUMN blog_force_skin

I must delete "blog_force_skin"?

12 Nov 12, 2007 05:31

It probably is dropped already, so it can't find it. Comment out the lines in ../blogs/install/_functions_evoupgrade.php 1730 - 1732:

$query = "ALTER TABLE T_blogs
DROP COLUMN blog_force_skin";
$DB->query( $query );

Good luck

13 Nov 12, 2007 17:12

Thx for all
But i've another one... :

MySQL error!

Can't DROP 'blog_default_skin'; check that column/key exists(Errno=1091)

Your query:

ALTER TABLE evo_blogs
                 ALTER COLUMN blog_allowtrackbacks SET DEFAULT 0,
                  DROP COLUMN blog_default_skin,
                   ADD COLUMN blog_owner_user_ID   int(11) unsigned NOT NULL default 1 AFTER blog_name,
                   ADD COLUMN blog_skin_ID INT(10) UNSIGNED NOT NULL DEFAULT 1 AFTER blog_allowusercss

14 Nov 12, 2007 18:19

Hi pouark,

You are nearly there. There means a new checkpoint and from there everything should run smooth. But you needed to go through this part because here it hanged on your previous install, so probably it didn't do everything before the next checkpoint.

Comment out line 1807 in _functions_evoupgrade.php:

// DROP COLUMN blog_default_skin,


The column probably was dropped already.

The checkpoint is nearing:

DROP COLUMN blog_default_skin,
	ADD COLUMN blog_owner_user_ID   int(11) unsigned NOT NULL default 1 AFTER blog_name,
	ADD COLUMN blog_skin_ID INT(10) UNSIGNED NOT NULL DEFAULT 1 AFTER blog_allowusercss' );
		echo "OK.<br />\n";

		install_basic_widgets();
		set_upgrade_checkpoint( '9408' );
	}


The two commands ADD COLUMN may give problems also (if they already exist). Comment them out, but only if they give an error.

Good luck

15 Nov 12, 2007 18:48

Afwas wrote:

Hi pouark,

You are nearly there. There means a new checkpoint and from there everything should run smooth. But you needed to go through this part because here it hanged on your previous install, so probably it didn't do everything before the next checkpoint.

Comment out line 1807 in _functions_evoupgrade.php:

// DROP COLUMN blog_default_skin,


The column probably was dropped already.

Thx but how to comment out this line ?
/* dont work

16 Nov 12, 2007 18:52

Comment out by placing

//


before the line or

/* some text to comment out */

Good luck

17 Nov 12, 2007 18:57

Afwas wrote:

Comment out by placing

//


before the line or

/* some text to comment out */

Good luck

Yes but i can't just comment ligne 1807:

like this :
/* DROP COLUMN blog_default_skin, */

Or like this:
// DROP COLUMN blog_default_skin,

I can just comment out the entire :

		echo 'Updating blogs table... ';
		$DB->query( 'ALTER TABLE T_blogs
								 ALTER COLUMN blog_allowtrackbacks SET DEFAULT 0,
									DROP COLUMN blog_default_skin,
									 ADD COLUMN blog_owner_user_ID   int(11) unsigned NOT NULL default 1 AFTER blog_name,
									 ADD COLUMN blog_skin_ID INT(10) UNSIGNED NOT NULL DEFAULT 1 AFTER blog_allowusercss' );
		echo "OK.<br />\n";


		install_basic_widgets();

		set_upgrade_checkpoint( '9408' );

18 Nov 12, 2007 20:20

Hi....

I've just delete the ligne 1807 and now :

MySQL error!

Table 'evo_skins__skin' already exists(Errno=1050)

Your query:

CREATE TABLE evo_skins__skin (
              skin_ID      int(10) unsigned      NOT NULL auto_increment,
              skin_name    varchar(32)           NOT NULL,
              skin_type    enum('normal','feed') NOT NULL default 'normal',
              skin_folder  varchar(32)           NOT NULL,
              PRIMARY KEY skin_ID (skin_ID),
              UNIQUE skin_folder( skin_folder ),
              KEY skin_name( skin_name )
            )

When that's will finish????

19 Nov 13, 2007 00:21

This will finish when there are no more errors :'(

I do not understand why you can't comment out a piece of the code.
For the time being you should continue with what you were doing: comment out or delete the pieces that give errors and try again.This *will* stop at one point and then you can happily blog ever after.

Good luck

20 Nov 13, 2007 01:15

but for this error, can i delete "evo_skins__skin" on database?

21 Nov 13, 2007 01:29

Yes you can.

There seem to be two kinds of errors:
1) CREATE a table when the table already exists -> comment out / delete the code to CREATE the table *or* delete the table from the database (and let the script create the table again).
2) DROP a table that is already deleted -> comment out / delete the code that DROPs the table.

Good luck

22 Nov 13, 2007 01:39

Ok i've make all you tell me
and finally, i've the default error message :

Vérification de la version du schéma BD... 9407 : OK.
Creating skins table... OK.
Creating skin containers table... OK.
Installing default skins... OK.
Creating widgets table... OK.
Updating blogs table... Installing default widgets...
Fatal error: mysql_free_result(): supplied argument is not a valid MySQL result resource in /mnt/152/sda/7/3/pouark/inc/_core/model/db/_db.class.php on line 793

23 Nov 13, 2007 01:58

This is a test. I am not sure if it works.
Coment out or delete line 1813:

install_basic_widgets();

If it doesn't give an error, that's fine, else I have another idea.

24 Nov 13, 2007 04:21

The same error message :(

pouark wrote:

Ok i've make all you tell me
and finally, i've the default error message :

Vérification de la version du schéma BD... 9407 : OK.
Creating skins table... OK.
Creating skin containers table... OK.
Installing default skins... OK.
Creating widgets table... OK.
Updating blogs table... Installing default widgets...
Fatal error: mysql_free_result(): supplied argument is not a valid MySQL result resource in /mnt/152/sda/7/3/pouark/inc/_core/model/db/_db.class.php on line 793

25 Nov 13, 2007 05:52

The good news is, it's stuck at set_upgrade_checkpoint. That's good because if you solve this problem, the rest of the upgrade script *should* run flawlessly.

You can manually set the new checkpoint in phpMyAdmin. In your database find evo_setting -> db_version. Set the content of that field (set_value) to 9408 and run the install script again.
Please let me know what the old value was.

Good luck

26 Nov 13, 2007 19:06

My DB version is 9409

I've change it to 9408
and i've another error message :

MySQL error!

Unknown column 'blog_stub' in 'field list'(Errno=1054)

Your query:

UPDATE evo_blogs
                    SET blog_access_type = "relative",
                        blog_siteurl = CONCAT( blog_siteurl, blog_stub )
                  

WHERE blog_access_type = "stub"

27 Nov 14, 2007 01:19

Hi pouark,

Something happened that I cannot explain, but never mind that. Change the database version (back) to 9409 and try again.

Good luck

28 Nov 21, 2007 22:04

I've replace db version to 9409

And now :

Vérification de la version du schéma BD... 9412 : OK.
Renaming tables...
Une erreur inattendue est survenue!

Si cette erreur persiste, merci de la signaler à l'administrateur.

Retourner à la page d'accueil
Informations additionnelles à propos de cette erreur:

MySQL error!

Can't find file: './pouark/evo_item__prerendering.frm' (errno: 2)(Errno=1017)

Your query:

RENAME TABLE evo_item__prerendering TO evo_items__prerendering,
                              evo_poststatuses TO evo_items__status,
                              evo_posttypes TO evo_items__type,
                              evo_posts TO evo_items__item

29 Nov 22, 2007 03:41

Hi pouark,

Can you have a look? Does the table evo_items__prerendering exist? The same with the other three. If they are already renamed, then I will give you some code to skip this part, else you want some code to create these entries.

Good luck

30 Nov 22, 2007 12:31

evo_items__prerendering doesnt exist anymore
and i can't rename the others...

31 Nov 22, 2007 13:01

Hi pouark,

This is going a bit slow ;)
Can you make a backup of your databse in phpMyAdmin and make it available online (put it on your server and send me a link to it, you may PM me if you prefer).
I will correct the problems.

Good luck

32 Nov 25, 2007 18:29

I have updated your database. All is working smooth now. If you have any questions left, please ask.

Happy blogging


Form is loading...