WP Find Your Nearest
[resolved] Could anyone decipher this error message! (7 posts)

  1. adamjsmith
    Posted 3 years ago #


    I am getting an error at the top of my results,

    Warning: deg2rad() expects parameter 1 to be double, string given in /home/traindri/public_html/******.info/wp-content/plugins/wp-find-your-nearest-premium/includes/getFYNSearchResults.php on line 60

    Is anyone able to help resolve it.



  2. adamjsmith
    Posted 3 years ago #

    Never mind, seems to be better now I've added tags/categories.


  3. j007jim007
    Posted 3 years ago #

    Hi Adam,

    I've got the same problem, tried adding some tags/categories to all FYN items but still getting it?

    Did you do anything else?

  4. adamjsmith
    Posted 3 years ago #

    Sorry, no, in the end that was enough. Sorry I couldn't be more help.

  5. Adam Sargant
    Posted 3 years ago #

    This error occurs if you have FYN items that don't have a latitude and longitude associated with them

  6. FreshIdeaWebsites
    Posted 2 years ago #

    This error appears twice (2x) at the start of any search results... but also lists the correct results. Can I assume that I have 2 entries without L&L values? If so, is there a quicker method to find/list those incorrect records (we currently have 100 listings)
    Would it be worth adding a php stmt to 'not' display these error codes?

    apprect your help

  7. FreshIdeaWebsites
    Posted 2 years ago #

    FYI...manually scanning the wp db identified my 2 errors
    Table = wp_postmeta
    Field = meta_key = _aphs_FYN_postcode
    I found one PCode value with no space (CDN pcode is A9A 9A9) it was entered as A9A9A9
    The second had a space as first character (eg. <space>A9A 9A9)
    In both these cases, the php function would be looking for a numeric value at a certain position but read an alpha character instead. Hence the php error "expected parameter to be double, string given" (in plain eng, 'expected to see a number, but saw a letter instead)

    Manually correcting both these records removed the Warning error.
    Hope this helps...Rob

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • WP Find Your Nearest
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic