New answers tagged force.com-sites
2
Sites cannot be packaged. You can package all other resources on which your site depends like visualforce pages or lightning components.
To deploy sites to the org there will be some manual steps required in the org and it is adviced to provide a post install instruction documents to the customers on how to set these sites up.
0
Please modify your page to use the SLDS Grid System. This will help you in building your page in mobile-first approach.
This page will provide you more details with a sample reference.
0
I was able to resolve it.
I captured the current page context at Custom Change Password page as below -
window.location.href = '{!$Page.ChangePasswordPage}?startUrl={!URLENCODE($CurrentPage.parameters.retURL)}';
Retrieved it at customized change password page as below -
startUrl = System.currentPageReference().getParameters().get('startURL');
And to ...
0
This screenshot shows a GACK Error Id response from Salesforce.
Basically, something went wrong internally and they just returned an error code that can be used to track the cause.
However, the only current official method to decode that error code is to contact Salesforce support via a case.
Please consider voting for the Salesforce Idea Provide a public ...
3
Depends a little whether you just need a token you can query for in a separate field, or something you can actually decrypt and read the id
Assuming the latter, you need to create a key, store it somewhere and then use it to encrypt and decrypt
e.g. create a key that is the right length and store the string somewhere safe:
Datetime dt = system.now();
String ...
2
After a painful 2 week trial and error dance with Salesforce Support (Case: #26307915), we learned that we have to do something very unintuitive.
It's a setting in the Dev Hub org which needs to be enabled.
Setup > Communities Settings > Enable ExperienceBundle Metadata API
We don't know why and it even worked after we disabled it.
0
Seems my assumption was correct.
After contacting SF again and getting the runaround that it was not their issue we showed them the nslookup that proved the URLs were pointing to different instance. When they saw that they escalated it and it was resolved shortly thereafter.
If you run into this situation, the quickest path to getting them to fix it is to ...
1
Found the solution of it, the issue was because of the permissions on site, field permission was missing.
Top 50 recent answers are included
