Site: www.roundablock.com (http://www.roundablock.com)
SMF 1.1.8 with TP
Other Mods:
1. URL Popup
2. Activate account redirection 0.1
3. Shared Forum Mod 0.2.5.3
4. Custom_Greeting_Depending_on_Time 0.5
5. AvatarSelect 1.1.2
6. zCommunity 0.7.3
7. Invite 1.14
8. Message for your guests 0.1
9. Welcome Topic Mod 1.1
10. Favorite drink 0.1
11. SMF Media Gallery 1.5.5
12. OS & Browser Detection 1.2
13. MoodBobels 2.3
14. Ultimate Profile 0.8.5
15. E-Arcade 2.5.7
16. TinyPortal 1.075
17. Favicon 1.2
18. Audible PM 1.0
These errors show up even on the default theme:
2: Missing argument 3 for db_query(), called in /home/**********/public_html/forum/Themes/default/TPBlocks.template.php(48) : eval()'d code on line 3 and defined
File: /home/***********/public_html/forum/Sources/Subs.php
Line: 238
2: Missing argument 2 for db_query(), called in /home/*******/public_html/forum/Themes/default/TPBlocks.template.php(48) : eval()'d code on line 3 and defined
File: /home/**********/public_html/forum/Sources/Subs.php
Line: 238
I did a search here but found nothing close to these..
I would greatly appreciate a point in the correct direction of fixing these.
Thank you
Jakki
I dont think they are TP related at all :-\
Just to make sure, reupload all the TP files manually through FTP and then check so all the TP code got added correctly.
Modification Instructions (http://docs.tinyportal.co.uk/index.php?topic=140)
I figured it might be since the TPBlocks.template.php was listed in that error.
I'll look through the modification instructions for the subs.php and see if I missed something...thanks.
I posted these errors on SMF also I re-uploaded the files and checked the modification instructions all match up...
What and where do these errors show up, what do you do ?
Clear your error log, and browse to a page, go back to the log and check it, We have had a lot of testsites running now for quite some time and these errors have never showed up for us.
It must be some other code you use or one of the other mods.
I've done that several times cleared it out and browsed the forum and then went to check error log and they are there....
Yes, but she asked "What" and "When"? What EXACTLY are you doing when the errors appear? Are you going to a specific page? Are you submitting a block or article? If it only happens on a specific page, what page is it? As you can see, there is some info you can figure out by doing this type of trouble shooting.
Yes, but she asked "What" and "When"? Those just show up.
What EXACTLY are you doing when the errors appear? Just click on the home button, went to the forum, then to admin to check errors.
Are you going to a specific page? NO
Are you submitting a block or article? NO
If it only happens on a specific page, what page is it? NO, they just show up
As you can see, there is some info you can figure out by doing this type of trouble shooting. IF it was that simple to figure out I would not be asking here...I noticed it had the TP template.php involved.
Here is the response I got from SMF forum:
http://www.simplemachines.org/community/index.php?topic=296705.0 (http://www.simplemachines.org/community/index.php?topic=296705.0)
He says it is more likely a TP problem and told me to come here.
The template rarely tells where the error is. The template just tells you which file is getting processed when PHP decided to throw the error. When multiple files are being processed all at once, the errors are generally wrong about which file the error actually occurred in. Do you have any custom blocks or articles? Try disabling them? If that does not do anything you'll have to look at SMF. There is a query that allows you to turn on debug so that it will give you a more specific error on the actual page when it happens, but I can't remember it. You'll have to look at SMF to find that. Since I don't have this problem on any of my sites, there's no real possible way to figure out what is causing it unless you can find that debug statement at SMF. After that, we'll see which mod/code is actually the cause of it.
In my above post they told me to come here. Kat from SMF told me it was a Tinyportal error...
Jakki, I'm not saying you need to go back to SMF to post. I'm telling you that SMF has a setting that will help US help YOU to figure this out. Find it, enable it. This will tell us for SURE if it is indeed happening in the blocks template. Please try my suggestions from my previous post as well and report back.
I'm checking into it..
Aha! Found the setting. :) Try the following setting. Place it in your Settings.php file temporarily. Once you get the error from this, post it here if its different that what you posted already. It shouldn't matter where you place this as long as its not inside another statement, and it is inside the <?php tags. :D
$db_show_debug = true;
I think after enabling this setting you should see the error at the top of your page.
I found they error there was double coding in that TPblockstemplate.php, thank god for winmerge to compare files. I compared that file with a new file out of the TP download. It's fixed and no more errors.
Wanted to say, since the way to add the debug info is here, for those kind of errors i think you should disable eval(); aswell.
Then of course you need to enabled it back.
INSERT INTO smf_settings VALUES ('disableTemplateEval', 1);
INSERT INTO smf_settings VALUES ('disableTemplateEval', 0);
I have used this method several times and it does help to pinpoint the error.
Quote from: Jakki on March 02, 2009, 10:46:31 PM
I found they error there was double coding in that TPblockstemplate.php, thank god for winmerge to compare files. I compared that file with a new file out of the TP download. It's fixed and no more errors.
Great you found the error. :) But this was TPBlocks.template? Was it an earlier version of it there perhaps?
Normally when TP upgrades it overwrites all TP files, to be sure all files are correct..but if you do it manually etc. that might not happen.
That's what happened Bloc. Even after I uploaded the new files manually I was still getting that error so I pulled that one down and compared it to a new fresh one.
I had to manually install TP on my site. I'm just glad it is fixed and the new TP is awesome.