Sign Up ›
  • Mohammed Al-Said
  • NEWBIE
  • 0 Points
  • Member since 2017
  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 1
    Replies
0 replies

Remove Instance Names from URLs for documentforce

following the link https://help.salesforce.com/articleView?id=000270912&language=en_US&type=1

Visualforce page with no namespace:
--c.visualforce.com will replace --c..visual.force.com
--c.documentforce.com will replace --c..content.force.com


what I assume for package namespace will be like
Visualforce page with namespace:
--.visualforce.com will replace --..visual.force.com
--.documentforce.com will replace --..content.force.com

now after changing the URL same as document and SF the result are
--.documentforce.com ----------------- not working manage Package
--c.documentforce.com --------------------------------work fine with manage Package

which one do we need to follow for the package namespace?
9 replies

Visualforce Page Links Fail When Critical Update Activated

There is a new critical update called Remove Instance Names From URLs for Visualforce, Community Builder, Site.com Studio, and Content Files.

DANGER! DANGER! DO NOT ACTIVATE!

This changes links for visualforce pages.  <domain name>.visualforce.com replaces <domain name>.<instancename>.visual.force.com.

For whatever reason, this does not work with Visualforce tabs or with buttons that link to visualforce pages.

With the critical update deactivated, the link for visualforce tab is https://<domain name>.<instancename>.visual.force.com/apex/TimeEntryCalendar?sfdc.tabName=01r500000003bNn.

When the critical update is activated, the link for the visualforce tab is https://<domain name>.visualforce.com/apex/TimeEntryCalendar?sfdc.tabName=01r500000003bNn.

The problem is that clicking the "activated" link yields this:
 
This site can’t be reached
<domain name>.visualforce.com’s server IP address could not be found.

In my case, it was a really big problem because the visualforce tab was the default home page. So activating the Critical Update essentially locked all of my users out of salesforce.com. 

This also fails with a simple button link to a visual force page.

If you assign a url to a button or type the link in - /apex/TimeEntryCalendar for instance, it works fine when the update is deactivated.

But activate the update, and it fails on just the simple link.

Problem exists in both Classic and Lightning.

MAJOR SNAFU!