Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We’re working on a Salesforce managed package that contains visualforce pages that are to be published on a Salesforce site.
When testing, we can access those pages at http://example.force.com/pagename
But when installing the managed package on a testing org, we can only access those pages is prepending the package namespace, http://example.force.com/namespace__pagename
How can I make the pages accessible at /pagename even when accessing from a managed package instalation?
A URL rewriter might possibly work but I’m pretty sure you’ll find no way around this — the point of the namespaces is to prevent naming conflicts between packages, being able to remove it from the page URL would mean there’s nothing to stop your package from conflicting with other packages or custom VF pages in the orgs the package is installed on.