force.com site not loading resources

Matt SonesMatt Sones ✭✭
edited February 4 in Problems
I get a blank page and all these console errors on a force.com site:

image

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

Comments

  • Matt SonesMatt Sones ✭✭
    edited February 4
    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?
  • Mark DeSimoneMark DeSimone 🛠️ 
    edited December 2017
    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?
  • Matt SonesMatt Sones ✭✭
    edited December 2017
    /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.
  • Matt SonesMatt Sones ✭✭
    edited December 2017
    Looks like I still had the window open. Here's as much as I could drill down:
    image
  • Mark DeSimoneMark DeSimone 🛠️ 
    edited December 2017
    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
  • Matt SonesMatt Sones ✭✭
    edited December 2017
    Mark,

    Everything is working now that I stitched the domain path to /public instead of /s.
    That one change made the difference.
  • edited January 2018
    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/skuid/topics/problem-loading-ckeditor-js-for-rich-text-field

    This problem started only after an upgrade to 11.0.3.

    Thanks,
    Tony
Sign In or Register to comment.