Viewing 6 replies - 1 through 6 (of 6 total)
  • I’m also getting this.

    Strict Standards: Non-static method GFCPTAddon::get_base_path() should not be called statically in /srv/www/example.com/htdocs/wp-content/plugins/gravity-forms-custom-post-types/gfcptaddon.php on line 55
    
    Strict Standards: Non-static method GFCPTAddon::get_base_path() should not be called statically in /srv/www/example.com/htdocs/wp-content/plugins/gravity-forms-custom-post-types/gfcptaddon.php on line 58

    Do you have an idea of when you are going to fix this?

    I’m also hitting this issue and will resolve with a single code change on line 121 of gfcptaddon.php:

    protected function get_base_path(){

    becomes…

    protected static function get_base_path(){

    Thread Starter Red Deer Web Design

    (@bdbolin)

    I believe I tried that in the past – no dice.

    I’ve since updated a few other plugins and it resolved the issue.
    And turned off error reporting ??

    Temporary solution at the very least.

    The solution that I’ve suggested above does appear to resolve to error for me.

    Yep benamozza’s method worked for me too, at least in terms of removing the error. I haven’t tried using the plugin fully yet though.

    Yes, that fixes it, and I’ve done the same change to resolve that warning. Can we get this in the next release, so updating the plugin doesn’t start displaying the warning, again?

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Strict Standards Error V3.0.1’ is closed to new replies.