search

Picolab / devtools

Repository for KRL Developer Tools
MIT License
6 stars 4 forks source link

child bootstrap fails with new accounts #83

Closed burdettadam closed 8 years ago

burdettadam commented 8 years ago

some how the bootstrap function to check what rulesets are installed fails(installedRulesets line 369 of wrangler.js), returns module not installed error, which causes a bootstrap event which in turn does the same check, but finds the rulesets and says everything is ok. this makes no sense because if the “module" was not installed the rule would not catch the bootstrap event, which it does. So we could have a javascript default that defaults to the wrong prod or dev version sometimes, or an eci that defaults to the wrong eci, or our ajax function is buggy. I added the bootstrap.dev ruleset to the cores to be installed in the child and could not get the error to happen again. This will cause the bootstrap ruleset to be installed twice, but also insure .dev version is installed. We will need to track the problem down further for a proper fix and or understanding.

earlyprogrammer commented 8 years ago

new accounts on the local version get bootstrap rid b507199x1.dev new accounts on the production site get bootstrap rid b506607x15.prod

Updating the bootstrap rid for the production site should fix this problem, I'm not sure where it is or how to do that, app registration stuff?

earlyprogrammer commented 8 years ago

I flushed b506607x15.prod and it seems to be working, so I'm closing this issue. I created a new account on prod site and creating children bootstrapped