FYI, I abandoned the VM and started over. I am now back to where I was before installing the skin which destroyed my site.
I liked the general story behind what xwiki is and I am trying to like it, but its not making it easy.
I installed that skin because it was the second one in the list after something with debug in the title. I did not mean to install a non-recommended skin. I did that because I made a copy of the flamingo skin following a page in the help but i was not showing up as an option. I just wanted to see if a skin installed by extension manager created a folder next to flamingo. It did not (!?). Why is a skin in the extension store allowed to provide content in the first place? That’s not what skins (should) do. The installer did stop on a “continue” prompt which was probably warning me that it was going to destroy my content but I was numb to hitting continue in the weird, non-standard UI.
Later I found that the list of skins does not correspond to the names of the folders of skins that you install in the filesystem nor the name of the skin in extension manager! ‘flamingo’ is not even an option in the drop down! By default there are two generically names “Skin (default)” and “skin bla bla bla” (which I assume is the user friendly name of flamingo). After installing Leiothrix skin, another option called something like “Public Site” show up in the list. I found through trail and error that I can enter the name of a skin folder (like flamingo) manually even though its not an option in the dropdown…
This seems like a naming issue. In an attempt to make the skin names in the admin UI “user friendly” a level of indirection was added that made it seem broken to me as I tried to introduce a new theme.
Now I am dealing with another more fundamental naming issue for pages. I created a nest page from from home called Team. Home.Team has nested pages for each person in that team. i.e. Home.Team.Bobg. I then included {{include page=./Team}} in Home but that breaks the Home.Team.Bobg link which now shows as a page that needs creation. If I create a new page via that link, not only do a get a new duplicate BobG page, but the Navigation Application shows it as a new duplicate top level Home node with a duplicate Team and BobG underneath it.
The page index reveals that the new page is Main/Team/BobG even though the Navigation Application shows it as a duplicate Home->Team->BobG hirearchy. Note that despite the link in the Team page being fully qualified as doc:Home.Team.BobG.WebHome (where the heck does WebHome come from?), it is interpreted differently based on whether you visit Team directly or the Team content is rendered inside of the Home page.
I have tried including the Wiki name in the link and with and without that weird ‘WebHome’ suffix.
Sometimes the path separator is ‘/’ and sometimes its ‘.’ but they are not interchangeable! You cant use ‘/’ in the link syntax yet the page index UI uses ‘/’ to show you the fully qualified page ID/location!
The page picker UI has this weird behavior that it shows the first level page tree initially but pages that contain nested pages do not show as folders that can be expanded. You have to select that page as if its the page you want and then re-enter the picker which will then show only the next level of choices, and repeat until you get to where you want to go.
These inconsistencies make it hard for me to have faith that I will be able to build a non-trivial site with xwiki with any sort of reasonable efficiency.
–BobG