adrien_be
9p6 comments posted · 0 followers · following 0
13 years ago @ Magnolia Documentation - Shop · 1 reply · +1 points
15 years ago @ Magnolia Documentation - How to change an autho... · 0 replies · +1 points
Security >> Roles >> Dbl click on anonymous role's hat >> Access Control List tab
>> Select:
"Website"
"Read only", "Selected and sub pages", "/"
15 years ago @ Magnolia Documentation - Updating Magnolia · 0 replies · +1 points
Thanks in advance.
15 years ago @ Magnolia Documentation - Updating Magnolia · 1 reply · +1 points
When you say remove the old module JARs, we assume that the same JAR names were used in the previous version of a module. I guess there must be exceptions though? (i.e. a JAR has been removed in a superior version after being merged with another one). This may be a far fetched question but I thought I'd ask you in case this is possible.
--
I've been updating from Magnolia CE 4.3.1 to 4.4.3 and I run into a problem with slf4j-api-1.6.0.jar
It seemed like Magnolia did not find the updated version of the jar file (previously it was slf4j-api-1.5.11.jar) so I simply put back slf4j-api-1.5.11.jar and it worked. The problem is that I'm not sure until what extent this is going to work/break my instance.
Here is the error message I get: The requested version 1.5.11 by your slf4j binding is not compatible with [1.6]. See http://www.slf4j.org/codes.html#version_mismatch for further details.
I went and it seems like its a mismatch with another jar file, I think the issue is coming from slf4j-log4j12-1.5.11.jar which needs to be updated to slf4j-log4j12-1.6.0.jar
I found that jar file here but I'm not too confident on the fact that it is the correct one http://grepcode.com/snapshot/repo1.maven.org/mave...
I got the following error message when replacing the slf4j-log4j12-1.5.11.jar by slf4j-log4j12-1.6.0.jar
"SEVERE: Error deploying web application directory magnoliaAuthor java.lang.NoSuchMethodError:" "org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V"
"at org.apache.commons.logging.impl.SLF4JLocationAwareLog.error(SLF4JLocationAwareLog.java:225)"
[...]
--
Also, after the "Magnolia installation and update" I get a few of these messages:
"Absolute path already in location /modules/standard-templatingkit/templates/stkHome/mainArea/template."
"Node template not found on location /modules/standard-templatingkit/templates/stkArticle/mainArea during update process."
I'm not too sure what those messages mean. The site seems to work fine but almost no testing has been done for now.
Is there anything I missed or any typical error I should be aware of that happen during updates?
15 years ago @ Magnolia Documentation - Standard Templating Ki... · 1 reply · +1 points
Just a quick post to provide you a link to the history of the STK .jar file
http://www.magnolia-cms.com/magnolia-cms/features...
You can find all versions you like, which is quite handy if you need to replicate a production environment on your local machine.
Note that the "bundles" that are provided on the main download page includes the STK .jar file as well as other related .jar files which must have some dependency relation to the STK I assume. Not too sure of that one.
Anyhow, the history of Magnolia CE releases is here http://sourceforge.net/projects/magnolia/files/ma...
Hope that helps.
15 years ago @ Magnolia Documentation - Updating Magnolia · 1 reply · +1 points
I could not find anything about upgrading/updating the STK and had to figure out by myself how to do it. And in the same time discover that the newer STK bundles are not compatible with previous versions of Magnolia most of the time.
A bit more documentation about this would be very helpful. I might start creating a page about this subject myself...