In sites installed in a dir (or path) relative paths don't work:
for example: www.domain.org/aiki  -> home base for aiki installation.
a relative "/foo"  url is translated to  www.mysite.org/foo NOT 
www.mysite.org/aiki/foo.

PD:off course, there are simple solution: a subdomain.

-- 
You received this bug notification because you are a member of Aiki
Framework Developers, which is subscribed to aikiframework.
https://bugs.launchpad.net/bugs/912632

Title:
  need some shorthand for relative urls using views, sites and language
  paths

Status in Aiki Framework:
  New

Bug description:
  The old aiki simply had a global variable [root] for defining an
  absolute url for paths in aiki. This is problematic because if used,
  it makes sites less portable.

  Thus, rg1024 completed the concept that aiki installations can have
  different sites, views, and languages. And, he came up with a
  shorthand [route]  which make absolute urls with the first adding on
  the current site, view or language.

  However, this [route] is an absolute path with the domain name
  included.

  We need some shorthand that makes an on-domain absolute path but
  autofills in the site, view and language path at the beginning of the
  url.

  So, instead of something like http://openclipart.org/en/my/path

  Can use something like [route-local] and receive /en/my/path

  Does this make sense?

To manage notifications about this bug go to:
https://bugs.launchpad.net/aikiframework/+bug/912632/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~aikiframework-devel
Post to     : aikiframework-devel@lists.launchpad.net
Unsubscribe : https://launchpad.net/~aikiframework-devel
More help   : https://help.launchpad.net/ListHelp

Reply via email to