I'm no ribbon xml expert but I believe the backstage stuff is a separate block. I have used this, which seems to work for the most part:
Code:
<backstage>
<tab idMso="TabInfo" visible="false"/>
<tab idMso="TabRecent" visible="false"/>
<tab idMso="TabNew" visible="false"/>
<tab idMso="TabPrint" visible="false"/>
<tab idMso="TabHelp" visible="false"/>
<tab idMso="TabPublish" visible="false"/>
<tab idMso="TabSave" visible="false"/>
<button idMso="FileSave" visible="false"/>
<tab idMso="TabFileSave" visible="false"/>
<group idMso="SaveGroup" visible="false"/>
<tab idMso="TabOfficeStart" visible="false"/>
<tab idMso="Publish2Tab" visible="false"/>
<tab idMso="TabOfficeFeedback" visible="false"/>
<button idMso="ApplicationOptionsDialog" visible="false"/>
</backstage>
During testing (at least), you want to have Client Settings > General > show add in user interface errors checked. So I guess I'm saying if we can't see any errors between these 2 then make sure you enable the error checking for this and maybe something will get pinpointed. In my testing, I also seemed to experience that the order of items matters for some reason. It may also be that I'm disabling some items within Group tags, not Tab tags.
Last edited by Micron; 10-27-2019 at 10:04 AM.
Reason: clarification & code correction
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.