Page 1 of 1
[SOLVED] Search module warning
Posted: Tue Jul 17, 2007 1:26 pm
by halm
After upgrading to CMSms 1.1, I get this when using the search module:
Code: Select all
Warning: Parameter origreturnid is not known... dropped in .../lib/misc.functions.php on line 1252
What's this now?
Re: Search module warning
Posted: Tue Jul 17, 2007 2:23 pm
by donnut
I've the same problem, also after upgrading to version 1.1.
The error occurs when using the search functionality on a page for the first time. The search does show the normal results (besides the warning). In my case the results are displayed in a different resultpage:
When the search is performed in the searchbox on the resultpage the warning does not appear.
Erwin
Re: Search module warning
Posted: Tue Jul 17, 2007 2:37 pm
by tsw
this one sneaked through our radar. we are going to release new version of news asap
Re: Search module warning
Posted: Wed Jul 18, 2007 8:20 am
by halm
I'd prefer a Search update, really
Re: Search module warning
Posted: Wed Jul 18, 2007 7:55 pm
by tsw
doh, its not the first time I've mixed these two up
Re: Search module warning
Posted: Tue Jul 24, 2007 2:09 pm
by mhokie
any word on the search update?
Re: Search module warning
Posted: Wed Jul 25, 2007 12:05 am
by izzysanime
o good, so I'm not the only one with the same problem, At least that is solved, just need that update.
Thanks,
Josh
Re: Search module warning
Posted: Sun Jul 29, 2007 6:02 pm
by Peter.Schwab
Quick and dirty solution (works for me and my clients):
commenting out lines 48 - 51 in /modules/search/action.default.php
Code: Select all
//if( $origreturnid != $returnid )
// {
// $hidden .= $this->CreateInputHidden($id, 'origreturnid', $origreturnid);
// }
I cannot say, how "dirty" this solution is. By now I have not seen any side effects though.
Best wishes
+peter+
Re: Search module warning
Posted: Sun Jul 29, 2007 8:08 pm
by tsw
Re: Search module warning
Posted: Fri Aug 03, 2007 8:52 am
by halm
Thanks guys! I've been offline for a while and haven't had the chance to applaud you.
There's a big [SOLVED] in the subject line for you
Purely platonic, but gratefully:
