News: TinyPortal Release Schedule. Please read this update for More Info.

Login  |  Register
HTML5 Icon HTML5 Icon HTML5 Icon
TP on Social Media
Welcome, Guest. Please login or register.
Did you miss your activation email?

January 22, 2020, 02:36:35 AM

Login with username, password and session length

Recent

Members
Stats
  • Total Posts: 189421
  • Total Topics: 20795
  • Online Today: 362
  • Online Ever: 917
  • (January 21, 2020, 09:02:26 AM)
Users Online
Users: 0
Guests: 38
Total: 38

Author Topic: Error Log: 8: Undefined index: show_download  (Read 1562 times)

0 Members and 1 Guest are viewing this topic.

Offline FUBAR

  • Jr. Member
  • **
  • Posts: 98
Error Log: 8: Undefined index: show_download
« on: March 07, 2011, 05:58:55 PM »
SMF version: SMF 2.0 RC5
TP version: TinyPortal 1.0 RC1
Default Forum Language: English
Theme name and version: DSv4 but happens on default as well.
Browser Name and Version: Firefox 3.6.13
Mods installed:
1.    Aeva Media 1.4c
2.    BUG FIX: array_diff_key compatibility 1.0    
3.    TinyPortal 1.102
Related Error messages:
http://www.mysite.com/forum/index.php?action=dlattach;attach=70;type=avatar
8: Undefined index: show_download
File: /home/mysite/public_html/forum/Sources/TPSubs.php
Line: 201

I'm honestly not sure if this really has to do with TP but I've been getting this error for a while now. 

I'm not really sure what could be causing this and can't find an action to replicate the issue.  When I click on the from the error message view I get the following header and message. 

An Error Has Occurred!
You are not allowed to access this section

Also this is always caused by guests so I guess it could be spiders causing the issue? 

Any idea's guys? I would really appreciate any help, thanks.  O0

Offline IchBin™

  • Developer
  • *
  • Posts: 16228
    • My Website

Offline FUBAR

  • Jr. Member
  • **
  • Posts: 98
Re: Error Log: 8: Undefined index: show_download
« Reply #2 on: March 09, 2011, 12:40:42 AM »
Thanks IchBin, I actually forgot to check the bugtracker.  It's good to see this has been fixed for the next release.  :)