Pages no longer loading after upgrade to 9.3.3

  • 2
  • Problem
  • Updated 2 years ago
  • Solved
  • (Edited)
After 9.3.3 was pushed, I have been having a lot of problems with my Skuid pages.

Pat Vachon kindly helped me resolve some issues when all of my pages were updated to their original versions.

However, I am still having issues where my pages won't load at all. I am able to edit them in the page builder, and I even grabbed the XML and pasted it into a new page...when when I try to preview...the page never loads.
Photo of Conlan O'Rourke

Conlan O'Rourke

  • 4,066 Points 4k badge 2x thumb

Posted 2 years ago

  • 2
Photo of susan.nordquist

susan.nordquist

  • 354 Points 250 badge 2x thumb
I experienced a similar problem and when I changed my theme from a custom one to one of the standard ones my pages showed up - not sure if this is the same problem you are having but worth a try.
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 11,732 Points 10k badge 2x thumb
Thank you for following up with this new information. Looking at your screenshot, it appears that the jSignature.min.noconflict.js is throwing errors, rather than an inline snippet. There is also the error above that, regarding the user-agent, and I'm not sure whether that error could be related to the jSignature errors. Since you have the jSignature resource in your org, do you have a way of setting up a simple test page to see if that javascript throws an error in a more stripped-down environment?
Photo of Conlan O'Rourke

Conlan O'Rourke

  • 4,066 Points 4k badge 2x thumb
Hi Mark, yes I just set up a test page with the same JS Resources, and the error continues to throw
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 11,732 Points 10k badge 2x thumb
Could you describe the resources you've got on that page? And is the page throwing the errors intermittently, or every time you load it? Are the errors the same?
Photo of Conlan O'Rourke

Conlan O'Rourke

  • 4,066 Points 4k badge 2x thumb
It's just the In-Line Component JS listed above, and the static resource. The static resource file is a signature capture canvas

File here: https://drive.google.com/file/d/0B1PKG9_1V4XTeE1jdi1hdTdmSVE/view?usp=sharing

Originally downloaded from GitHub here: https://github.com/willowsystems/jSignature
Photo of Conlan O'Rourke

Conlan O'Rourke

  • 4,066 Points 4k badge 2x thumb
And yes, the same error is thrown consistently every time I load the page
Photo of Peter Herzog

Peter Herzog

  • 1,674 Points 1k badge 2x thumb
Related: We are having the same problems and we would like to roll-back one of our sandboxes to pre-brooklyn.  Has anyone tried this?  Is it possible?
Photo of susan.nordquist

susan.nordquist

  • 354 Points 250 badge 2x thumb
Hi Peter - 
Here is some helpful insight (paraphrased) I received yesterday from Karen @skuid:

Regarding rollback: 

The issue with Salesforce's Spring '17 release created problems in installing any version of Skuid. They provided a workaround which has been implemented in Brooklyn Iteration 3 (9.3.3) so currently, customers are only able to install 9.3.3. Even if we could help them uninstall and reinstall (not recommended), we wouldn't be able to get them back on 8.15.8. (from a package install)

Options:

1. They can create a new sandbox off their production org and it should automatically bring the production version of Skuid (Rockaway 10) down with it.  They would be able to package up their Skuid pages in the sandbox they've been working in so they don't lose their development there. They'd be able to unpack those pages in the desired sandbox. Here is a tutorial on how that can be done.

*note: If you have not yet installed skuid on production, you can still do so as long as your production instance is still on Winter '17 and has not been updated to Spring '17

2. A number of bugs from 9.3 have been resolved in 9.3.3 and more will be addressed in Iteration 4 (released 1/26/17, currently available on skuid.com/release website). (you may need to install 9.3.3 into an org before updating to 9.3.4 because of the Spring 17 issue, not positive on this one)

Also, Skuid has an auto-update opt-out list that you may want to put yourself on.  Just send the request to their support email and provide the org ids for the environments you don't want to auto-update.

Hope this helps!

Photo of Jannik Gysi

Jannik Gysi

  • 594 Points 500 badge 2x thumb
Hi Conlan,

First we have to find out, on which jSignature call, you get the error. I assume it's on the second or the third one. Comment out one at a time, until your error doesn't show up again.

If it's the second one, try to use
element.jSignature("clear");
instead of
element.jSignature("reset");
If it's the third one, try to pass some hardcoded data (see below) and let me know if it works, so I can help you further investigating this issue.
element.jSignature("setData", "data:" + "image/jsignature;base30,cVZ1000Y59ce1Gomn1Sla4331222_2Q9aad331000000062344544");
(Edited)
Photo of Conlan O'Rourke

Conlan O'Rourke

  • 4,066 Points 4k badge 2x thumb
Hi Jannik,

Great, thanks. It looks like its the second call that throwing the error...once I commented that second jSignature call, the page loaded fine...although the Sign component didn't load (but I think that's to be expected).

Please advise.

Thanks,

Conlan
Photo of Zach McElrath

Zach McElrath, Employee

  • 50,694 Points 50k badge 2x thumb
Official Response
This may help resolve the error. Anywhere that the following code is used:

$(document).ready(function() {

Replace it with:

$(".nx-page").one("pageload", function() {
Photo of Conlan O'Rourke

Conlan O'Rourke

  • 4,066 Points 4k badge 2x thumb
Excellent, that took care of the issue. Thanks Zach!
Photo of Zach McElrath

Zach McElrath, Employee

  • 50,694 Points 50k badge 2x thumb
Great to hear! Just want to make a note that this is not a change introduced by the Brooklyn / 9.x.x release,  $(document).ready(function(){ ... }) and $(function(){ ... }) have not worked in Page Includes for years now at this point, the only way to reliably have Javascript code run from a Page Include only after Skuid Model initialization is complete is to use the .one("pageload") approach.