Page 1 of 1

Problem after migrating from 2.5 to 3.4.2

Posted: 04 Jul 2015, 16:34
by adpc
Hi,

After migrating from 2.5 to 3.4, when you place a message on frontend, users get this message below. :x
Also when I place on backend a message, it is not sorted on date, and is on the last page on the frontend. The other migrated messages are sorted on date. How can I solve this? Thanks
1062 - Duplicate entry '1' for key 'PRIMARY' SQL=INSERT INTO `uz0i2_phocaguestbook_items` (`id`, `catid`, `parent_id`, `lft`, `rgt`, `level`, `path`, `username`, `userid`, `email`, `homesite`, `ip`, `title`, `alias`, `content`, `date`, `published`, `checked_out`, `checked_out_time`, `params`, `language`) VALUES (1, 0, 0, 0, 1, 0, '', 'ROOT', 0, '', '', '', 'root', 'root', '', '0000-00-00 00:00:00', 0, 0, '0000-00-00 00:00:00', '', '*');
Mogelijk kunt u deze pagina niet bezoeken wegens:

een verouderde bladwijzer/favoriet
een zoekmachine heeft een verouderde lijst van deze website
een fout getypt adres
u heeft geen toegang tot deze pagina
De gegeven bron is niet gevonden.
Er is een fout opgetreden tijdens het verwerken van uw verzoek.
Probeer één van de volgende pagina's:

Startpagina
Als de problemen blijven bestaan, neem dan aub contact op met de systeembeheerder van deze website en rapporteer de onderstaande fout.

Duplicate entry '1' for key 'PRIMARY' SQL=INSERT INTO `uz0i2_phocaguestbook_items` (`id`, `catid`, `parent_id`, `lft`, `rgt`, `level`, `path`, `username`, `userid`, `email`, `homesite`, `ip`, `title`, `alias`, `content`, `date`, `published`, `checked_out`, `checked_out_time`, `params`, `language`) VALUES (1, 0, 0, 0, 1, 0, '', 'ROOT', 0, '', '', '', 'root', 'root', '', '0000-00-00 00:00:00', 0, 0, '0000-00-00 00:00:00', '', '*');

Re: Problem after migrating from 2.5 to 3.4.2

Posted: 05 Jul 2015, 23:25
by Jan

Re: Problem after migrating from 2.5 to 3.4.2

Posted: 06 Jul 2015, 00:03
by adpc
Hi Jan,

Yes, I followed that guide, all the rest works well, except the most important thing, posting a new message on frontend.
If I post a message on backend it works, but it is not sorted on his date, it is the last message on the last page.. I could move it to the first page by changing the "left" and "right" in database and let these number follow on the message before that (example: last migrated message is 163,164, then I changed the new post to 165,166)

Maybe this problem is the issue why posting on frontend gives this message?

Thanks for your fast reply.

Cedric

Re: Problem after migrating from 2.5 to 3.4.2

Posted: 11 Jul 2015, 13:58
by Jan
Hi, no this should be not the problem, as the script just takes a look for last numbers and will paste new posts with higher numbers :idea:

I am testing it now, getting standard behaviour - when I paste the post in backend this will be displayed as first in the list.

Did you check if the sorting of list in backend in right?

The problem by the message is not the ordering but the ID, if you have migrated, you get the ID in your items and it cannot paste the "first" message into system because there is one with the same ID.

Which version of Phoca Guestbook you are running, testing now the latest with all the possible options ( 3.0.4) and get no such problem:

1) the ID for primary key is never defined as it is autoincrement, so I don't get any problem with duplicate
2) all the messages I add are set Ok with ordering (even I had all posts migrated :idea: )

Hmm, really no idea what could be the problem for this :Idea:

Jan

Re: Problem after migrating from 2.5 to 3.4.2

Posted: 11 Jul 2015, 15:37
by adpc
Hi Jan,

Thanks for reply. If I add new in backend it gets a right ID, date (So it sorts as the newest post there); But in database lft and rgt started again at 1,2 so in that way it is not the newest post on frontend (as I am already at 164,165(before migration)). Changing it in database and set lft rgt OK, sets the post as new on frontend, but this is a huge work for all the messages..
That is a really weird problem, together with the posting issue on frontend :/

Thanks!
Cedric

Re: Problem after migrating from 2.5 to 3.4.2

Posted: 12 Jul 2015, 12:03
by Jan
Hmmm, :-(, I really cannot say what went wrong there :-(

Re: Problem after migrating from 2.5 to 3.4.2

Posted: 12 Jul 2015, 12:44
by adpc
Hi Jan,

Just did the migration with the same messages on a new Joomla installation @Localhost. Result: posting on frontend works here, but new messages started with LFT & RGT from the beginning, so in that case he adds them at the end. (Just like I add them on my Original site on the backend)
Here on the images you can check it (posts on website with date at last page, and how it looks on database - ELLEN is normally the first message):
Image & Image
Did you not encounter the problem that LFT & RGT started from 1,2 when you tried to migrating?
I think if there is a way to let them count normally, I could remove everything from PhocaGuestbook of my website, and start over?
And in worst case, I thought to export the old messages to an article. And after that start over with PhocaGuestbook from 0, if this is possible?
Already a lot of thanks!

Cedric

Re: Problem after migrating from 2.5 to 3.4.2

Posted: 15 Jul 2015, 00:25
by Jan
Hi, when you change the ordering in frontend, how this will be ordered? Not sure what could be the problem there, but maybe the easiest solution is to change the ordering in frotend (but if the old post will be different to new, maybe this will not help, so maybe the ordering needs to be changed when making the migration :idea: ) but I really cannot find the problem as testing and get the ordering OK :-(

Jan

Re: Problem after migrating from 2.5 to 3.4.2

Posted: 15 Jul 2015, 11:58
by adpc
Hi, changing the "order by" in the menu-item (only place where I see option to change order) doesn't do anything. Even when I "ask" to order by "username", nothing happens :idea:
Thanks

Re: Problem after migrating from 2.5 to 3.4.2

Posted: 23 Jul 2015, 23:51
by Jan
Hmmmm, really, really no idea, I have made the migration on test server from latest 2.5 version to 3.4.3, tested with some posts and then everything all Ok on my test server. I cannot say what can be wrong there. I think the guide is OK, it was created by user who did the migration on different sites and tested, really no idea :-(

Jan