Log is swarming with errors from TPmodules.php

[IchBin]

The files name is only the point at which the error occurs. It doesn't mean it's actually in the file.

[patme]

Ok then. Reinstalled whole SMF and TP. No mods were involed this time, except for TP obviously, and guess what. Same error still showing up in logs.

[IchBin]

Does the error exists on every page load? Does the error happen if you disable all your blocks? Does error happen if you visit a certain article? Please try to narrow down when you are seeing the error. You can do this by viewing the log after each page that you load to see if a new error was thrown.

[ZarPrime]

Let me just step in here briefly.  The error appears to be a bug in SMF 1.1.10 from reading the bug report on SMF ...
http://dev.simplemachines.org/mantis/view.php?id=3623

Near the bottom of that page, where it says "Attached Files" there is a text file attached to that post which gives the fix.  The file is called fix.txt and you need to download and view that file and make the edit specified in it to the ManageAttachments.php file in the .../Sources folder on your site.  The text shown on the bug page is not complete.  The fix.txt file contains the entire fix.  Please do the edit specified and then let us know if it solved the problem.

ZarPrime

[IchBin]

That would only happen when viewing the Manage attachments screen though Zar. I'm pretty sure this person is using a block code or something that has that variable in there or something. I just need to find out the info above.

[ZarPrime]

That was the first thing I thought about yesterday when I first read this topic and, after doing some checking, I found several block code snippets that make use of this variable.  For instance, the Team Page code uses this variable.

ZarPrime

[patme]

Let me just step in here briefly.  The error appears to be a bug in SMF 1.1.10 from reading the bug report on SMF ...
http://dev.simplemachines.org/mantis/view.php?id=3623

Near the bottom of that page, where it says "Attached Files" there is a text file attached to that post which gives the fix.  The file is called fix.txt and you need to download and view that file and make the edit specified in it to the ManageAttachments.php file in the .../Sources folder on your site.  The text shown on the bug page is not complete.  The fix.txt file contains the entire fix.  Please do the edit specified and then let us know if it solved the problem.

ZarPrime

I found and applied this bugfix before, without results. The error is still there.

Anyway, you asked to narrow it a bit, so I disabled all blocks, and articles, my index was showing just menu and logotop area, nothing else and my error still showing in admin logs. Actually I can visit forums, post and browse it, and ther is no error but once I hit /index.php its again flooding this message all over the logs.

[G6Cad]

Then it's some code in your index.php file in the root directory, When you reinstalled your SMNF and TP, did you use the big upgrade files and replaced everything with fresh new files ?

[IchBin]

If you'd like I'll take a look at it and see if I can fix it. PM me a temp admin account and some FTP details if you'd like.

[patme]

Yes I'm pretty sure that all files was from big installation file I downloaded from SMF and TP site.

I did one test. Installed a fresh SMF with TP in a new directory, and used a new database (empty one) and guess what? - no errors. Then changed database reference to my current forum (old) and errors appeared (of course used repair_settings.php to fix URL's)

I did the same with current forum/tp installation, changed the database to the one I just created, and no errors were produced.

That means, there is everything fine within the files.

I smell its something wrong in the database.

You must know that recently upgraded from SMF 1.1 RC3, maybe something went wrong, however had no errors reported durring the upgrade. I wiped out all TP related tables from the database before upgrading to SMF 1.1.10 tho.