Portal Engine Questions on portal engine and web parts.
Version 5.x > Portal Engine > Wildcard URLs View modes: 
User avatar
Member
Member
scott_hancock-urmc.rochester - 3/23/2011 12:57:55 PM
   
Wildcard URLs
I've read the section in the Developer's Guide (5.5 r2) about Wildcard URLs but I need a clarification.

I have a url:

http://localhost/abc/Encyclopedia/Content.aspx?ContentTypeID=90&ContentID=x01682

In the Path section of the document properties I've created the Document Alias: /Encyclopedia/Content/{ContentTypeID}/{ContentID}

but this only works if I manually create a new Document alias in the Document aliases section of Document properties (by clicking "Add new alias").

1. Is that how it's supposed to work?
2. What is the difference between the two different document alias sections in the document properties? I read the help but it wasn't clear to me.

It would be nice to have an example with two query string variables in the documentation.

Thanks,
Scott

User avatar
Kentico Developer
Kentico Developer
kentico_ivanat - 3/24/2011 6:00:03 AM
   
RE:Wildcard URLs
Hi,

if you have a URL: http://localhost/abc/Encyclopedia/Content/90/x01682.aspx and set a Document URL path: /abc/Encyclopedia/Content/{ContentTypeID}/{ContentID}

(if the abc is a virtual directory, please use: /Encyclopedia/Content/{ContentTypeID}/{ContentID})

the URL will be changed to:
http://localhost/abc/Encyclopedia/Content.aspx?ContentTypeID=90&ContentID=x01682

There is no need to define new Alias.

You can access query parameters for example using query macros:
{%ContentTypeID%}
{%ContentID%}

Best regards,
Ivana Tomanickova

User avatar
Member
Member
scott_hancock-urmc.rochester - 3/28/2011 7:54:05 AM
   
RE:Wildcard URLs
Thanks,

I realized my mistake. I was not putting the .aspx at the end of the url and that was causing the problem. Creating the new alias eliminates that problem which is why I thought you needed both.

Scott