Bridge Xoops-SMF 1.1 RC3 Beta 1

[Orstio]

I am not referring to the admin user of Xoops, nor the admin user of SMF.  I am referring to the database users.

[X-Ception]

just a prod to let you know 2.0.16 is now out:
changelog:

- Fixed bug #1538291 : Mailer Return-Path header is not set correctly (skalpa/alienhand)
- Fixed bug #1548771 : Criteria doesn't handle IS NULL correctly (skalpa/garrath)
- Fixed bug #1589652 : XoopsTopic::getNiceTopicPathFromId not working (skalpa/dugris)
- Fixed bug #1559119 : Activation key appended to the login form URL (skalpa/bandit-x)
- Fixed bug #1551559 : PHP 5.0.x fatal error in userinfo.php (skalpa/rowd)
- Fixed bug #1570396 : Checkbox doesnt work in the user notifications page (skalpa/bandit-x)
- Fixed bug #1565746 : Installer does not accept mysql passwords with $ in them (skalpa/Ann O. Neemous)
- Fixed bug #1546415 : XoopsForm::getElements broken with insertBreak() (skalpa/dugris)
- Fixed bug #1549803 : XoopsObject errors are not translated (skalpa/giba+wcrwcr)
- Fixed bug #1529039 : Add auth.php english language file. Forgotten in the 2.0.14 (pemen)
- Fixed bug #1525206 : ldap provisioning problems - timezone_offset (pemen)
- Fixed bug #1554972 : Auth provisionning maintain (option) after user creation (pemen)
- Fixed bug #1591544: XOOPS session is not destroyed properly when custom session is enabled (phppp/xuser)
- Fixed a bug that causes reset of block options over module update (phppp)
+ Added fields mapping between Xoops User Database and Auth Server atttribute. The user
can choose wich field to synchronize. (pemen)

seems that have given up on php 4.2.x as requirements now say "Any PHP version >= 4.3 (PHP 4.2.x may work but is not officially supported)"

[Orstio]

Excellent.  That actually solves at least one of the problems I had with 2.0.15. 

seems that have given up on php 4.2.x as requirements now say "Any PHP version >= 4.3 (PHP 4.2.x may work but is not officially supported)"

No surprises there, really.  There are a lot of known security holes in PHP < 4.3.11, and most hosts are offering 4.4.4.

[andeon]

I am not referring to the admin user of Xoops, nor the admin user of SMF.  I am referring to the database users.

ok, I made the configuration with user default root and password " "

In my instalation it has to only user test.

where we can see xoops + smf ?

The bugs of version 2.0.15, they can not function whith smf?

I can make other tests, can ask for!

thank

[whodat]

I read through most of this thread  and I think I have most everything set the way you've mentioned.

fresh install of RC3 which works fine if I access it on it's own. I access it with the bridge (xoops 2.0.16) and I can see it, post to it but after pressing post I come up with a blank page, but it does post the topic as I can see it when I go back to the index.

Sample errors: (lots more that look about the same)

   
2: Cannot modify header information - headers already sent by (output started at /home/mbr/public_html/mainfile.php:211)
File: /home/mbr/public_html/smf_rc3/Sources/Subs.php
Line: 2607
   

8: Undefined index: xoops_js
File: /home/mbr/public_html/templates_c/default-default^%%08^082^082CA1DD%%theme.html.php
Line: 39
   

8: Undefined index: smf_content
File: /home/mbr/public_html/templates_c/default-default^%%BB^BB7^BB72B854%%db%3Asmf_index.html.php
Line: 6

2: Cannot modify header information - headers already sent by (output started at /home/mbr/public_html/mainfile.php:211)
File: /home/mbr/public_html/smf_rc3/Sources/Subs.php
Line: 3195

2: Cannot modify header information - headers already sent by (output started at /home/mbr/public_html/mainfile.php:211)
File: /home/mbr/public_html/smf_rc3/Sources/Subs.php
Line: 3192

Same errors more or less come up when I try to clear the error log or do other admin changes. Pretty much anytime I do a change post of some sort.

I have 2 seperate databases X and S both have each others user added. The path is a cut and paste from the SMF to the Bridge.

Just in case, I dropped a php.ini with the majic quote thing on in some of the folders (didn't change a thing)

What did I miss?

[X-Ception]

AFAIK xoops bridge doesnt work with seperate databases yet.

[Orstio]

fresh install of RC3 which works fine if I access it on it's own. I access it with the bridge (xoops 2.0.16) and I can see it, post to it but after pressing post I come up with a blank page, but it does post the topic as I can see it when I go back to the index.

Can I see a URL?

[whodat]

PM'd you links and logins

[Orstio]

I have 2 seperate databases X and S both have each others user added.

Are you absolutely sure your SMF database user has access to your Xoops database?  I ask because when I tried to logout, I received this:

2: Cannot modify header information - headers already sent by (output started at /home/mbr/public_html/mainfile.php:211)
File: /home/mbr/public_html/modules/smf/index.php
Line: 361

the code it is attempting to execute when encountering this error is this:

Code Select Expand

$logout = mysql_query("
UPDATE ".XOOPS_DB_PREFIX."_session
SET sess_data = ''
WHERE sess_id = '" . $_COOKIE[session_name()] . "'");

setcookie($xoopsConfig['session_name'], '', time()- 3600, '/',  '', 0);

Which would indicate to me that the SMF database user could not access the Xoops database to perform that query.

[whodat]

It's set up the way I have other things before.

Cpanel cut and paste:

Code Select Expand


mbr_smftest

    Users in smftest
    mbr_smftest (Privileges: ALL PRIVILEGES)

        Connection Strings
        Perl $dbh = DBI->connect("DBI:mysql:mbr_smftest:localhost","mbr_smftest","<PASSWORD HERE>");
        PHP $dbh=mysql_connect ("localhost", "mbr_smftest", "<PASSWORD HERE>") or die ('I cannot connect to the database because: ' . mysql_error());
        mysql_select_db ("mbr_smftest");

    mbr_xoop1 (Privileges: ALL PRIVILEGES)

        Connection Strings
        Perl $dbh = DBI->connect("DBI:mysql:mbr_smftest:localhost","mbr_xoop1","<PASSWORD HERE>");
        PHP $dbh=mysql_connect ("localhost", "mbr_xoop1", "<PASSWORD HERE>") or die ('I cannot connect to the database because: ' . mysql_error());
        mysql_select_db ("mbr_smftest");


mbr_xoop1

    Users in xoop1
    mbr_smftest (Privileges: ALL PRIVILEGES)

        Connection Strings
        Perl $dbh = DBI->connect("DBI:mysql:mbr_xoop1:localhost","mbr_smftest","<PASSWORD HERE>");
        PHP $dbh=mysql_connect ("localhost", "mbr_smftest", "<PASSWORD HERE>") or die ('I cannot connect to the database because: ' . mysql_error());
        mysql_select_db ("mbr_xoop1");

    mbr_xoop1 (Privileges: ALL PRIVILEGES)

        Connection Strings
        Perl $dbh = DBI->connect("DBI:mysql:mbr_xoop1:localhost","mbr_xoop1","<PASSWORD HERE>");
        PHP $dbh=mysql_connect ("localhost", "mbr_xoop1", "<PASSWORD HERE>") or die ('I cannot connect to the database because: ' . mysql_error());
        mysql_select_db ("mbr_xoop1");

[Orstio]

Right.  That shows me that your Xoops database user has access to your SMF database.

You also need to grant your SMF database user access to the Xoops database.

[whodat]

The way I read it they are:

the first two are smftest = smf data base
    Users in smftest
    mbr_smftest
    mbr_xoop1

second two are xoop1 = xoops database
Users in xoop1
    mbr_smftest
    mbr_xoop1

Is there something beyond that?

[Orstio]

OK, I didn't scroll the quote box earler.  My bad.

This is cPanel?

[whodat]

Yes. You need a login there also?

[Orstio]

Sure.  Then I can see your error log to see what is going on.

[whodat]

pm'd

[Orstio]

Thank you.

The error about headers sent from mainfile.php at line 211 is the key.

mainfile.php should not have 211 lines.  It looks as if you have used some sort of editor that has double-spaced the file, and added two empty lines at the end of the file.

You'll need to delete those two empty lines after "?>".

EDIT -- Yep, made that change, and all is good now. 

[whodat]

EDIT -- Yep, made that change, and all is good now. 

Well maybe... Error log is still filling up...


edit -- Wasn't the upgrade, I checked my backup and mainfile was the same way. I did change the location of my Xoops root once but don't remember what program I used to do it with but whatever it was must have done that.

[whodat]

All of the errors appear to be in the templates so it probably has nothing to do with you or the bridge.

Thanks a bunch for all the help!!

<script type="text/javascript">
<!--
<?php echo $this->_tpl_vars['xoops_js']; ?> <<<--------this is the error line #40

//-->
</script>

it just looks like something isn't getting set - - and it probably makes no difference to SMF

I'll see if I can track it down.

[andeon]

hi,

Orstio , you recommend some tool that I can use to test in localhost in windows xp? (I have that to use this at the moment)

brigde functions in localhost correct? (local computer)

Thank