Recent Topics
  1. b2evolution CMS Support Forums
  2. b2evolution Support
  3. General Support
  4. Problem with duplicate entry in table evo_users__fielddefs after upgrade to 6.4.2-beta

Problem with duplicate entry in table evo_users__fielddefs after upgrade to 6.4.2-beta

1 May 17, 2015 21:42    

Hi all,

I did a small shit in my blog :-(

I am play in my blog with 6.4.2beta (I know that it is not stable, etc etc... but it is very amazing, anyway...)

In upgrade the install scritp warning that a table has a duplicate entry and stoped upgrade... So I trunced the table and the upgrade finish success. But the link's user don't show anymore :-( View sreenshot below)

http://sfl.pro.br/blogs/media/blogs/fotoblogue/links-uers.png

I try export table from database backup and import in new database (with phpmyadmin) but I received this message:

```
Erro

Comando SQL:

-- -- Extraindo dados da tabela `evo_users__fielddefs` -- INSERT INTO `evo_users__fielddefs` (`ufdf_ID`, `ufdf_ufgp_ID`, `ufdf_type`, `ufdf_name`, `ufdf_options`, `ufdf_required`, `ufdf_duplicated`, `ufdf_order`, `ufdf_suggest`, `ufdf_bubbletip`) VALUES (1, 1, 'email', 'MSN/Live IM', '', 'optional', 'allowed', 1, 0, NULL), (2, 1, 'word', 'Yahoo IM', '', 'optional', 'allowed', 2, 0, NULL), (3, 1, 'word', 'AOL AIM', '', 'optional', 'allowed', 3, 0, NULL), (4, 1, 'number', 'ICQ ID', '', 'optional', 'allowed', 4, 0, NULL), (5, 1, 'phone', 'Skype', '', 'optional', 'allowed', 5, 0, NULL), (6, 2, 'phone', 'Main phone', '', 'optional', 'forbidden', 1, 0, NULL), (7, 2, 'phone', 'Cell phone', '', 'optional', 'allowed', 2, 0, NULL), (8, 2, 'phone', 'Office phone', '', 'optional', 'allowed', 3, 0, NULL), (9, 2, 'phone', 'Home phone', '', 'optional', 'allowed', 4, 0, NULL), (10, 2, 'phone', 'Office FAX', '', 'optional', 'allowed', 5, 0, NULL), (11, 2, 'phone', 'Home FAX', '', 'optional', 'allowe[...]

Mensagens do MySQL : Documentação
#1062 - Duplicate entry '' for key 'ufdf_code'

```

unfortunately my skill in MySqL or database is NULL :-(

Is there any workaround for this problem?

The blog run fine except link social media that don't show :-(

Thanks for any help

Back to top

2 May 18, 2015 08:41

@oigreslima from what version was you upgrading in the first place? Also, your site is not available at this moment, so I can't see your screenshot.

Is the table in which you're trying to import that sql empty?

Back to top

3 May 18, 2015 11:46

Hi @mgsolipa,

I has upgrading 5.2.2 > 6.0.0 (ok) after 6.0.0 > 6.1.2 (ok) and when 6.1.2 > 6.4.2 the problem occurred!

No, the table in which I am trying to import is not empty. The db.zip was create in backup 6.0.0 > 6.1.2!

My site is, at moment, avaliable again :-)

Thanks

@mgsolipa wrote earlier:

@oigreslima from what version was you upgrading in the first place? Also, your site is not available at this moment, so I can't see your screenshot.

Is the table in which you're trying to import that sql empty?

Back to top

4 May 18, 2015 19:55

@oigreslima you cannot restore an old backup. The table structure has changed.

You need to do this:

1) Restore your previous DB completely (all tables)
2) Go to that table and change the names that are duplicates. You probably have 2 fields called "Facebook" or any other name. All names must be unique.
3) re-run the upgrade process and it will work.

Back to top

5 May 19, 2015 01:39

Hi @fplanque

First all, thanks for your reply and your nice software!

I fix my shit :-) I follow a remix your direction!

1) I install (in another directory) an new b2evolution 6.4.2. (with another DB).
2) I compare the table evo_users__fielddefs in two DB (new install create demo users , demo post, blogs, etc)
3) I add table/field in my DB as was in DB form new install

After I edited my profile in my blog! Because links are mix (bio with flickr, etc..)

Now all is ok.

There is any warning when I add an another link, but work :-) I hope that in stable version (after upgrade) all will worf fine!

@fplanque wrote earlier:

@oigreslima you cannot restore an old backup. The table structure has changed.

You need to do this:

1) Restore your previous DB completely (all tables)
2) Go to that table and change the names that are duplicates. You probably have 2 fields called "Facebook" or any other name. All names must be unique.
3) re-run the upgrade process and it will work.

Back to top

6 May 20, 2015 18:12

Ok, good you could fix it.

In the next release, the upgrader will no longer fail in case of duplicates.

Thank you for reporting.

Back to top

7 Apr 04, 2017 19:30

Hi, now for the first time in twelve years I am in trouble during a standard upgrade (not the automatic one). I also got this duplicate error, and the upgrader got stuck, and I don't know what to do:

MySQL error!

Duplicate entry 'german' for key 'cat_urlname'(Errno=1062)

Your query:

ALTER TABLE evo_categories

      MODIFY cat_urlname varchar(255) COLLATE ascii_general_ci NOT NULL

I am upgrading from 5.0.6 to 6.8.8.

I hope somebody can help. Thanks!

Back to top

8 Apr 04, 2017 20:07

I was able to fix it by changing the variables via phpmyadmin

Back to top


Form is loading...