You need to sign in to do that
Don't have an account?
Strange Behavior on Overridden View/Edit link for Portal Users logging in via a Sites page
I have a Customer Portal where I've created a Site for the users to login from. This problem only appears when logging into the Portal via the Site. If they login using the standard Portal URL there is no problem, but of course we want the users to login via the Sites page.
If I override the VIEW or EDIT links on a Custom Object, when the user clicks the EDIT link or the item NAME in a View, they get an error for "Page Not Found" (the error below is a VIEW link error):
Page Not Found: /portalpage/a1CQ0000000ouMS/e
If I remove the override for the VIEW, when the user clicks the link it opens up the page properly, and it even shows the exact same URL that appeared in the error message.
Very bizzarre. The page exists either way, but for some reason the overridden link is creating an issue.
I confirmed that the VisualForce page used in the override is available to the Portal User and Sites user Profiles and checked any other security setting I can think of. Doesn't seem to be a security setting, especially given the odd page not found error, but who knows.
Is there a way I can override the VIEW/EDIT page for a Custom Object and have that override work for Portal Users that login via a Sites page?
Best Regards,
Mike
I was able to find a creative work-around for this. In general, I did not want to rebuild every list and page using VisualForce just to get the links to work on my portal-site. So, to work-around the PageNotFound error, I created a custom PageNotFound VisualForce page that detects the "error" and just redirects the user to the correct page:
Best Regards,
Mike
I was having the same problem and this worked for me. Thanks!
we will look in to this. It should work without the workaround
Thanks. In my case, I have a custom object with an overridden edit button linking to a visualforce page. As Mike said, it works for regular users, but not on the Customer Portal. I used the following modification of Mike's example to get it working:
I will be happy to share further access to our code if you have any questions.
Regards,
Rich
We have logged a bug for this and working on it. You shouldn't need to do any workaround it should just work if you overwrite the buttons with a visualforce pages.