Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • The new version they just pushed updated the dependencies so just grab the newest 3.0.4 and you should be good.

    Try this:

    SSH into your server and cd into the cloudflare plugin folder. Run composer update, activate the plugin, enter credentials.

    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

    Try this:

    SSH into your server and cd into the cloudflare plugin folder. Run composer update, activate the plugin, enter credentials.

    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

    @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.

    @furkan811 I just tested your fix on my development server and also my production server. Made the changes as per your instructions and also even went so far as to restart php to make sure it wasn’t caching any PHP files. I still get no change. The domain name is highlighted correctly in the drop down “Active Zone” but there is nothing else besides 3 blue buttons.
    Home, More Settings, Analytics.
    Then under that “Please select a domain that is provisioned with CloudFlare.”
    Then “Version: 3.0.3”

    When you switch pages nothing changes except the URL bar address.

    I get 0 PHP errors on server logs, global and per site logs checked on server.

    No errors in the console logs, which read like this

    
    JQMIGRATE: Migrate is installed, version 1.4.1
    Download the React DevTools for a better development experience: https://fb.me/react-devtools
     action @ 17:23:43.685 CONFIG_FETCH 
     action @ 17:23:43.818 CONFIG_FETCH_SUCCESS 
     action @ 17:23:43.820 CONFIG_UPDATE_BY_KEY 
     action @ 17:23:43.822 INTL_FETCH_TRANSLATIONS 
     action @ 17:23:43.825 USER_LOGIN_SUCCESS 
     action @ 17:23:43.828 ZONES_FETCH 
     action @ 17:23:43.831 @@router/TRANSITION 
     action @ 17:23:43.832 @@router/UPDATE_LOCATION 
     action @ 17:23:43.872 INTL_FETCH_TRANSLATIONS_SUCCESS 
     action @ 17:23:43.874 APPLICATION_INIT 
     action @ 17:23:45.192 ZONES_FETCH_SUCCESS 
     action @ 17:23:45.222 ZONE_SET_ACTIVE_ZONE 
     action @ 17:23:48.994 @@router/TRANSITION 
     action @ 17:23:48.995 @@router/UPDATE_LOCATION 
     action @ 17:23:49.891 @@router/TRANSITION 
     action @ 17:23:49.891 @@router/UPDATE_LOCATION 
     action @ 17:23:51.570 @@router/TRANSITION 
     action @ 17:23:51.570 @@router/UPDATE_LOCATION
    

    The last few entries are me switching pages.

    The only thing of interested I was able to dig up was, drilling into the ZONE_SET_ACTIVE_ZONE

    
    Object
    type
    :
    "ZONE_SET_ACTIVE_ZONE"
    zone
    :
    Object
    name
    :
    "website-domain.com"
    plan
    :
    Object
    name
    :
    ""
    __proto__
    :
    Object
    status
    :
    "inactive"
    type
    :
    ""
    __proto__
    :
    Object
    __proto__
    :
    Object
    

    This was in the “action” state. Not sure if the fact it says under the plan “inactive” means anything of value to you. I definitely have an active plan with the DNS properly configured, have been using it for a year flawlessly.

    Without really looking into it too far. I think it’s an issue with the ajax loading of the settings page.

    100% the correct account

    Yeah, it’s been on Cloudflare Pro Plan for around a year.

    Same here, after update it just is stuck on the page asking you to select a domain that is provisioned with CloudFlare. It auto selected my URL from the list but nothing else happens. Clicking on any of the buttons ‘Home’ ‘More Settings’ ‘Analytics’ does nothing either.

    PHP v7.0.11
    No PHP errors in the site log or global log
    WP v4.6.1
    Not on a subdomain, not multi-site
    Also no errors in browser (checked in chrome dev tools)

    • This reply was modified 8 years, 2 months ago by rifi2k.
Viewing 9 replies - 1 through 9 (of 9 total)