Topic RSS
11:26 am
I have a new version of this problem. I get "a suspect request has been rejected" when using the standard search field on my site, and am not running WP-UserOnline plugin.
I have Wordpress v 2.8.5 and did not notice the problem before upgrading, though it could have occured before and passed by unnoticed.
I'm running the following plugins:
Akismet
All in One SEO Pack
AZIndex
Category Posts Widget
Exec-PHP
Google XML Sitemaps
NextGEN Gallery
Official StatCounter Plugin
Simple:Press Forum (go figure :P)
Twitter Tools
WordPress.com Popular Posts
WordPress.com Stats
WP-PostRatings
Yet Another Featured Posts Plugin
Yet Another Related Posts Plugin
Any ideas as to what might cause this problem? You can check the site at http://violentcinema.se , to search check out http://violentcinema.se/sok
most odd. how the hell is it doing that? its trying to make a simple text string output and making it the page title???
Guessing its another conflict. I have bumped the priority of this ticket we have to try to figure out how in the hell other plugins are invoking our sanitization routine (or why it might be running).
I would disable all your plugins, clear your browser cache and try it again. If it works now, it is some sort of conflict, so start enabling them one by one until it breaks. if a second conflict is found, it might give us more info to understand this.
very highly unlikely related to wp 2.8.5
I'm running WPMU and had the same conflict between WP-User-Online and SimplePress 4.1.2. Commenting out the iine in the WP-User-Online plugin as described earlier in this thread corrected the problem.
I've been using Simple Press on this particular site for nearly a year but never had this problem prior to upgrading to 4.1.2.
4.1.2 strengthened security in a few areas too which is what the message is all about. but we havent yet been able to ascertain why it would even be called/activated on the media loader and/or how it users online conflicts.
we have a ticket open on this and will get to the bottom of it.
part of the problem is I cannot duplicate the issue locally with wp users online. clearly something afoot as multiple users are experiencing the issue and resolution, but hard to debug when I cannot get the error to occur. I only have standard wp, but users are reporting it with both wp and wpmu.
Actually, I am able to no duplicate it. argh, have been testing on my spf 4.2 sites… which is a bad new – good news issue. It does appear to be an issue related to 4.1.2, but good news is that it does not occur (at least for me) with the upcoming 4.2 version…
will still see if I can figure out what the issue is so folks can use both before 4.2 releases…
If those of you having this issue, could try a quick workaround for me and let me know the results, it would be appreciated…
in simple-forum/sf-header-forum.php at line 285, find this code
if(isset($_GET['search']))
{
if($_GET['search'] != '') $sfvars['searchpage'] = sf_syscheckint($_GET['search']);
} else {
$sfvars['searchpage'] = 0;
}
if(isset($_GET['value']) ? $sfvars['searchvalue'] = attribute_escape($_GET['value']) : $sfvars['searchvalue'] = '');
if(isset($_GET['type']) ? $sfvars['searchtype'] = sf_syscheckint($_GET['type']) : $sfvars['searchtype'] = 0);
if(isset($_GET['include']) ? $sfvars['searchinclude'] = sf_syscheckint($_GET['include']) : $sfvars['searchinclude'] = 0);
$sfvars['searchresults']=0;
and change it to be the following instead…
if(isset($_GET['search']))
{
if($_GET['search'] != '') $sfvars['searchpage'] = sf_syscheckint($_GET['search']);
if(isset($_GET['value']) ? $sfvars['searchvalue'] = attribute_escape($_GET['value']) : $sfvars['searchvalue'] = '');
if(isset($_GET['type']) ? $sfvars['searchtype'] = sf_syscheckint($_GET['type']) : $sfvars['searchtype'] = 0);
if(isset($_GET['include']) ? $sfvars['searchinclude'] = sf_syscheckint($_GET['include']) : $sfvars['searchinclude'] = 0);
} else {
$sfvars['searchpage'] = 0;
}
$sfvars['searchresults']=0;
and see if that fixes it up… you might want to do a forum search on your site too and make sure it still works.
Yep, that worked on my test site!!!
(did remember to put the wp-useronline.php back to its original version first, check if "suspect request" came up again, it did, then applied your code >> problem gone; search also worked).
Most Users Ever Online: 444
Currently Online: jawaulk, BlueDagger, irlandes1
69 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
-Radio-: 1251
Lee H: 606
Luffer: 535
Conrad_Farlow: 502
jim: 478
neon: 263
ovizii: 240
Tal: 240
Member Stats:
Guest Posters: 2626
Members: 7363
Moderators: 1
Admins: 2
Forum Stats:
Groups: 5
Forums: 16
Topics: 10897
Posts: 79582
Newest Members: Rick Thomas, joelrob, ndc, MacBravO, irlandes1, triphop, betokan, Jonathan Yovani Muñoz, somosguatemala, ahcreate
Moderators: Brandon C (162)
Administrators: Yellow Swordfish (22240), Mr Papa (23688)
Log In
Register
Home
Add Reply
Add Topic
Quote
Offline



Visit

Privacy Policy



