Skip to main content
Nintex Community Menu Bar
Question

force.com site not loading resources

  • July 11, 2024
  • 7 replies
  • 21 views

Forum|alt.badge.img+18

I get a blank page and all these console errors on a force.com site:

I’ve done sites before successfully, but struggling with this one. Any ideas?

7 replies

Forum|alt.badge.img+18
  • Author
  • July 11, 2024

Hmm.

I changed the domain path for my site from /s to /public, and now everything works.
Is there some reason that we have to use more than one character for the path? If so, please document?


Forum|alt.badge.img+10
  • Nintex Employee
  • July 11, 2024

Is /s a path that had been working in the past? I’m not sure there is a required minimum number of characters. When those console errors were present, were you able to click on them to drill down to get any more details about why the requests were aborted?


Forum|alt.badge.img+18
  • Author
  • July 11, 2024

/s never worked. There were a couple that I could drill down on, but I don’t recall exactly what the problem was. The 404 error I could drill down on, but that one I expected (I have the wrong name for a css resource embeded in the theme). I couldn’t drill down on most of the 503 errors.


Forum|alt.badge.img+18
  • Author
  • July 11, 2024

Looks like I still had the window open. Here’s as much as I could drill down:


Forum|alt.badge.img+10
  • Nintex Employee
  • July 11, 2024

Thank you for the additional information. Just to be sure - does the Guest User have Skuid Page Viewer permissions? See Step 5: https://docs.skuid.com/latest/en/skuid/deploy/salesforce/visualforce/force-com-site.html


Forum|alt.badge.img+18
  • Author
  • July 11, 2024

Mark,

Everything is working now that I stitched the domain path to /public instead of /s.
That one change made the difference.


Forum|alt.badge.img+5

Hey Matt or Mark,

I’m having what might be a similar problem and I’m wondering if you’ve seen anything like it. See my topic:

https://community.skuid.com/t/problem-loading-ckeditor-js-for-rich-text-field

This problem started only after an upgrade to 11.0.3.

Thanks,
Tony