Viewing 7 replies - 31 through 37 (of 37 total)
  • Hi @@clompers,

    Cloudflare will only cache wp-admin if you set “Cache Everything” page rule. To avoid it you should add a page rule to bypass cache for wp-admin.

    @k0872, it looks like your error is similar to this post

    @thellimist thanks

    I have set a rule in page rules to bypass /wp-admin/* but still get the grey screen.

    which is the config.js 404

    aslo putting it into developement mode, should overide the admin cache if it is , but this does not help

    • This reply was modified 8 years, 1 month ago by k0872.

    @k0872 can you post your PHP error logs and your browser console logs?

    Thanks

    I have no php errors.

    in the console- network all I get a 404 for the config.js file

    browser console logs will show the url of my site which I dont want on this forum.

    renaming my htacces file allows access to the admin section?

    so there is a conflict in my htacccess file?

    but I am not sure what.

    @furkan811
    Ok, so I’m pretty sure I figured out what the issue here is. At least this definitely solved it for me.

    As I got into it more and more and read @k0872 post about how the config.js file was 404ing. I was confused about why that file was even being called so I started looking into the compiled.js file that is actually being called in my wp-admin area. Of course as you know it is using source maps. Previously I had a similar issue with css source maps not working correctly after being packaged for production. It was missing dependencies.

    So moral of the story, I SSH into my server and cd into the cloudflare plugin folder. Run composer update, activate the plugin, enter my credentials, works flawlessly. Don’t even need the hotfix that was posted above.

    So anyone with this issue and shell access to their server:
    install composer (if you don’t already have it)
    https://getcomposer.org/doc/00-intro.md#installation-linux-unix-osx

    composer update

    Activate the plugin
    Enter your credentials

    Either your lock file is out of date before you are packaging for production or your packaging script isn’t setting up the source maps correctly.

    @k0872, @clompers, @runofthemill, @visionitse, @defunctlife, @mantukai, @dacosta1979, @maryouli_com, @minato3, @jpforte

    Hi all. We’ve released 3.0.4. The problem should be fixed.

    If you still have issues please open a new topic with the following information

    – Description of the error
    – PHP version
    – PHP error log

    Thanks.

Viewing 7 replies - 31 through 37 (of 37 total)
  • The topic ‘blank settings page. 3.0.3’ is closed to new replies.