simplemap icon indicating copy to clipboard operation
simplemap copied to clipboard

New entries with a Map field must be saved twice before they show up in search results

Open jrrdnx opened this issue 4 years ago • 4 comments

Description

I'm not sure if this is due to the new Draft workflow in Craft 3.6, but when I add a new entry that contains a Map field it must be opened and saved again before it will appear in the search results. All of the address information is saved and doesn't need to be re-entered, but the entry doesn't show up in the results when searching by location until it's re-saved.

Steps to reproduce

  1. Create a new entry in a channel with a Map field and hit Save.
  2. Load up the template with the following tag:
{% set serviceCenters = craft.entries()
    .section('serviceCenters')
    .serviceCenterLocation({
        location : searchLocation,
        radius : searchDistance,
        unit: 'mi',
    })
    .orderBy('distance')
    .limit(50)
    .all()
%}
  1. The new entry does not appear in the results.
  2. Open up the entry and (without making any changes) save it again.
  3. Return to the front-end page and hit refresh and the entry now shows in the search results.

Additional info

  • Craft version: 3.6.4.1
  • Maps version: 3.9.0.2
  • PHP version: 7.4.11
  • Database driver & version: MySQL 5.7.32
  • Other Plugins:
  • Amazon S3: 1.2.11
  • Cookies: 1.1.12
  • CP Field Inspect: 1.2.4
  • Embedded Assets: 2.4.5
  • Feed Me: 4.3.5.1
  • Freeform: 3.10.6
  • Mix: 1.5.2
  • Neo: 2.8.18
  • Redactor: 2.8.5
  • Redirect Manager: 1.1.1
  • SEO: 3.3.30
  • Super Table: 2.6.7
  • Typed link field: 1.0.24

jrrdnx avatar Feb 08 '21 21:02 jrrdnx

We've just been notified that this is also affecting a client on an older version of Craft CMS 3.4.23 and Maps 3.8.4.

jrrdnx avatar Feb 17 '21 12:02 jrrdnx

We're encountering the same problems, see issue #271 . Doesn't seem like there is any progress. Our deadline is coming up, so we'll probably look into fixing this ourselves or refactoring to a different plugin.

fthues avatar Feb 24 '21 09:02 fthues

We're encountering the same problems, see issue #271 . Doesn't seem like there is any progress. Our deadline is coming up, so we'll probably look into fixing this ourselves or refactoring to a different plugin.

Did you find a way to fix this yourself? Would be interesting to know.

Antimated avatar Mar 31 '21 14:03 Antimated

Has this plugin been abandoned?

kerns avatar Apr 18 '21 21:04 kerns