Re: I broke the link to the home page
I think I did this too.
I'm pretty sure that this was caused by this section of the lib/setup/wiki.php file:
// If the HomePage does not exist, create it if ($check && !$tikilib->page_exists($_REQUEST['page'])) { // Get the translated HomePage content $homePageLang = $prefs['language']; $homePageTranslationKey = '_HOMEPAGE_CONTENT_'; //get_strings tra("_HOMEPAGE_CONTENT_") $translatedHomePageContent = tra( $homePageTranslationKey ); // If the HomePage has not been translated yet, fallback to the 'en' translation if ( $translatedHomePageContent == $homePageTranslationKey ) { $homePageLang = 'en'; $translatedHomePageContent = tra( $homePageTranslationKey, $homePageLang ); } $tikilib->create_page( $_REQUEST['page'], 0, $translatedHomePageContent, $tikilib->now, 'Tiki initialization', 'admin', '0.0.0.0', '', $homePageLang, false, null, 'n', '' ); unset( $homePageTranslationKey, $translatedHomePageContent, $homePageLang ); }
If I was logged in as admin, I got the regular Wiki home page when clicking on "Wiki" or "Wiki->Home" on the user menu. However, if I logged on as my normal regular user account, somehow, "page" got set to "http://mydomain.org/tiki-custom_home.php" and clicking on "Wiki" caused the wiki to create a new wiki page called "http://www.mydomain.org/tiki-custom_home.php" which was marked with "Tiki initalization", etc, as per above and which contained all of the default "congratulations" text that's in the _HOMEPAGE_CONTENT_ section of the language.php file (in my case, lang/en).
I did a bunch of stuff. Eventually it seemed to just start working on its own. I'm not sure what I did. I did disable "use URL index", which I had set to "http://mydomain.org/tiki-custom_home.php" at one point; however, the site didn't start working until well after I'd disabled it. I also had cleared the cache a bunch of times (not just the tiki wiki caches, but my browser cache) and, alas, I couldn't tell you what it was that I did immediately prior to the site deciding to work on its own. Perhaps there's a server-related cache that had to timeout on its own or something.
I'm using 6.4.
— Kat