Jan Haderka wrote:
I upgraded our build to use magnolia-module-extended-templating-kit
1.3.1-SNAPSHOT [1.3.1-20100413.143708-1], but the issue doesn't seem to
be fixed. Accessing Magnolia on localhost (not mapped for any site) the
You mean that "localhost" is not set in any of the existing site/domains
or that there is no site definition for the page you are trying to
access at all?
I mean that 'localhost' is not set in any of the site/domains.
generated links still contain the name of the site definition and when
Yes as I explained before when accessing the site content via different
domain then one configured for given site, the site definition name
needs to be included in the link, however the links are translated
properly. I cannot reproduce your problem. Could you provide me with
more detailed instructions on how to reproduce it and maybe complete
stacktrace of the error posted on pastebin.com or similar?
1. I start Magnolia and go to http://localhost:8085/magnoliaAuthor/ to
login.
2. From the list of websites I choose one and double click its icon
which takes me to the site's homepage, which loads ok:
http://localhost:8085/magnoliaAuthor/<website-name>.html
3. All href links on this page look like
http://localhost:8085/magnoliaAuthor/<site-definition-name>/<page-name>.html
That's not correct, is it?
4. When clicking such a link I get a 404 page.
5. When I try to access
http://localhost:8085/magnoliaAuthor/<website-name>/<page-name>.html I
do get the desired page. However, the links on this page all contain
<site-definition-name> instead of <website-name>, so clicking those also
return 404s.
following such a link I still get a big FreeMarker template error:
----
get(cssFiles) failed on instance of
info.magnolia.module.templatingkit.style.ThemeReference
The problematic instruction:
----------
==> list model.site.theme.cssFiles as cssFile [on line 18, column 1 in
templating-kit/templates/global/htmlHeader.ftl]
before this error occurs, the template should set page title to
siteTitle - pageTitle. Could you please give me complete url as well as
title that the page with the error had?
We have a custom 404 page setup configured in web.xml and the 404 page
gets loaded from a separate Magnolia site, but loading that page fails
with the new multi-site support, so that's why I was getting that stack
trace. I disabled that custom 404 page for now and now I just get a
plain 404 page when accessing a link like
http://localhost:8085/magnoliaAuthor/<site-definition-name>/<page-name>.html
that gets generated by Magnolia.
So, our main problem is that the generated links in pages have the site
definition name where the site name should be.
Nils Breunese.
De informatie vervat in deze e-mail en meegezonden bijlagen is uitsluitend
bedoeld voor gebruik door de geadresseerde en kan vertrouwelijke informatie
bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking
van deze informatie aan derden is voorbehouden aan geadresseerde. De VPRO staat
niet in voor de juiste en volledige overbrenging van de inhoud van een
verzonden e-mail, noch voor tijdige ontvangst daarvan.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
