Search broken?

[tibaltfox]

Apologies if this has already been addressed. I tried to search for it, but, you know.. I couldn't

At first I thought it was just a me-problem, something temporary, but now that it's continuing across multiple platforms and browsers I'm wondering if it's a broader issue.

Search box does not work for me. It returns the following error:
"The database value you're trying to insert does not exist: id_search"

I am currently running CrunchBang Linux 9.04.1 and using Chromium. However, the problem for me seems echoed on both Firefox and Chromium, not just on CrunchBang/Ubuntu but on Fedora 13 as well (OS info is probably irrelevant, but for the sake of debugging and in case I am, indeed, the only one experiencing this issue, thought I'd mention it anyways).

[Renegade-Sandwich]

that happens to me to. I have no idea why.

[MangoPaws]

I noticed this a while ago, and then it worked for like a day, and then it didn't again.

[Spaz]

This has been happening to me, too. Figured it was just my wonky connection.

[Harlan]

It happens with me occasionally, just on and off.

I'm using the latest version (whatever that is) of Firefox on 64-bit Vista Ultimate.

[Mudd]

Honestly guys, replying to this thread stating that it's "Happened to you before too" isn't going to help any at all. At least tell us what Browser you're running or something like that so it makes our lives easier. While this too has happened to me, and I use Firefox, it only happens when I search something that isn't really a word.

Ex: I search "Lucky" and stuff came up. I then searched "lol" and got the error.

This could also be because people are searching at the same time and could cause a problem, but that's just a wild guess.

[Natasha Softpaw]

I never use the search function, so I never noticed this, it's probably been broken since the upgrade.  I just looked into it, and I should be able to fix it soon-ish.

This is why I keep saying if something is broken, tell me about it, never assume that I already know.  Because, most likely, I don't already know; you wouldn't have seen it broken if I did.

Honestly guys, replying to this thread stating that it's "Happened to you before too" isn't going to help any at all. At least tell us what Browser you're running or something like that so it makes our lives easier. While this too has happened to me, and I use Firefox, it only happens when I search something that isn't really a word.

Ex: I search "Lucky" and stuff came up. I then searched "lol" and got the error.

This could also be because people are searching at the same time and could cause a problem, but that's just a wild guess.

While the first part is excellent advice, in this case it's a server-side issue caused by the manual intervention I had to do to get the upgrade to work, so browser information is irrelevant.  Basically, there's a difference in database structure between versions that I didn't correct for when I had to essentially restructure the database tables manually.

[tibaltfox]

I never use the search function, so I never noticed this, it's probably been broken since the upgrade.  I just looked into it, and I should be able to fix it soon-ish.

This is why I keep saying if something is broken, tell me about it, never assume that I already know.  Because, most likely, I don't already know; you wouldn't have seen it broken if I did.

Honestly guys, replying to this thread stating that it's "Happened to you before too" isn't going to help any at all. At least tell us what Browser you're running or something like that so it makes our lives easier. While this too has happened to me, and I use Firefox, it only happens when I search something that isn't really a word.

Ex: I search "Lucky" and stuff came up. I then searched "lol" and got the error.

This could also be because people are searching at the same time and could cause a problem, but that's just a wild guess.

While the first part is excellent advice, in this case it's a server-side issue caused by the manual intervention I had to do to get the upgrade to work, so browser information is irrelevant.  Basically, there's a difference in database structure between versions that I didn't correct for when I had to essentially restructure the database tables manually.

At first, like many people here, I thought it was just some strange client-side thing going on. Especially seeing as I hadn't heard any complaints from any one else on the matter.
But, given the choir of 'amens!' received here, server side makes sense

Yay for fixinz!
I think Ms. Natasha deserves a round of applause,
for, you know, being an awesome admin and stretching herself well beyond her means..
like, I dunno, some thick, invulnerable rubber band..
OF AWESOME THINGS.

Thanks Natasha. No rush :3.
*claps*

[copb.phoenix]

And again, I get this error.

Tried "youtube videos"

[TheOneWolf]

It only happens when I search site-wide.  If I searchfor collar in General Chatter, I find the collar thread.If I search site-wide, I get the error. To search in general chatter, you go to General Chatter and search, just to clarify.

[Natasha Softpaw]

This has been fixed.  Let me know if it's still an issue.

And, even though no one ever listens to me, PLEASE report ANY problems you encounter anywhere else on the site, because I can't fix it if I don't know about it.  NEVER assume I'm already aware unless there's a thread about it, or unless you've talked to me directly about it.  There are few things that anger me more quickly than finding out that something on the site has been broken for months and not a single person told me about it; seeing a thread pop up with a bunch of people having the same problem, who never told me it was a problem, makes this much worse.

[tibaltfox]

This has been fixed.  Let me know if it's still an issue.

And, even though no one ever listens to me, PLEASE report ANY problems you encounter anywhere else on the site, because I can't fix it if I don't know about it.  NEVER assume I'm already aware unless there's a thread about it, or unless you've talked to me directly about it.  There are few things that anger me more quickly than finding out that something on the site has been broken for months and not a single person told me about it; seeing a thread pop up with a bunch of people having the same problem, who never told me it was a problem, makes this much worse.

We're sorry Natasha! *bakes you cookies*
People probably just don't want to bother you, having the best intentions at heart and all :3

Ladies and gentleman, we have search!
*cheers*