Oh … and I forgot to mention, I’ve tried setting up the VisualForce page both as a direct load of the page, and through the Page Assignment redirects. No different in behavior either way. Here is the current version of the Learning Center tab VisualForce page that is using Page Assignments…

<apex:page standardController="Learning_Series__c" recordsetvar="l" 

extensions="skuid.Redirects" showChat="true" docType="html-5.0" readonly="true" showheader="true" sidebar="false" action="{!IF(canUseSkuid,'',redirect)}" title="{!$ObjectType.Learning_Series__c.labelPlural}"> <skuid:page actiontype="Tab" objecttype="Learning_Series__c"/> </apex:page>

* bump *

Any thoughts on how to debug why the VisualForce page is returning an error?  All I can tell from the logs is that a couple Skuid SOQL calls are made - so at least some of the Skuid code is running, and I don’t see how my code can cause this failure (though maybe my configuration can?)  

Thanks…

- Chris

Chris, I’m pretty stumped on this one. Seems like there’s 2 separate issues, which may need to be treated separately, but they may be related.

I think you should log the first one as something like “Switching communities incorrectly sends user to local rather than namespaced Visualforce Page” — Salesforce’s Community switching Servlet is definitely generating the wrong URL (unidesk--c.na5.visual.force.com rather than unidesk--skuid.na5.visual.force.com), this is not a Skuid issue.

And you should definitely log a case about the 2nd issue, with the VF page not loading, to get Salesforce to give you the internal Gack description of the error message you’re receiving: Salesforce System Error: 472535200-1330485 (-921938118) (-921938118). Sometimes the internal error messages help provide a clue to what’s going wrong — sometimes they don’t. 

Hope that helps!

Thanks for looking at it Zach.  I’ve spent some more time trying to get ready to submit to Salesforce for support where I could show that it has nothing to do with Skuid, but I seem unable to do this.  Simply by changing the Page to use standard VF code, it works just fine.  No more errors.

But if the page has the Skuid code (for direct page load, or page load via page assignment) I get the error.  And all my communites show this failure, not just by new ones (as I originally thought) - though it is more obvious now with the “generic” VF code as those pages load fine, and when I switch to the original community page I now get the failure.

This makes it hard to show to Salesforce that this isn’t a Skuid problem.  Any ideas how I might reproduce a failure that doesn’t involve Skuid?

Do note that we see the SOQL statements accessing Skuid tables in the debug log, prior to the error, so we know that some of the code must be running.  So I wonder if maybe this is some interaction still between Skuid and communities / community switching?

Thanks!

- Chris

Chris, in my testing in your org, I have had the Community switching fail and throw (variously) Internal Server Errors or the Force.com Sites error page — even when the VF page is just your simple “Hello world” example.

I think that the root error has to do with how Salesforce Communities are (a) storing / remembering the last tab / URL a user was on in a particular Community, and then returning to that tab when you return to that Community (b) switching between VF pages different namespaces, which is where Skuid comes in to play, in the sense that Skuid is distributed as a managed package, which has a namespace, and so any time you go to a VF page included with Skuid the URLs have to switch into a different domain in order to correctly resolve — and something in here is not working correctly, as your examples show above, where the URL goes to unidesk–c.na5.visual.force.com rather than unidesk–skuid.na5.visual.force.com — it may be that the Community URL rememberer is not correctly storing the right Domain of the user’s last tab. I’m not sure, but I think that this is enough to go on for sending the error report to Salesforce.