Hi,
You do not need to enable additional logging if you are using our default
configuration. If currently you do not get an info logging saying Running
storage schema updates and migrations at some point, and your database is
declared Database XXX needs migration(s), it could not be safely used!,
Hi,
I need to tune the footer(pdffooter.vm) when exporting to PDf to smth
like page N of M , where M is the total number of pages of the output
document.
Could somebody give me a hint?
Thanks,
Elena.
___
users mailing list
users@xwiki.org
Okay, here is an Update: Using the xwiki.cfg file I posted to pastebin, I
modified
xwiki.store.migration=1
After restarting the server I am still getting the exact same error message
in the browser.
Looking at the DATABASECHANGELOG from inside the target database, the
Liquibase executions get
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Hi,
At least, you have progressed, you achieved the configuration so that the
migration was tried, but has failed.
Your diagnosis about what happened seems to me quite right. We drop only FK
constraints, and we do not care about any PK constraints, since our
supported databases are not affected
On Tue, Jul 31, 2012 at 5:37 PM, Arioch arioch...@gmail.com wrote:
Well, may we have Office import/export encoding features to be fixed in 4.2 ?
Done.
You asked for patches, why having 0 Java experience, i made them, code
changes are in Jira.
I tried to build it at home, while having 0
Hello dear XWikiers,
one of the issues of XWiki which keeps coming up since many many versions are
failed restarts. They manifest themselves as a web-application that misses
something I could never identify and starts triggering lack of authorizations.
They tend to fairly randomly. Rather
