I am posting this here because I thought you might be interested in hearing something I seem to have stumbled across. You can read all about it on this thread:
Basically, what seems to be the case (I emphasize seems because I am far from a PHP expert, and know my very definite limitations), is an interaction problem between mambo-SMF forum and the new mambo-G2 (gallery2), such that when mambo-SMF is installed, the mambo-G2 will not run.
I think the problem may be caused by some of the mambo-SMF changes to the index.php file.
Michiel_1981 who is the developer of the mambo-G2 component, like you, is right on top of his forum and supports it superbly and proactively. If you are so inclined, I suspect you could easily resolve this with a simple tweak so both of your important components can co-exist in the same mambo site.
You can contact me by mail or true his forum. A lot of people want to use both our component, so a fix should be made don't you think? I'm here to help on the gallery2 component side.
It seems the problem is caused by the following line (added by cowboy to mambo's main index.php):
require_once ($smf_path."/SSI.php");
If you comment it out, mambo-G2 works fine.
Interestingly, mambo-SMF also seems to work fine with it commented out (at least I didn't see any overt impact). The one thing I did notice was the module mod_smf_recent_posts ceases to function when it is commented out. That's not good.
I noticed that line also caused problems for other mambo components, see:
Well in SSI.php series of calls, it clears what Mambo had initialized. For example, $_REQUEST is cleared by it. That is why on one fix, $_REQUEST value is saved to $_TMP and copied back to $_REQUEST after SSI.php call. There were other variables that probably needed be saved as well.
if SSI.php clobbers the mambo context,(...a naive question...) might it be possible to save the entire mambo context before the SSI require_once and restore it after the SSI require_once returns?
Would this eliminate the issue once and for all?
Don't know how realistic/feasable this is, just brainstorming, and hoping there is no mambo variable which mambo-G2 and mambo-SMF require different values of to function.
I believe SSI.php is an actual SMF Forum file, so you would have to download SMF according to Cowboy's install instructions (it's a very easy, automated install).
cleanRequest() function is messing up gallery2 component and maybe a lot more components and modules, because it is included on every page and executed.
You need to look what's on cleanRequest(). It's just what I said on my previous post. The truth is, SSI is included just to support the other modules create for the "other" bridge. I maybe able to look on this myself this weekend. My cable modem is up and running .
Since you are respectively owners of two of the most significant components in the Mambo world, this cooperation is really nice to see.
It sounds like cowboy may not need this SSI afterall for his own bridge, so hopfully a fix is possible - in which recent posts, recent topics and optional SMF login module will still work.
That's what i'm saying. I guess there's still a need to save the state of some of the variables there, just like what's already done for $_REQUEST. In Mambo's index.php, $_REQUEST state is saved to $_TMP and retrieved back after the call to SSI.php.
None of the text or images in this public website may be copied without the expressed written consent of the authors. Copyright 2005 by MamboHacks.com. Powered by Mambo. All rights reserved. TERMS OF USE
Forum
Author
Logged
.
