> A couple of sites I've updated to Tiki 8 have shown a strange behavior,
> that would be good to avoid.
> The site first displays as if it is missing many preferences. It
> displays using TheNews theme. There is an error message:
> Required features: *feature_wiki*. If you do not have the privileges to
> activate these features, ask the site administrator.
> The only error is $.cluetip is undefined.
> The html page title is missing, also.
> Seems to me this was corrected sort of spontaneously at a site I
> upgraded a day or two ago. I have a site upgrade in progress now where
> it is still a problem in one browser (Firefox) though Ok in Opera. Any
> -- Gary
I know the problem you're talking about. Trebly reported it in
The problem is session data. Your 8.x install is using session data that
it shouldn't use. There could be 2 reasons, either the session data is
in an old Tiki 7 (pre-upgrade) format. Or it belongs to another site. I
found one bug that would cause session data between different sites to
conflict this week and fixed it. But I cannot fix it for already
released versions. I explained that problem in a comment on the above
report, but it's not really simple :-(
One thing is sure, if you have sites setup in a way where PHP sessions
would conflict, you would get this problem. One such configuration is
installing a site in a subdirectory of another site's directory, for
example having one site in localhost/ and one in localhost/8.x/. If that
is your case, as your URLs suggest, you do have a "normal" session
conflict. I don't know if the following will be clear, but if a site is
installed in localhost/, Tiki kind of stores the cookie in localhost/.
The cookie will be used for the whole localhost/, including
subdirectories. So if you access localhost/8.x/ later, the 8.x install
will use the root site's session data, which is bad.
Clearing these should solve/workaround.
I am worried about this problem would like to understand the root cause
of your problem, maybe if we can chat on IRC. But we may need to
implement a session data conflict check in any case.
Thanks for reporting