TinyPortal

Development => Support => Topic started by: Ixo on October 17, 2009, 04:16:34 PM

Title: TPShout & modSettings issue
Post by: Ixo on October 17, 2009, 04:16:34 PM
Link to my site: http://www.wow-info.es
SMF version: 1.1.10
TP version: 1.0 beta 4
Theme name and version: Portalblack
Browser Name and Version: Doesn't matter.
Mods installed:
1.     SMF Sitemap      1.2.2      
2.    reCAPTCHA for SMF    0.9.6    
3.    Pretty URLs    1.0RC    
4.    Cristalab Icon Set    1.0    
5.    TinyPortal    1.083
Related Error messages:
-------------The next error shows 6 times per page viewed-------------
8: Undefined variable: modSettings
File: .../Themes/Portalblack/languages/TPShout.spanish_es-utf8.php (tp_above sub template - eval?)
Line: 18




Title: Re: TPShout & modSettings issue
Post by: IchBin on October 17, 2009, 08:00:25 PM
You have any custom blocks are articles with php code? It is most likely because one of them is using $modSettings but has not declared $modSettings as a global.
Title: Re: TPShout & modSettings issue
Post by: Ixo on October 17, 2009, 09:48:39 PM
Thanks for your answer IchBinâ„¢. My only php code block is a "recent messages" box. I updated the code, and the error got fixed, but now i receive 2 different new errors:

----- It shows 1 time per visit -----
2: Invalid argument supplied for foreach()
File: .../Themes/default/languages/TPShout.spanish_es-utf8.php (main sub template - eval?)
Line: 15
-----------------------------------------

----- It shows 1 time per visit -----
8: Undefined index: boardnews
File: .../Themes/default/languages/TPShout.spanish_es-utf8.php (main sub template - eval?)
Line: 15
-----------------------------------------

Any idea/help would be great. Thanks in advice.
Title: Re: TPShout & modSettings issue
Post by: IchBin on October 17, 2009, 09:54:03 PM
You need to do some research here. First, search this forum to see if your errors have been reported and fixed. If not, you may just have to wait until Bloc can fix them. If they have not been reported, then you should try to figure out where they are coming from. You can do this by seeing which page it happens on. Multiple or a single page you hit. You can also test if it is the blocks you have by disabling all blocks and then adding one by one to check to see if any particular block is causing the error. Might do the same thing for articles if you have them.