images base path / where ezimage defined?

Next topic

Author	Message
Scot Wilcoxon	Sunday 06 April 2003 2:43:20 pm I'm trying to make a site one level down: example.com/info rather than immediately under a domain. Others have mentioned trying to use example.com/~username. The stylesheets and images directories are not found, as they are looking for "design" in the root directory which is one level too high (/var/www/html/design rather than /var/www/html/ezpublish/design). I see where wwwDir is set, but adding an "else" to take the first part of the path (/info/) works for the missing directories but makes generated links be /info/info/. (I recognize that wwwDir is set to before the .ini files are read thus no configuration can be used at that point) Apparently I have to make the "ezimage" template operator recognize the situation (for images -- stylesheet I'll deal with next). I see the code is in kernel/common/ezurloperator.php. What would seem to be the best way of dealing with this? Perhaps by seeing that SiteURL contains a path after the site name? Or does that violate a design concept?

Author

Message

Sunday 06 April 2003 2:43:20 pm

I'm trying to make a site one level down: example.com/info rather than immediately under a domain. Others have mentioned trying to use example.com/~username.

The stylesheets and images directories are not found, as they are looking for "design" in the root directory which is one level too high (/var/www/html/design rather than /var/www/html/ezpublish/design).

I see where wwwDir is set, but adding an "else" to take the first part of the path (/info/) works for the missing directories but makes generated links be /info/info/. (I recognize that wwwDir is set to before the .ini files are read thus no configuration can be used at that point)

Apparently I have to make the "ezimage" template operator recognize the situation (for images -- stylesheet I'll deal with next). I see the code is in kernel/common/ezurloperator.php.

What would seem to be the best way of dealing with this? Perhaps by seeing that SiteURL contains a path after the site name? Or does that violate a design concept?