I see the warning in the logs that you describe in MAGNOLIA-3447, but it
doesn't prevent me from installing and running Magnolia. Can you please
describe there what exactly have you done that it stops you from running? Also
the warning occurs only on fresh installation, but not during the upgrade as
you claim in the ticket.
Thanks for the answer, I found the cause for the other problem. At the
beginning I thought it was caused by the cache problem, but the other
error I posted before is caused by this:
http://jira.openmindlab.com/browse/MGNLSTRIPES-7
The changes in the AbstractMagnoliaFilter broke other filters that do
not depend on the AbstractMagnoliaFilter itself. The real problem is
that the error given is not exacly "speaking", even if it is quite
obvious once you find out. So if you have any strange error coming up
after the update, just check all the filter you have and the filters
inside the modules you include.
Just to be extra-clear about the issue, I'm updating to Magnolia 4.4 an
application that I'm developing, and I have the magnolia.update.auto set
to true. But I'm using the in-mem reopsitory, so every start is like a
fresh start, and because of this I was reading the error logged in the
isse. I wasn't that clear in the issue, I'm sorry.
Regards, Danilo.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
