EOS help
- SissyChris76
- Explorer

- Posts: 25
- Joined: Sat Mar 02, 2019 9:53 am
- Gender: Male
- Sexual Orientation: Open to new ideas!
- I am a: Switch
- Location: UK
-
Philocalist
- Explorer

- Posts: 51
- Joined: Mon Dec 03, 2018 8:30 pm
- Gender: Male
- Sexual Orientation: Straight
Re: EOS help
I do not really see the inner workings from here.
What I would need you to do is to go to the backwards cirle arrow symbol and send me the json file (which is essentially the backup).
- SissyChris76
- Explorer

- Posts: 25
- Joined: Sat Mar 02, 2019 9:53 am
- Gender: Male
- Sexual Orientation: Open to new ideas!
- I am a: Switch
- Location: UK
Re: EOS help
How do I send you the JSON file?
-
RemiHiyama
- Explorer At Heart

- Posts: 203
- Joined: Thu Feb 28, 2019 3:30 pm
- I am a: Switch
Re: EOS help
Are you talking about the way it gets stuck on PAGE54-1?
Viewing in chrome, it gives me this error:
As far as I've been able to tell, this always means you have a locator - either for an image or an audio action - pointing to a file that doesn't actually exist in your tease. And not in the page where you first get the error, but one a couple pages after it. (The preloader, as the name implies, is loading things for pages you haven't reached yet.)
I don't know if the number of pages in the future it looks is always the same though, but you can find the problem page by working backwards - find a page later in the chain that works, then jump to the one before it, then the one before it, and so on until you find one that gives an error message, and that should be the one with the problem. Of course this is more difficult if you have branching logic, have pages that rely on variables being set or javascript being called, and so forth...
Viewing in chrome, it gives me this error:
Code: Select all
Preloader.js:16 Uncaught (in promise) TypeError: Cannot read property 'hash' of undefined
at e.value (Preloader.js:16)
at N (play.js:12)
at e (EosHost.js:155)
at EosHost.js:234
at Array.map (<anonymous>)
at n.value (EosHost.js:234)
at Object.n.<computed> [as preload] (EosHost.js:187)
at EosHost.js:249
at Array.forEach (<anonymous>)
at EosHost.js:248I don't know if the number of pages in the future it looks is always the same though, but you can find the problem page by working backwards - find a page later in the chain that works, then jump to the one before it, then the one before it, and so on until you find one that gives an error message, and that should be the one with the problem. Of course this is more difficult if you have branching logic, have pages that rely on variables being set or javascript being called, and so forth...
Auto: Replaces selected instances of the word "not" with the word "definitely".
- SissyChris76
- Explorer

- Posts: 25
- Joined: Sat Mar 02, 2019 9:53 am
- Gender: Male
- Sexual Orientation: Open to new ideas!
- I am a: Switch
- Location: UK
Re: EOS help
Wow thanks for that, I'll check that out, I really appreciate your time with this!RemiHiyama wrote: Mon Jun 22, 2020 6:16 pm Are you talking about the way it gets stuck on PAGE54-1?
Viewing in chrome, it gives me this error:
As far as I've been able to tell, this always means you have a locator - either for an image or an audio action - pointing to a file that doesn't actually exist in your tease. And not in the page where you first get the error, but one a couple pages after it. (The preloader, as the name implies, is loading things for pages you haven't reached yet.)Code: Select all
Preloader.js:16 Uncaught (in promise) TypeError: Cannot read property 'hash' of undefined at e.value (Preloader.js:16) at N (play.js:12) at e (EosHost.js:155) at EosHost.js:234 at Array.map (<anonymous>) at n.value (EosHost.js:234) at Object.n.<computed> [as preload] (EosHost.js:187) at EosHost.js:249 at Array.forEach (<anonymous>) at EosHost.js:248
I don't know if the number of pages in the future it looks is always the same though, but you can find the problem page by working backwards - find a page later in the chain that works, then jump to the one before it, then the one before it, and so on until you find one that gives an error message, and that should be the one with the problem. Of course this is more difficult if you have branching logic, have pages that rely on variables being set or javascript being called, and so forth...
- SissyChris76
- Explorer

- Posts: 25
- Joined: Sat Mar 02, 2019 9:53 am
- Gender: Male
- Sexual Orientation: Open to new ideas!
- I am a: Switch
- Location: UK
Re: EOS help
I guess it was obvious what to do, I just deleted the few pages that existed after the issue. Taught me the lesson to test after each page created. Thst way, I'll never get ahead of myself lol. Thanks again for your advice. I was wondering, has anyone yet written a manual ourt guide? Peace
