3.0.5 blank setting page

The root cause of the error is while requesting the resource config.js we’re settings the header to Accept: ‘text/javascript’. All browsers accept the header text/javascript but external security modules may only accept application/javascript header.

This allowed me to find fix for error…

I have access to IIS server so changed the MIME option on the wordpress website so that .js record was text/javascript rather than application/javascript.

There is a change that this will stop other js from working but if it does I figure that I can get access to fix settings and then chance MIME record back to stop any other js breaking.

Hi @ligken, your issue is different from others. Could you submit a support ticket to cloudflare.com with the following information;

– Link to this post.
– The URL shown in your browser when you’re in Cloudflare Plugin Settings page. It should be something similar to https://www.domain.com/wp-admin/options-general.php?page=cloudflare#/?_k=6x1xhw
– In WordPress Admin Panel: Settings > General Settings: WordPress Address (URL)
– In WordPress Admin Panel: Settings > General Settings: Site Address (URL)

Thanks

Hi @ninjayetiwordpressorg,

When we release plugin version 3.0.7 the issue should be fixed. You can revert your settings after updating.

Thanks

Hi @thellimist

done, ticket number Request #1272215

Thanks

WordPress 4.6.1
CloudFlare 3.0.6

Same issue and same error in Firebug (no config.js found but it’s there)

Waiting for the new version

Thank you

I upgraded to 3.0.6, but still a blank page with 406 error in the console. I will give it one more try when 3.0.7 or higher is released, if the error still occurs, then I am done with the CF plugin. Too much hassle for my time.

Hi all

Cloudflare WordPress Plugin 3.1.0 released. Could you verify regarding the issue being fixed.

Changelog: https://en-gb.www.ads-software.com/plugins/cloudflare/changelog/

Thanks

Yes thanks a lot, it’s function now. Great job (y).

Glad to hear that.

I’ve marked this topic as resolved. If you have any issues or suggestions related with the plugin please open a new topic.

Thanks everyone!

Just for the record, it has NOT been fixed!
Brian Brown, Ph.D.

I confirm it.

I stopped using that plugin months ago on all my sites, I guess it was a good idea.

Hi @brianbrown and @artigianidelweb,

The issue you’re having might be different than the one reported in this post.

Could you open a new post with a description on how to reproduce the error. Please provide:

– browser console logs
– Plugin version
– WP version
– SSL setting

We’ll look into it.

Thanks