Warning: strpos(): Empty delimiter. in /home/joomlaha/public_html/components/com_smf/smf.php on line 14 SMF Shoutbox 1.5, Joomla 1.011 and SMF Forums 1.1.RC3
Home Forum SMF Shoutbox 1.5, Joomla 1.011 and SMF Forums 1.1.RC3
I am working a devsite to test some changes for a redesign on our clan site and I am looking to dump our AJAX shoutbox and use the SMF Shoutbox on the forums instead but I am running into install problems. Because the 2nd error is listed as database I was thinking it might because of the bridged forums. Looking for any ideas of next steps.
I then modified that file with the included code to display the shoutbox with this code insert in the exact spot recommended and confirmed by some users when I posted at the main SMF forums
Code:
// display shoutbox if (function_exists('sbox')) sbox();
So after verifying with some users I went ahead and ignored the warning and installed. It failed and gave me this error code which is the one that makes me think it has to do with the bridged forums.
Quote
Incorrect table name '' File: /home/killerba/public_html/devsite/smf/Packages/temp/sbox_setup.php Line: 83
This is the code referenced in the error.
Code:
// drop table if it exists. Should make SMF-update 1.1rc2 -> 1.1rc3 easier. $result = mysql_query("DROP TABLE `{$db_prefix}sbox_content`");
$result = db_query(" CREATE TABLE `{$db_prefix}sbox_content` ( `id` int(11) unsigned NOT NULL auto_increment, `time` int(10) unsigned NOT NULL, `ID_MEMBER` mediumint(8) unsigned NOT NULL, `content` text NOT NULL, PRIMARY KEY (`id`))", __FILE__, __LINE__);
Line 83 is the last line in that code. Any ideas? I am hoping it is simple matter of changing those values but I am lost.
I am working a devsite to test some changes for a redesign on our clan site and I am looking to dump our AJAX shoutbox and use the SMF Shoutbox on the forums instead but I am running into install problems. Because the 2nd error is listed as database I was thinking it might because of the bridged forums. Looking for any ideas of next steps.
I get this initial error when installing as it does its pretest
I then modified that file with the included code to display the shoutbox with this code insert in the exact spot recommended and confirmed by some users when I posted at the main SMF forums
Code:
// display shoutbox if (function_exists('sbox')) sbox();
So after verifying with some users I went ahead and ignored the warning and installed. It failed and gave me this error code which is the one that makes me think it has to do with the bridged forums.
This is the code referenced in the error.
Code:
// drop table if it exists. Should make SMF-update 1.1rc2 -> 1.1rc3 easier. $result = mysql_query("DROP TABLE `{$db_prefix}sbox_content`");
$result = db_query(" CREATE TABLE `{$db_prefix}sbox_content` ( `id` int(11) unsigned NOT NULL auto_increment, `time` int(10) unsigned NOT NULL, `ID_MEMBER` mediumint(8) unsigned NOT NULL, `content` text NOT NULL, PRIMARY KEY (`id`))", __FILE__, __LINE__);
Line 83 is the last line in that code. Any ideas? I am hoping it is simple matter of changing those values but I am lost.
Why are you using mambo-smf bridge that is way out of date? You should be using JSMF 2.0RC2.
Because I love old things. Just finished updating the forums and I hand't checked here for updates. I will go ahead update and see if that resolves the issue.
Ok did a complete scrub on the subdomain started with a fresh install of Joomla 1.1.011 with SMF 1.1.R3 and the 2.02 RC2 bridge and modules. I am no longer getting the first error message but I get the second regarding Line 83 and install fails.
Has anyone else been able to get this SMF to work with Joomla?
Joomla Hacks is a Joomla Components, Joomla Modules, Joomla Templates, & Joomla Mambots resource portal. None of the text or images in this public website may be copied without the expressed written consent of the authors. Copyright 2005 by JoomlaHacks.com. Powered by Joomla. All rights reserved.
Terms of Use
Author
Forum
Logged
Just finished updating the forums and I hand't checked here for updates. I will go ahead update and see if that resolves the issue.
