Integrity Check hanging after upgrading to new Site Builder

@iamtimbo
8 years ago
301 posts

Hello!

Finally bit the bullet, and have upgraded to 'new' Site Builder. All seemed fine, but when doing an integrity check, it hangs. Given it an hour each time. Looking at the log, it has the following:

Array
(
    [error] => Query Error: Duplicate entry '26' for key 'PRIMARY'
    [_post] => Array
        (
            [_uri] => /core/integrity_check_save/__ajax=1
            [jr_html_form_token] => 4ceadd03ac0ab00ab077f080c16adf24
            [jr_html_form_profile_id] => 1
            [jr_html_modal_token] => bc802aba0fba5201c232dc937291db5d
            [validate_modules] => on
            [validate_skins] => on
            [repair_modules] => on
            [repair_tables] => on
            [optimize_tables] => on
            [fcsid] => kf62svuefevnoqkf9384hu2vk0
            [_ga] => GA1.3.1815655662.1479298061
            [auto925354006a44] => 1-587bfa8f688d717b0e7c47a1aea98e09
            [jrcore_pager_rows] => 100
            [jr_location_url] => http://ourtownstory.co.uk/sbcore/widget_order_update/l1-location-1/__ajax=1
            [sess925354006a44] => deb514982ed54edb904698ff0dc0cc30
            [sc_is_visitor_unique] => rx10365420.1480521225.741B7E7F67954FF01F390196BBD8A832.7.6.5.5.5.5.5.3.1
            [__atuvc] => 1246, 3747, 12948
            [__atuvs] => 583edfa8da445d56080
            [_asomcnc] => 1
            [module_url] => core
            [module] => jrCore
            [option] => integrity_check_save
            [__ajax] => 1
        )

    [query] => INSERT INTO jr_jrsitebuilder_menu (menu_id,  menu_updated,  menu_parent_id,  menu_order,  menu_title,  menu_url,  menu_group)
                        VALUES ('26',  UNIX_TIMESTAMP(),  '0',  '30',  'England I - M',  'england-i-m',  'all')
)

As a result, I don't think it is importing the things it is supposed to; pages linked to in the drop-down menu that existed before are now asking me to create them.

Any thoughts?

EDIT: it also means it isn't 'turning off' old Site Builder. Which I think is supposed to happen.
updated by @iamtimbo: 03/28/17 11:05:43PM

@brian
8 years ago
10,148 posts

Wow - I had no idea someone was still using the "old" site builder. The problem here is that menu_id is an AUTO_INCREMENT column, but has been defined as id "26", which must already exist.

Michael built the importer for the old to new, so he would be the best to check on this. Are you able to disable site builder and complete the integrity check or is it hanging at the same point every time?

--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

@iamtimbo
8 years ago
301 posts

Had no permanent Internet connection for the last year, so not had the chance! Trying to prepare myself for 6 now....

It hangs if old site builder is disabled, haven't tried it with disabling new site builder - is that what you meant?

@brian
8 years ago
10,148 posts

iamtimbo:
Had no permanent Internet connection for the last year, so not had the chance! Trying to prepare myself for 6 now....

It hangs if old site builder is disabled, haven't tried it with disabling new site builder - is that what you meant?

The integrity Check should never hang, so it sounds like the importer in the NEW Site Builder needs to be fixed up. I'll get a ticket open on it and we will check this out.

Are you locked out of your site? If so, disable BOTH the old and new and run the integrity check if you can - that should fix things up for everything EXCEPT site builder - but it will at least get things working for you.

Let me know if that helps.

--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

@iamtimbo
8 years ago
301 posts

Not locked out. Have disabled new SB, re-enabled old SB, and integrity checked, and it's absolutely fine.

Will leave it as is for the time being.

updated by @iamtimbo: 11/30/16 10:38:16PM

@michael
8 years ago
7,714 posts

not a good idea to go back to the old site builder after installing the new. It makes it even harder to upgrade.

Remember this from our last talk about it:
https://www.jamroom.net/the-jamroom-network/forum/new_posts/39836/upgrading-from-very-old-site-builder/search_string=old+site+builder

michael:
Its real hard to say what will happen without doing it, then fixing the results. Probably after the import you will need to fiddle with things.

The worst thing to do is to change it, see things are not quite right and immediately revert because then you'll have an extra step (which involves database manipulation) next time you want to try, so set aside a few hours just in case. do it, and work through any issues after the transition.

If it all does fail and its not going to work, you can turn off the new sitebuilder module and turn back on the old ones and you will be back to where you are now.

The correct thing to do is turn off the old site builder after the new one is upgraded.

Then check for issues, fix the issues, and delete all the old modules of site builder. I can't remember specifics, its pretty old now.

@iamtimbo
8 years ago
301 posts

Hi, Michael,

I do indeed remember the conversation, and set aside some time to do this.

I put the site into maintenance mode, and having checked the documentation and forums as to whether old SB needed to be switched off, but couldn't find anything. From memory I recalled that the switch off process would be handled by the integrity check.

The home page was pretty messed up, with widgets and what have you all over the place, but rather than just "immediately revert", I took the time to move/delete/rewrite widgets and templates - and, for what it's worth, it was all easier than I expected, and you were right, I should have borne with it the first time.

Happy with the way I had it, I finished up my session by doing what I always do; resetting the caches and running an integrity check. It was at that point that the first hang occurred. I gave it a considerable time longer than it usually takes, but, having concluded that the connection had dropped, or that I should have disabled old SB, I disabled it and tried again. I gave it an hour with the same result.

As on the PC I was using the home page appeared to be working, I left new SB active, and old SB inactive. It was only on the commute home, when I had a chance to post about experience from my iPad, I realised that the pages that the root drop-down menus link to were inviting me to create them. I have to have these, as the drop downs don't 'drop down' consistently on iPad, and the pages are workaround indexes.

I left the site in Construction Mode until 2300 GMT (10 hours after I started), but with nothing more to go on, and the site unnavigable for tablet users, I felt I had no choice but to reactivate old SB. I'm certainly not complaining, just perhaps objecting to the assertion that I immediately reverted back!

I will have to have another bash another day, and this time will turn off old SB after activating new SB. I assume it's at that stage I should run the integrity check.

Thanks as ever for your help.
updated by @iamtimbo: 12/01/16 06:32:51AM

@brian
8 years ago
10,148 posts

The integrity check should not take that long - you can just refresh your browser and re-run it. You can also try reloading the Jamroom 6.0.0 core from the Marketplace (ACP -> Core -> Marketplace -> Tools -> Reload Modules and Skins). Shortly after the initial release I pushed a small change to the core that increases the integrity check "timeout" length, which could help here.

--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

@iamtimbo
8 years ago
301 posts

It seemed too long to me, but I'm always haunted by the 'be patient' warning!

I need to do the skin clone and check it through first, then I'll go to 6. So excited about cards in the activity feed!

(on that note, I had been going to add the css for embedded tweets and fb posts. Will that not be necessary with 6?)

@brian
8 years ago
10,148 posts

iamtimbo:
(on that note, I had been going to add the css for embedded tweets and fb posts. Will that not be necessary with 6?)

I'm not quite sure what you mean - do you mean you are embedding Facebook and Twitter posts in your Jamroom timeline? If so, then yes - the scanner will bring in the OG tags for the remote page when creating the "card". It will not however bring in any CSS, as it is designed to match the look and feel of the Jamroom skin - NOT Facebook.

For Twitter, I believe they use Twitter cards which are not supported - yet. We have an open ticket to get Twitter card support in, as well as migrate the Open Graph tag support OUT of the ShareThis module and into it's own module.

Let me know if that helps.

--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

@iamtimbo
8 years ago
301 posts

That's exactly it. Sounds perfect.