• Hey guys,

    Just wanted to tell that the feature/function you’ve introduced to the plugin is a massive risk for a lot of installs. It broke two of my plugins that rely on javascript (BuddyPress, BuddyPress Global Search) and an addition broke javascript in my theme.

    I think it’ll make a lot more sense to use this plugin for tracking the IPs of comments/users and make all the other options opt-in only. It literally took me half a day to find this issue, since it’s pretty much the last place where you’d expect to look when debugging.

    Hopefully you’ll do something about this because honestly just rewriting parts of the output of everything printed on a page on the page is a big deal. It breaks things you know ??

    Thanks for the awesome service Team CloudFlare ??

    https://www.ads-software.com/plugins/cloudflare/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author simon-says

    (@simon-says)

    Hi Bowe,

    Thanks for your feedback and sorry you had this issue, as you noticed you can disable this. We’d like to understand what didn’t work for you here, can you send us a support ticket perhaps with an example of the HTML that was rewritten?

    Simon

    Thread Starter Bowe

    (@bowromir)

    Hey Simon,

    Sure thing! Where do you want me to submit the support ticket?

    Here’s what I’ve found that causes this issue.

    With CloudFlare Plugin Activated

    <form role="search" method="get" id="searchform" class="searchform" action="//www.sensei.net/">
    				<div>
    					<label class="screen-reader-text" for="s">Search for:</label>
    					<input type="text" value="" name="s" id="s" class="form-control">
    					<input type="submit" id="searchsubmit" value="Search">
    				</div>
    </form>

    Without CloudFlare Plugin Activated

    <form role="search" method="get" id="searchform" class="searchform" action="https://www.sensei.net/">
    				<div>
    					<label class="screen-reader-text" for="s">Search for:</label>
    					<input type="text" value="" name="s" id="s" class="form-control ui-autocomplete-input" autocomplete="off">
    					<input type="submit" id="searchsubmit" value="Search">
    				</div>
    </form>

    It seems to do a rewrite on form actions, which causes the issues with certain plugins and scripts.

    Plugin Author simon-says

    (@simon-says)

    Hi Bowe,

    Could get in touch with our support team by submitting a ticket here:

    https://support.cloudflare.com

    And share with us some steps to replicate the actual issue that will help us understand more. It’s valid to use protocol relative tags in form actions, so this should not cause an issue, but there may be some edge cases with other scripts we need to consider.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Protocol rewriting function is a big risk for lots of sites.’ is closed to new replies.