Forums / Setup & design / Dumb question on path configuration

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Dumb question on path configuration

Author Message

John Blossom

Thursday 22 May 2003 3:43:21 am

I have been working with Marlabs to get EZ3 configured, with some issues, unfortunately. The way that it is configured currently I get ugly URLs, not the nicely formed URLs that I see on your own site and other sites. for example, from my root (http://www.edgeleader.com), if I click on a folder named "testfold" I get a URL:

http://www.edgeleader.com/user/content/view/full/19/?PHPSESSID=d1218374ba86ab312b299fb119262b4d

instead of something like:
http://www.edgeleader.com/content/testfold

How do I configure EZ3 to do this properly? Related question: do I HAVE to have the additional "geek" layers show up in my URLs when all I want my users to see is the natural progression of folders, such as, in this example:
http://www.edgeleader.com/testfold.

Many Thanks,
John Blossom

Selmah Maxim

Thursday 22 May 2003 5:25:47 am

Hi ..

1. modify siti.ini

[URLTranslator]
# Use either enabled or disabled
Translation=enabled
# Enable this if you want to percieve the url as a path element
# for the node tree. By entering the path in the url and ending it
# with a .html you will get the correct node.
NodeTranslator=enabled

2. give the links like this :
<a href={$node.url_alias|ezurl}>link</a>

thats it !

John Blossom

Friday 23 May 2003 8:01:42 am

Selmah,

Thanks for your reply. Oddly (...??), when I went to check the site.ini file, the parameters that you mentioned were indeed set the way that you had suggested, and the URLs were looking a little more nominal. now a test foleder off of the root directory comes up:
http://www.edgeleader.com/user/content/view/full/19/

I tried your snip of code in the template, but it only refers to the current node. I will dig more on this to educate myself, but the simple thing I'm trying to do is to have a template automatically build an index of folders that refers to the true folder structure via folder aliases.

Best,
John Blossom