Public area => Bug reports => The Pub => Archived fixes => Topic started by: billy2 on March 26th, 2012, 04:24 PM
Title: Database Error
Post by: billy2 on March 26th, 2012, 04:24 PM
Keep coming back to this for a while now. Been at least 15 mins between tests - still happens.
Search > Save Drafts > top result
and get this on clicking the 1st result
Notice: Undefined index: nav_buttons in ../Themes/default/Display.template.php on line 841
Warning: Invalid argument supplied for foreach() in ../Themes/default/index.template.php on line 885
Pages: « previous 1 [2] Go Down Notice: Undefined index: get_message in ../Themes/default/Display.template.php on line 32
Fatal error: Function name must be a string in ../Themes/default/Display.template.php on line 32
Also..... Cannot post a screen shot even though its 35kb jpg
:edit: I know you are working on display template - so could be connected :edit: seems to be first line in many screens
Title: Re: Database Error
Post by: Norodo on March 26th, 2012, 04:37 PM
I have something similar:
Bug:
(click to show/hide)
When I press next:
(http://puu.sh/mtha)
in this http://wedge.org/pub/plugins/7274/plugin-facebook-for-wedge/msg276296 on page two
I get
Posted: March 26th, 2012, 04:36 PM
Also my image doesn't show up in my post...
Title: Re: Database Error
Post by: Nao on March 26th, 2012, 04:38 PM
Yeah I may have broken something that doesn't fail for me.
I know that posting a new message will break the database for me. I'm taking a break because this is all fucke up really. Im not even sure the SMF codebase works in reverse mode.
Title: Re: Database Error
Post by: billy2 on March 26th, 2012, 04:52 PM
nice an easy does it ;)
Title: Re: Database Error
Post by: Nao on March 26th, 2012, 05:15 PM
Norodo: the images don't show up because of the url tag bug. Whenever you edit a post, make sure to remove any url tags before you submit, otherwise they'll break. I also removed your second image because it has full paths in it.
Also, I wanted to point out that the numerous errors are due to the Display.php file not completing its run, and still not cancelling the Display template calls (that, in itself, is also a bug I'd say.)
The database error is due to the message list being request with a "LIMIT -1" which isn't supported. This is one of the tons of bugs I'm currently working on... I've got to say, it's been a long time since I haven't got as many PHP bugs in a row.
Title: Re: Database Error
Post by: Norodo on March 26th, 2012, 05:19 PM
I also removed your second image because it has full paths in it.
Ah. Sorry. Didn't notice that, and didn't think twice since the error is "public". :S
Well. Take it easy. No stress.
Title: Re: Database Error
Post by: Nao on March 26th, 2012, 05:29 PM
Yeah but it won't be 'public' in a few hours, and this topic will stay here forever... ;)
Anyway. I'm currently exploring a different path for topic=xxx.msg1234. Instead of transforming message ID 1234 into a page offset, I'm simply keeping the 1234 and hoping it'll be enough to calculate the offset. It seems to be working for now... Fingers crossed.
Title: Re: Database Error
Post by: Norodo on March 26th, 2012, 05:33 PM
As I said I didn't think about it :)
Title: Re: Database Error
Post by: Nao on March 26th, 2012, 06:02 PM
Okay, 'normal order' pages seem to be okay... Which is an impressive feat considering I've rewritten quite an important thing... I'll see about reverse order pages now. Oh, and I think that the 'all pages' feature is broken... I'll need to enable it in Wedge to test it.
Title: Re: Database Error
Post by: Arantor on March 29th, 2012, 12:54 AM
So, is this still a reproducible error?
Title: Re: Database Error
Post by: Nao on March 29th, 2012, 08:00 AM
It can be reproduced by provoking a database error inside Display.php, which no longer happens ;)
Title: Re: Database Error
Post by: Arantor on March 29th, 2012, 12:00 PM
Hahahaha, yes, I expected that one :P But it doesn't do it as standard, no? (If not, it can be sent to the archive.)
Title: Re: Database Error
Post by: Nao on March 29th, 2012, 12:41 PM
Nope, it doesn't. Yes, do yourself the pleasure of archiving it ;)
(Wondering whether we really need to use the 'Fixed' prefix in subjects... There's already the board name...)
Title: Re: Database Error
Post by: Arantor on March 29th, 2012, 05:24 PM
The 'fixed' prefix was only relevant before we had the archive board :P
Title: Re: Database Error
Post by: Nao on March 29th, 2012, 05:39 PM
Yup...
BTW I'm considering opening a Test board, which would be ignored automatically from the homepage's recent topics list and generally from post counts. What do you think?
Title: Re: Database Error
Post by: Arantor on March 29th, 2012, 05:55 PM