Portal links invalid after republish

Posted by Rollbase User on 06-Jun-2011 01:30

Hi Guys I'm not a portal expert, but I set up a portal which does not require login that basically just allows the client to view the status of their application. we e-mail the client at the beginning, and tell them to hang on to the link. My link url originally looked like this: {!#PORTAL.17129448.17445350#url}&id={!id} which evaluates to: https://www.rollbase.com/prod1/portal/portal.jsp?c=11771965&p=17523314&g=17523345&id=12345678 - I was simply providing the link to the portal page, and appending the id but after I republish every time, the link becomes invalid because the g parameter (page id) changes, so the clients links don't work any more. So then I thought I would try {!#PORTAL.17523314.emailUrl} and set the default portal page to my 'view application page', however, can I need to pass the ID like this: {!#PORTAL.17523314.emailUrl}&id={!id} However this evaluates to: https://www.rollbase.com/prod1/portal/portal.jsp?c=11771965&p=17523314&g=17523345 (The ID is

All Replies

Posted by Admin on 06-Jun-2011 11:13

How exactly ID was discarded during installation? Installer will not modify you templates in any way.

Posted by Admin on 09-Jun-2011 18:32

No, I didn't say that the ideas discarded during installation (publish).... there are two different matters here:



1) if I try to link directly to a portal page, using



{!#PORTAL.17129448.17445350#url}&id={!id}



Then the link that we give to the user becomes invalid after publish because the page id changes (the g=xxxx parameter).



to try to get around this, I tried the following:



2) Different Matter: if I try to link to the portal using the email url



{!#PORTAL.17523314.emailUrl}&id={!id}



then some sort of internal redirect occurs to the primary page, but when this happens, the ID is discarded ( nothing to do with publish... this happens immediately).



does this make sense?

Posted by Admin on 09-Jun-2011 23:05

It does not matter if page ID changes since template token {!#PORTAL.17129448.17445350#url} uses original IDs which do not change during installation.



If you see that template token becomes invalid after installation it's a bug. I should test this.

This thread is closed