OK...
Please disregard, I finally figured it out LOL... it took me all day but i put in the absolute path where the comment /SSI.php is... apparantly it needed an absolute one to do that.... is this a bug?

I followed your instructions closely, after doing it a few times... it's working now but for some odd reason, I had to put the ABSOLUTE pate into a couple of documents by hand because the installer didn't do it.  Even in the smf config, I had the absolute path as required but it didn't put that in correnctly.

I know it's not a write issue because I have all permissions set up correctly.

Another weird thing... where the config specifies the ABSOLUTE path, if you try and change it... your config won't allow it... it will simply put it back it what it 'thinks' should be default.. is that working as intended?  I can see this could be a problem for those who many need to change that in the smf config.  I'm wondering if this had to do with my problem.

Thanks again!

Yeah... this one is a strange thing, and I do believe it is a bug (or just a little glitch in the code...

First things first

1) I noticed that in my templates "index.php" code, that around line 17 there is a line that says:


if (!defined('SMF')){
  require ($mosConfig_absolute_path."/administrator/components/com_smf/config.smf.php");
  require ($smf_path."/SSI.php");
}

I had to replace it with the path (remember I'm working on a test server, but it's the same thing:

if (!defined('SMF')){
  require ($mosConfig_absolute_path."/administrator/components/com_smf/config.smf.php");
  require ($smf_path."W:/www/hipware/forum/SSI.php");
}

Now, notice I had to put in the full path.  Yours will be different based on your server, for example, it may need to be:

home/public_html/forum/SSI.php
(or something similar).

THEN...
I had to do the same in the smf.php file located in /components/com_smf on or around line 15:

if (!defined('SMF')){
     global $mosConfig_absolute_path;
     require_once ($mosConfig_absolute_path."/administrator/components/com_smf/config.smf.php");
     require_once ($mosConfig_absolute_path."/administrator/components/com_smf/functions.smf.php");
     require_once ($mosConfig_absolute_path."/administrator/components/com_smf/functions.smf.main.php");
     require ($smf_path."/SSI.php");
}

Replace with:

if (!defined('SMF')){
     global $mosConfig_absolute_path;
     require_once ($mosConfig_absolute_path."/administrator/components/com_smf/config.smf.php");
     require_once ($mosConfig_absolute_path."/administrator/components/com_smf/functions.smf.php");
     require_once ($mosConfig_absolute_path."/administrator/components/com_smf/functions.smf.main.php");
     require ($smf_path."W://www/hipware/forum/SSI.php");
}

or something similar to your server as stated in the first code example.

NOW.. here is the tricky part...
Please let me know if any of you experience this, because it's VERY strange...

In your mambo admin panel, go to SMF Configuration. 
I noticed that the settings don't stick (even with FULL writing permissions on the config file).  I tried experimenting with the path, and it would insist on putting in what it "thought" was the path, but it's correct.  It wouldn't let me change it.

I opened up the config file (the php file in your administrator/components/com_smf/) and I noticed that the absolute path was BLANK!  I played with this and it was the only way it would stick to what I wanted.  Then it would show up in the SMF configuration in the control panel.

This problem remains...
It still says that SMF is not installed, yet I have it working.  So that leaves the new update feature out of the question.

Can anyone go through the documents that I've stated and experiment and see if your findings are the same?  Or is this all intended? 

In some ways I'd like to revert back to 1.0 until it's fixed, but I deleted the file

Anyway, still a GREAT job on this bridge !!

Keep us up-to-date! I do hope I've helped...

Cheers,
Jim

Hi,

I had exactly the same problem Jim had. However Jim's solution didn't work for me. Here is my solution:

I edited only the config_smf.php under administrator/components/com_smf/ and put this as the smf path:

$smf_path = ($mosConfig_absolute_path."/forum");

[In my case smf is located in a subdirectory named forum under the mambo' direcotry.]

So far everything seems to be working. I'll update if anything goes wrong.

Regards,
Ertu

Your problem seems like the config.smf.php is not writable. If you notice, Mambo has a configuration option that sets files permission settings of files you installed. Look at those settings in Global Configuration.

On 1.2 I made adjustments so future users don't have to worry about this permissions and manually inserting codes.

i'm still working on 1.2, my changes there are mostly on installation process. 1.1a should be fine. I already tested it twice.