Error with Skuid Page in Lightning Community Builder
I have some simple Skuid tables that I am embedding into my Napili Community via the Community Builder and Skuid custom component. These were functioning correctly yesterday, but today I'm no longer able to see the pages in either sandbox or production. I received this error in production:
"Cannot add Inline Javascript in the Lightning Runtime, and no Page Support File was found or there was a timeout."
We are trying to launch our community next week, and these features are critical. Any advice on this would be appreciated.
Thanks!
Eulogio
"Cannot add Inline Javascript in the Lightning Runtime, and no Page Support File was found or there was a timeout."
We are trying to launch our community next week, and these features are critical. Any advice on this would be appreciated.
Thanks!
Eulogio
Tagged:
1
Categories
- 7.9K Questions
- 926 Ideas
- 220 Discussion Categories
- 178 General
- 9 Community Feedback
- 3 Community Info
- 18 Knowledge Base
Comments
Is there custom javascript on the pages? If so, do the pages work without it? If so, there is likely a problem with the custom javascript on your page.
Yes I did activate the community this morning, do you think that would cause issues? I'm not sure why that would affect the already active sandbox community though.
My page does have a small amount of javascript, but again this was working in the sandbox before this morning.
Thanks!
Eulogio
Do the pages work without any of it? Absolutely scrapped, do your pages load?
What are you seeing for your pages themselves when a user tries to access the community? We need much more detail to be able to help
Here is a screenshot of what users see in the Community. It simply doesn't show.
Is it a detail page or something attached to an object? The permissions will need to be set to public if it is a public community
Below is what it should look like. Again, it's a pretty straightforward table of info, nothing too fancy about it. It is pulling Contact info.
This page also throws the following error:
I made sure that Contact permissions are enabled. We have another Community that is active that functions correctly with our permissions, but this is the first time we're trying to add a Skuid component to this.
I generated the support file and that removes the error messages, but nothing actually shows up on the page still. Do you think it has anything to do with the gatherer.js script? I notice that the resource URLs it is referring to are incorrect. For example:
This gives me a 503 error. But if I use the correct Community path:
This downloads the resources correctly. I wonder if this other URL is having similar troubles with the links not pointing to the correct path:
What do you think?
Thanks!
Eulogio
It sounds like generating the support files was a necessary step, but there's another unresolved issue to understand. Would you mind telling us your current Skuid release #, and whether you've recently upgraded?
Also, in Chrome's developer tools, sometimes I can find out more information by looking in the Network tab for resources that didn't load, or returned an error. If you can share anything that doesn't look like a '200' that'd be helpful too.
We are currently on 11.2.7. I updated from 11.2.2 this week in hopes of fixing this Community issue.
Using the Network tab, the only non-200 message I see is the one I referenced in the comments above - 503: https://thebroadcenter.force.com/community/resource/skuid__IconsSVG
One thing I'm seeing though is that the page will continuously make a request to
It looks to me that this gatherer.js script is having trouble connecting properly. Am I reading this correctly?
Thanks!
Eulogio
It sounds like there is another relevant piece to the puzzle that we haven't identified yet. Are you able to try using a different Skuid page in this community, perhaps starting with the simplest possible? See if that loads as expected. If so, add things in little by little until your test page resembles the affected page, to see if you can identify what is causing the issue.
Or an alternate method would be to comment out certain elements of your page XML one by one to see if you can determine which one affects whether the page loads. And, if you're comfortable sharing the page XML here, I can see if it causes similar issues in my org (I'll have to remove custom fields and objects).