Support » Plugin: SimpleMap Store Locator » Fatal error

  • Resolved Tim Derouin

    (@tderouindesign)


    There is an error within the SimpleMap plugin that is causing other issues (intermittent 500 internal error) on our website. Do you know how to resolve the error listed below?

    PHP Fatal error: Call to a member function get_options() on a non-object in /home/username/domain-name/web/wp-content/plugins/simplemap/classes/maps.php on line 110

    Thank you for any assistance you can provide!

    https://wordpress.org/plugins/simplemap/

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    How often does that happen? That line is where it’s loading the options. Any idea what the circumstances are where you see it?

    $defaults = $simple_map->get_options();

    Tim Derouin

    (@tderouindesign)

    It is an error that our web hosting company says comes up all the time. However, the 500 internal server error was found to be unrelated to the SimpleMap plugin. That being said, I am not sure if anything needs to be done. I appreciate any insight you may have but we should be all set.

    Thanks!

    I just upgraded to 2.4.10 and it took my entire site down with a 500 internal server error as well. I’m trying to roll back to 2.4.9, but am struggling to find it.

    Any help would be appreciated!

    After finding 2.4.9 on GitHub I installed it and got the following fatal error:

    Plugin could not be activated because it triggered a fatal error.
    Parse error: syntax error, unexpected ‘:’ in /var/www/…/wp-content/plugins/simplemap/classes/widgets.php on line 54

    Plugin Author Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Hi DJ Lein,

    You should make a separate thread instead of hijacking another person’s.

    We inadvertently introduced a PHP 5.3 requirement in 2.4.9+. We’ll address it for the next release, but in the meantime you can fix it by updating to a newer version of PHP. PHP 5.2 reached end of life 5.5 years ago.

    Sorry about the threadjacking, Michael. I saw it marked as resolved, but didn’t really think the issue was resolved–at least the commentary wasn’t all that descriptive/helpful to others.

    Your note on the PHP 5.3 requirement is extremely helpful though. Thank you for the prompt response.

    Plugin Author Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    These are unrelated topics, and each should be in its own thread. This was marked as resolved because Tim said it was resolved in that the hosting company confirmed that his problem was unrelated to SimpleMap.

    https://codex.wordpress.org/Forum_Welcome#Where_To_Post

    “Posting your own topic is smiled upon. Unless you are using the same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme, and configurations as the original poster, do not post in someone else’s thread. Start your own topic.”

    Meanwhile, I’ve opened a Github issue for your problem. https://github.com/semperfiwebdesign/simplemap/issues/91

    Either way, I recommend installing the latest version of SimpleMap, and upgrading PHP (ideally to 7, but certainly later than 5.2).

    Tim Derouin

    (@tderouindesign)

    I am once again having (seemingly the same) problem. The hosting company had to boost our php memory limit from 128 to 256M due to a simplemap error as seen below.

    Fatal error: Call to a member function get_options() on a non-object in /home/domainname/web/wp-content/plugins/simplemap/classes/maps.php on line 121

    This resolved the problem but we cannot keep requesting a php memory boost. Any idea as to what may be causing the fatal error? In addition, I wanted to point out that clicking on “Clicking this link will remove all data from the database.” and then clicking OK on the popup does not remove anything from the database as all my settings were still present after deleting and installing a clean version of the plugin to try and elminate the error.

    Any help you can provide would be greatly appreciate. Thank you for you time.

    Plugin Author Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Tim, Thank you for the report.
    We have issues opened to investigate each of these.

    We recommend have a 256M+ PHP memory limit. There’s no reason for your host to arbitrarily restrict you to something lower than that.

    Tim Derouin

    (@tderouindesign)

    Thank you for your time Michael. I look forward to hearing from you regarding the results of your support team’s findings.

    Plugin Author Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    @tderouindesign

    Have you had this problem since? I’d love to know some more information about your setup so we can try and troubleshoot this, as we’ve been unable to reproduce it. Generally SimpleMap takes very very little memory.

    https://github.com/semperfiwebdesign/simplemap/issues/104

    Tim Derouin

    (@tderouindesign)

    Good morning Michael. I have not had the issue come up since my last message (and have installed and setup the plugin on a couple other websites since then). It truly appeared to be something that the hosting company was having issues with and not necessarily the SimpleMap plugin. As always, I appreciate the follow up and find that whether my premium support has expired or not I always receive great assistance on both the WordPress support forums and premium SimpleMap support.

    Plugin Author Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Hi Tim,

    Thank you for letting me know. You may want to install a tool like the Query Monitor plugin peek under the hood a bit. SimpleMap itself *shouldn’t* be taking up a lot of memory.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Fatal error’ is closed to new replies.