[Resuelto] Map 1.8.3 still not working right with MariaDB

[Autor]

Mensajes

[scottL-3]

I am trying to: distance search in a View with Maps

Link to a page where the issue can be seen:
Working (maps 1.7.4): enlace oculto
Not Working (maps 1.8.3): enlace oculto

I expected to see:
10 or more partners in a radius of 30 miles of the search center.

Instead, I got:
2 partners in a radius of about 2 miles of the search center.

I fixed this on the live site by downgrading to Maps 1.7.4 again. Kept 1.8.3 on staging so you can see the difference. The only difference between these two sites is the Toolset Maps version.

[Luo Yang]

Hello,

I have checked the Debug information you provided above, the MYSQL version is 5.5.5.

According to our server requirement document:
https://toolset.com/toolset-requirements/
the minimum requirements to run Toolset plugins: MySQL 5.6 and above.

It is same requirement as WordPress:
https://wordpress.org/about/requirements/

Can you try to upgrade the your MariaDB db version to MariaDB-10.1 or above, see MariaDB document:
enlace oculto

[scottL-3]

Thanks Luo.

I had Kinsta update the staging site to MariaDB 10.4 and it did not change the results. The search there still returns only 2 results where it should return 10 or more. Now the only difference between staging and live is that live has the older version of Maps (1.7.4) and works properly and staging has the newer version of Maps (1.8.3) AND MariaDB 10.4 and does not work properly for distance search.

[Luo Yang]

The problem you mentioned above is abnormal, please try these:

1) In case it is a compatibility problem, please deactivate all other plugins, and switch to wordpress default theme 2019, and test again

2) Also check if there is any PHP/JS error in your website:
https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/

3) If the problem still persists, please provide database dump file(ZIP file) of your website, I need to test and debug it in my localhost, thanks
https://toolset.com/faq/provide-supporters-copy-site/

[Luo Yang]

Thanks for the details, I am downloading the files, will update here if there is anything found

[Luo Yang]

The SQL file you provided above is not valid, I get lots of SQL errors while importing it, see screenshot import-sql.JPG

After import the sql file, there are lots of databse table missing, so please try to export the database dump file with duplicator plugin, you can export database only by following their document:
enlace oculto

[scottL-3]

Please set my next reply to private and set it so I can attach the SQL file again. I am able to import the file into a local MySQL and see the tables and entries so the issue may have been in the upload process or the zipping of the file. I compressed this one during export, uncompressed it, imported it into a new database successfully so I'll try sending you this one in next reply.

[Luo Yang]

OK, I have enabled the private message box again, please provide the new database dump file again, thanks

[Luo Yang]

Thanks for the details, I am downloading the files, will update here if there is anything found

[Luo Yang]

The database dump file is not valid too, I get the same SQL errors as I mentioned in screenshot:
https://toolset.com/wp-content/uploads/2019/09/1333141-sql_import.jpg

So please follow the document I mentioned above to export the database dump file:
https://toolset.com/faq/provide-supporters-copy-site/

you can export database only by following their document:
enlace oculto

Private message box enabled again. thanks

[Luo Yang]

Thanks for the details, I can import the duplicator package and see the same problem in my localhost, and I am trying to debug it, will update here if there is anything found.

For the database dump file problem, I was using MarioDB console to import the sql file.

[Luo Yang]

Here are what I found, it should be a problem of post view "Test Installer Finder", I have tried to create another new post view, with same distance filter, it works fine, see screenshot: distance-filter.JPG.

I suggest you created another new post view, and test again.

[scottL-3]

Can you escalate this to a developer? If the problem goes away when switching to a different but identical View, then the cache of locations or some other data must be at fault unless the View itself is somehow corrupted. This is a complicated View and if all customers on MariaDB have to rebuild their Views to work with the newer version of Maps, that is not very good for Toolset's business and will make people leery of Toolset. We (Toolset and me) need to know the root cause here not just that re-creating the View makes the problem go away.

I will try to re-create the View and see if it helps here too but I'd really like to know what the actual problem is.

[Luo Yang]

Yes, there might be a cache problem, you can disable Views cache by this:
Edit the page "Find an Installer", replace views shortcode from:
[wpv-view name="test-installer-finder"]

To:
[wpv-view name="test-installer-finder" cached="off"]

And test again.

More help:
https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-view
cached (opt):
off
Turns off the caching system for the View.

[scottL-3]

Unfortunately, set cached to off doesn't change the outcome. Same problem.

Also, if I re-create the view in a new view and change the page to use the new view, I get the same result so not sure why it worked differently for you. Are you sure you tested on MariaDB?