Migrating from a v8 to a v10 version of xwiki, the old version has LDAP enabled. The new version is completely fresh, on a VM created today, installed via the xwiki deb packages. I could log in as superadmin and access the admin console on the fresh wiki with no problems.
I imported the old wiki’s export file into the new v10.9, and now the superadmin user no longer works, and neither does the admin user created in the initial setup wizard. They can both log in, but can’t do anything, and the hamburger menu doesn’t have ‘administration’ as an option. The page on login has the following message instead of most page elements: Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed. Check the rights of its last author or the parameters if it's rendered from another script.].
(I’m not sure if it’s relevant for superadmin apparently losing perms (disabling ldap doesn’t return functionality), but I’m also struggling to get the LDAP working - i can’t log in as my own user yet. Iteration is slow. Old wiki had ldap server on localhost, new wiki has a centralised ldap, and I’m not an ldap expert )
This is on a disposable test VM as I sort out the commands to put into Ansible, so I can zap the machine and start afresh easily.
I imported the old wiki’s export file into the new v10.9
This is quite a dangerous way of doing an upgrade. Ideally you should update the WAR and let XWiki take care of the migration from one version to another.
Back to your current situation, according to the errors in the screenshot the problem is that the author of most of the pages don’t have the right to execute scripts (I guess you did a partial export/import and lost the right setup of those imported pages authors or something like this). Since an important part of the UI and especially all the administration is based on wiki pages it does not work so well. So it is a right issue but it does not have anything to do with the right of the user with which you logged in.
Thanks for your help Thomas, it’s appreciated. I have now made a new import file and have an almost 100% working new site now. The only fault I’ve found is one sidebar heading in the admin part of the wiki, but apart from that, it all seems to be working. Unfortunately I’m way behind the 8-ball and have to wrap this up and move on to the next fire.
Re: the warning on the import style, unfortunately my hands are tied a fair bit here - I’m breaking up a multi-app legacy server that’s in heavy use, and can’t easily image it for replacement in case I screw up an in-place upgrade (there’s also no war file in either the old or new installs).
My LDAP problem was due to not realising the LDAP authenticator needed to be installed (I thought it was a default module - the logs didn’t seem to complain that it was missing…). Curiously, LDAP didn’t work for me configured in the config file, but the same settings configured in the GUI with LDAP Application worked. Must have done something wrong, but need to move on rather than figure it out…
Again, thanks for your help - making a new backup file was iffy from the old site for reasons I won’t bore you with, but it looks like it was the secret sauce to getting past the roadblock.
)