Visvanath Ratnaweera

Hi Paul

Thanks for pointing out . I checked config-dist.php but missed it. So '$CFG->site_is_public = false;' answers my question. Thanks a lot.

P.S. The flurry of off-topics: Leaving all the "non-scientific" guess work aside, if this hub/errorconnect develop to be a (new) frequent problem, it will be a hard one for most of the newcomers because it requires deletion of information on either side - in Moodle and in HQ. As Ken already pointed out, this is future. It is fully OK with me to leave the future alone.

<rant>I hear an army of marketing recruits looking for work.

I know, it is mean, the world says FOSS need more marketing. But when they are there, they annoy some. When I think of it, the marketing attracts the clueless and annoy the die-hard. The site registration has the potential being an example. But we don't want more of these: 'Firefox is Fine. The People Running It are Not'. Or do we?</rant>

Ken, you and me will find workarounds. The other cases you mention, don't interest me. I put the rant above, so that you know have a short answer and know why I avoid discussing the root cause of the problem. Pl. understand if I don't re-visit this thread. 

Dear Mary

Thanks for coordinating, resp. pointing out to the procedure to follow: https://docs.moodle.org/en/Site_registration#I_can't_register_my_cloned_site. With that the immediate problem could be SOLVED - but partly.

I still think that the site registration is becoming more and more a compulsory part of the installation/upgrade procedure. There must be a way of bypassing this, like a flag in the config.php.

I must have taken a wrong mod/scorm/. Got the identical code downloaded and replaced the mod/scorm/ with it. Matter RESOLVED.