• Resolved SLIS

    (@slis)


    Hi,

    I’m trying to fix some 404 errors, and Simple Firewall is conflicting with my redirection plugin. I get the following error: Warning: Unable to parse URL in…public_html/wp-content/plugins/wp-simple-firewall/src/common/icwp-data.php on line 136

    Ive been using both plugins for awhile and this is the first problem I’ve had so trying to figure out whats changed.

    Is there a way to fix so I can get my 404’s redirecting again?

    Thanks!

    https://www.ads-software.com/plugins/wp-simple-firewall/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Paul

    (@paultgoodchild)

    Where exactly are you seeing this error? What are you doing when it happens? And how is it conflicting with the 404 redirection?

    Thanks,
    Paul.

    Thread Starter SLIS

    (@slis)

    Hi Paul,

    The error shows at the top of my homepage when I click the soft 404 link in Google webmaster tools. I took a screenshot which I can send (just wasn’t sure if I should show code publicly or should do via email).

    The conflict is that the redirect doesn’t work and it just repeats the error.

    I tried again today and the redirects appear to be working now (although the error code still shows initially).

    What’s really weird are the links that are showing as 404 such as this (I left this unfixed for the moment):

    https://smellslikeinfinitesadness.com/search/2/page/17/+https%3A//www.facebook.com/SmellsLikeInfiniteSadness/

    I’ve been receiving several of these each month and I don’t know what is generating them in the first place? I just have them redirect to the general search page of my site.

    Any ideas would be great.

    Thanks!

    Plugin Author Paul

    (@paultgoodchild)

    For the next release I can try just silencing the warning message that comes from the PHP parse_url() function. It’s not actually an error that’s causing any interruption of code, except that that output might just come before sending the HTTP headers (which would be responsible for handling your redirects).

    So in that case, a PHP textual warning outputting before header directive would break your redirection.

    To help you get around this until I make the next release, open up the file: icwp-data.php that has the error and on line 136 where it has the function parse_url(), change nothing else on the line except just add the “@” symbol before it, i.e.:

    @parse_url( ..... );

    That will silence errors and warnings and hopefully stop breaking your redirections.

    Hope it helps for now!
    Cheers,
    Paul.

    Thread Starter SLIS

    (@slis)

    Paul,

    Thanks so much! I’ll give this a go.
    Just to pick your brain: do you have any idea why I’m getting these weird “Facebook search page” 404’s in the first place? I just can’t figure out whats generating them.

    Thanks again,

    Michael

    Plugin Author Paul

    (@paultgoodchild)

    I honestly can’t say Michael what would be going on here.

    It could be facebook buttons you have on the pages are building their links incorrectly and you have a leading space character in the “href” field. That would be my only guess to that…

    Would you mind taking a few moments and dropping a review in for the plugin if you’ve found it to be useful? That’d be much appreciated…

    Thanks,
    Paul.

    Thread Starter SLIS

    (@slis)

    Paul,

    Certainly!

    Thanks for your prompt replies and info.

    Michael

    Plugin Author Paul

    (@paultgoodchild)

    Just letting you know that @parse_url is in place for version 4.4.0

    Cheers,
    Paul.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Conflict with Redirection Plugin’ is closed to new replies.