Bridge Xoops-SMF 1.1 RC3 Beta 1

[Orstio]

Followed the instructions fine.  But now I can't login from either xoops or wrapped SMF. I get this error:


Quote
2: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource
File: G:\Program Files\Apache Group\Apache2\htdocs\Xoops\modules\smf\index.php
Line: 202

Not sure what's going on there

Is this with a username that exists in SMF, but not in Xoops?

[ShaneR]

Well...not quite sure how to answer that..lol.. as  I used the same username/password for xoops admin account as I did for my SMF install.

So for the purposes of trouble shooting...can't be narrowed down to a certain account right now (I think that's what you were getting at).

[Orstio]

Alright, are they installed in separate databases, then?

Does your SMF database user have access to the Xoops database?

[ShaneR]

Yes they are in seperate databases.

And yes, access rights to the database should not be a problem as both SMF and Xoops access MySql with the root Uname and password.

[ShaneR]

Heh...ya know, I think I'm too brain dead to be messing with this stuff tonight

I'm guessing smf and Xoops need to share the same database--makes sense...not sure why I didn't clue into that. Or, maybe I'm wrong about that to...lol

Anyway, did a 2nd installation of Xoops (still have the first), but this time put it in the same database as smf.  Seemed to work as I could login...but would then just get a blank page (path to smf etc is fine).

Anyway, I'm not an expert in any of this (I have problems spelling PHP!!;)  )...just playing around   So, my apologies for any stupidity

[waqass]

This brige is working with 2.03 but when I use xoope 2.2.3 then this error is show on in the module preference
Warning [PHP]: main(../functions.php) [function.main]: failed to open stream: No such file or directory in file modules/smf/admin/index.php line 25
Warning [PHP]: main() [function.include]: Failed opening '../functions.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in file modules/smf/admin/index.php line 25
Notice [PHP]: Constant _MI_ADMIN already defined in file modules/smf/language/english/modinfo.php line 33
Notice [PHP]: Constant _MI_ADMIN_DESC already defined in file modules/smf/language/english/modinfo.php line 34 What could the possible solution I have done fresh installation and seprate database as well as seprate users for them!I always get blank page..?

[waqass]

Moreover if I give the full url in the preferences of module which is this /home/billa/public_html/smf/index.php then i get this message Fatal error: main() [function.require]: Failed opening required '/home/billa/public_html/smf/index.php/index.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/billa/public_html/modules/smf/index.php on line 87
Warning [PHP]: main(/home/billa/public_html/smf/index.php/index.php) [function.main]: failed to open stream: Not a directory in file modules/smf/index.php line 87

[Orstio]

Heh...ya know, I think I'm too brain dead to be messing with this stuff tonight

I'm guessing smf and Xoops need to share the same database--makes sense...not sure why I didn't clue into that. Or, maybe I'm wrong about that to...lol

No, they don't actually, but it may be difficult on a local machine to assign permissions to databases the way you can in cPanel.

Anyway, did a 2nd installation of Xoops (still have the first), but this time put it in the same database as smf.  Seemed to work as I could login...but would then just get a blank page (path to smf etc is fine).

Turn off compressed output in SMF.

Anyway, I'm not an expert in any of this (I have problems spelling PHP!!;)  )...just playing around   So, my apologies for any stupidity

No problem.  I'd like the installation to be as painless as possible.

[Orstio]

Moreover if I give the full url in the preferences of module which is this /home/billa/public_html/smf/index.php then i get this message Fatal error: main() [function.require]: Failed opening required '/home/billa/public_html/smf/index.php/index.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/billa/public_html/modules/smf/index.php on line 87
Warning [PHP]: main(/home/billa/public_html/smf/index.php/index.php) [function.main]: failed to open stream: Not a directory in file modules/smf/index.php line 87

The path should be this:

/home/billa/public_html/smf

Not this:

/home/billa/public_html/smf/index.php

Bright yellow on white is impossible to read.  Please don't do that.

[X-Ception]

Few queries that i have, my minds been busy again sorry.

1. if i was to have two sites, using one SMF both bridged, would this cause any known sync issues

2. would it be possible to code into the bridge a "manual sync" option that could check users on both sets of sites ( site and forum ) and pull the none exsisting users from one to the other  ( ensureing no duplicated accounts of course ) ?

[ShaneR]

Thanks for all the help (and work), Orstio.

I decided pretty quickly that Xoops wasn't for me, so I took the installations off...but, if you find you need some ( somewhat inexperienced)testing, I don't mind throwing it back on...takes seconds.

Shane

[Orstio]

1. if i was to have two sites, using one SMF both bridged, would this cause any known sync issues

What do you mean by two sites?  If the TLDs are different, the cookies will not set.

2. would it be possible to code into the bridge a "manual sync" option that could check users on both sets of sites ( site and forum ) and pull the none exsisting users from one to the other  ( ensureing no duplicated accounts of course ) ?

It is possible, but I'm not sure of any issues that can arise due to this.  It's important to know, I guess, that SMF uses a salted SHA1 encryption for passwords, not the usual MD5 of most PHP software.  SMF also has the ability to read MD5 passwords like other software, and then convert it to its own SHA1.  So, this makes mass-user migration difficult, because the raw password is not available, like it is when the user is logging in, and the SHA1 password from SMF can't be interpreted by Xoops.

There is a method that I use for the SMF login.  It works, but if used in a mass-migration situation, may have the unpleasant side effect of an admin user trying to get into the admin panel and failing.  This is not an issue with the login-migration situation, because a raw password can be made available.

[waqass]

I have tried the both paths but I always get blank screen I am using 2.2.3 xoops?What could be else problem?

[X-Ception]

What do you mean by two sites?  If the TLDs are different, the cookies will not set.

lets say
www.example.com/xoops
www.example.com/music


www.example.com/forums

in that theory basis both sites, same tld, could you forsee any disasters ?


and many thanks for your explanation on the other question most helpful

[Orstio]

Yes, as long as they are the same TLD, it's not a problem.  In fact, you could probably do something like this:

http://xoops.example.com
http://music.example.com

and http://forum.example.com

as long as you make sure to check subdomain independent cookies in the SMF admin panel.

You have probably seen from my test site that I have the same forum bridged to Xoops, PostNuke, PhpNuke, and iGaming.

[X-Ception]

Yes, as long as they are the same TLD, it's not a problem.  In fact, you could probably do something like this:

http://xoops.example.com
http://music.example.com

and http://forum.example.com

as long as you make sure to check subdomain independent cookies in the SMF admin panel.

You have probably seen from my test site that I have the same forum bridged to Xoops, PostNuke, PhpNuke, and iGaming.

Yeah i had a wander ( excellent work btw tho half of it is over my head ) - thank you very much for your efforts .. once again
appreciated

[X-Ception]

Has something changed in xoops 2.2.4 tho everything is the same as always i seem to be getting a white page, have yet to have this. The only real change as i mentioned is the usage of patch for xoops.

[avatar]

It seems to me that - contrary to received advice -  the xoops login works for both xoops and smf, and that the smg login does not work for xoops.

I was running my site with the xoops login and all was fine for xoops and smf, but when I read this thread and took the advice to not show the xoops login, but use smf, I found myself locked out of xoops. I managed to trick my way back into xoops admin and changed the login block back to the way it was, and all is ok again.

BTW Thanks for the bridge

[nulla]

I am new to SMF... looks great, I am impressed. I am familiar with xoops and I have installed the module and bridged, setup the correct path and I link up but I do not seem to be wrapped into xoops. Login to xoops does not login to smf. If I register first in SMF this member does not show in Xoops.
I can get SMF running by clicking on the menu in xoops but no side menu, though this is set up to show in blocks ... am I missing something on the SMF side of this?

thanks for a great looking board

[X-Ception]

I am new to SMF... looks great, I am impressed. I am familiar with xoops and I have installed the module and bridged, setup the correct path and I link up but I do not seem to be wrapped into xoops. Login to xoops does not login to smf. If I register first in SMF this member does not show in Xoops.
I can get SMF running by clicking on the menu in xoops but no side menu, though this is set up to show in blocks ... am I missing something on the SMF side of this?

thanks for a great looking board

did you install SMF using the same admin uname/pass as you did in xoops ?