SMF Version: SMF 1.0.7
Hi...I'm a newbie to SMF software but a regular Wordpress user.
I saw a post in the wordpress forums about a bridge between Wordpress and SMF (Enigma2...etc).
So I took my exisiting Wordpress 2.02 install which is still working great. Installed SMF 1.0.7 into a /forum directory. Then followed the (well detailed) instructions to install Enigma2 on top of SMF (1.0.7).
After running the install routine I'm presented with a screen that shows an Enigma 2 header; a couple of SMF info boxes (user info on the left, news box on the right; with the Search field below left and "Key Stats" below right) then a error line which reads...
"Fatal error: Call to undefined function: menu() in /home/httpd/vhosts/mydomain.com/httpdocs/forum/Sources/Load.php(1040) : eval()'d code on line 329"
So I looked up line "329" in Sources/Load.php and it reads...
// Hacker... you can't see this topic, I'll tell you that. (but moderators can!)
followed by this line of code
if (!empty($board_info['error']) && !($board_info['error'] == 'access' && $user_info['is_mod']))
So my questions are:
Did I get this error because I had an empty SMF forum? (no posts)
Or
Is there likely something I did incorrectly in the installation? (I can't imagine what I triple-checked the instructions)
I realize I'm not complete with the Bridging of Wordpress (there is still a couple of other steps to go - but this looks like a "showstopper" and I need to know to decide whether to just wipe it all out and start over - or if I can fix this somehow...
anyone know what happened?
thanks in advance...
DA
It should'nt have anything to do with how many posts you had in teh forum lol. Lets see...do you have msn? Maybe I could help..
"Load.php(1040) : eval()'d code on line 329" = error on line 329 of the code passed to the eval statement on line 1040 of Load.php.
Run this query in phpMyAdmin and you should get a more useful message:
INSERT INTO smf_settings VALUES('disableTemplateEval', 1);
That will make SMF use require() for loading templates instead of eval(), which will give you the actual file where the problem is happening.