Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi there,

    I’m also experiencing this fatal crash but had the same issue on one of my custom ACF addons and found the workaround. The code has been running for years without a hitch but ACF did indeed change their API. https://www.advancedcustomfields.com/resources/integrating-custom-field-types/

    I got your plugin running by changing the Init.php by making sure that the Field is imported.

    
    use ACFGravityformsField\Field;
    

    And updated the addField function to use the new callback (which fills in the new REST api callbacks)

    
    /**
    * Add a new Field object for our newest version in Advanced Custom Fields
    */
    public function addField()
    {
    	acf_register_field_type('ACFGravityformsField\Field');
    }

    Cheers

    I’ve had the same problem on one of my sites. line 927 in search-everything.php calls sa_api(), which returns as Michael described an WP Error object. The site is 3-4 year old one, the last update to the plugin brought the problem (on the local dev site and the live site on the server). Research Everything compose-screen widget setting are both disabled and no Zemanta API key is given.

    Thanks you!

    Hi there,

    Just want to second the bug and the fix of it. I derived exactly the same version and now things work as they should. In my case it broke custom taxonomy filter on the admin listing screens.

    Thanks!

    Just stumbled over this post. It’s a bit late but for future reference …

    $memcached_servers = array(
      'default' => array(
        'unix:///tmp/memcached.socket'
      )
    );

    Works for me. Think the tripple slash is the secret sauce ??

    hello,

    I have had the chance to test php-fpm 5.5 with it’s new opcache and w3tc. All works fine but the opcache makes trouble as it caches the w3tc settings php files. Thus changes via the admin tool are not immediately visible which leads to confusion. Double saves and in my eyes sometimes even malfunctions. As opcache surely will be used more and more it might be good to use tweak your code to add opcache_invalidate(…) [https://www.php.net/manual/en/ref.opcache.php] for the affected scripts to make sure that the files are loaded new once the setting page’s confirmation page is rendered.

    Many thanks for your work!

Viewing 5 replies - 1 through 5 (of 5 total)