Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.1-milestone-1
-
Fix Version/s: 4.2-milestone-1
-
Labels:None
-
Difficulty:Unknown
-
Documentation:N/A
-
Documentation in Release Notes:N/A
-
Similar issues:
XWIKI-7315Wiki macros are not registered in workspaces XWIKI-7318Importing a XAR fails to register Macros in a cluster of wikis XWIKI-4520Not possible to generate inline content from wiki macros when the macro body starts with another macro XWIKI-5439Log too verbose when attempting to register wiki macros with insufficient privileges (for example at wiki startup) XWIKI-6185In some conditions wiki macro with user visibility are not registered with the proper user XWIKI-4742Code Macro language option only works with the language set to "none" XWIKI-4633Add ability to register components only for a given user or for a given wiki XWIKI-5668Wiki macros fail to register correctly on the first import of a .xar XWIKI-8004Wiki macros with global visibility are not registered when installed as extensions XWIKI-7739 "Current wiki" wiki macros not available in the macros list in wysiwyg in path based multiwiki
Description
To reproduce, edit xwiki.cfg and add xwiki.readonly=1, then restart the wiki. When opening the main dashboard, you'll see: Unknown macro: activity, and so on for the other macros on the homepage.
I think that's because the way readonly is working as far as I remember is at rightservice level itself by returning false pretty much all the rights except view which mean that the wiki macro don't have enough right to be registered.