evoWeb / store_finder

Store finder extension for TYPO3
GNU General Public License v2.0
2 stars 9 forks source link

Evoweb\StoreFinder\Controller\Event\MapGetLocationsByConstraintsEvent::__construct() must be an instance of TYPO3\CMS\Extbase\Persistence\QueryResultInterface #35

Closed webworker-united closed 2 years ago

webworker-united commented 2 years ago

hey, in TYPO3 11.5.8 with your current store_finder version 6.0.0, we got this error in frontend:

Argument 2 passed to Evoweb\StoreFinder\Controller\Event\MapGetLocationsByConstraintsEvent::__construct() must be an instance of TYPO3\CMS\Extbase\Persistence\QueryResultInterface, array given, called in /var/www/html/public/typo3conf/ext/store_finder/Classes/Controller/MapController.php on line 191

thanks in advance for solving

mschwer commented 2 years ago

Hi @evoWeb , is there any solution in to this problem? I am having the same problem. storefinder_show seems to work correctly, storefinder_map is causing the above written frontend error.

Thanks for your feedback!

marcelmarty commented 2 years ago

Same problem here on TYPO3 11.5.4 and store_finder 6.0.0

studio65digital commented 2 years ago

Same here. TYPO3 Version 11.5.10

garbast commented 2 years ago

Should be resolved in branch develop. Please test and i will release the fix as version 6.1.0

mschwer commented 2 years ago

Hi @garbast , thanks for the update. Unfortunately it's still not working - even though with an other error:

Argument 1 passed to TYPO3\CMS\Extbase\Persistence\Generic\PersistenceManager::getObjectCountByQuery() must implement interface TYPO3\CMS\Extbase\Persistence\QueryInterface, null given, called in /var/www/html/public/typo3/sysext/extbase/Classes/Persistence/Generic/QueryResult.php on line 117

studio65digital commented 2 years ago

Hi @garbast! Same here.

garbast commented 2 years ago

In a2aaaa1b I changed how the empty result is provided. Please check if the error is still present in your installation.

studio65digital commented 2 years ago

Works wonderful now. Thanks a lot!

mschwer commented 2 years ago

Hi @garbast , the last error is now gone, now it's saying

(1/1) #1618235512 Exception Country may never be empty query: array ( )

Country is definitly set in the backend. Anything else I have to have in mind concerning "country"? example-data

mschwer commented 2 years ago

Any news or suggestions what could cause the error? @garbast

stephangrass commented 2 years ago

Hi, I get also the error Country may never be empty query: array ( ) and don't know why.

Any solution?

garbast commented 2 years ago

In which situation does this empty query occure? Did you submit a search before? It indicates that the geocoding query was send to the google api without a country. A search always needs to contain a country. Either from a selectbox in the search form, or via defaultContrains in TypoScript.

stephangrass commented 2 years ago

Hi, I will check it again soon. For now I have problems with the Import.

storefinder:import 1:/user_upload/locations.xlsx 203 1 {"A": "import_id", "B": "name", "C": "adress", "D": "City", "E": "zipcode", "F": "country", "G": "phone", "H": "email", "I": "url", "J": "icon"} "" ""

will get the error

"Too many arguments to "storefinder:import" command, expected arguments ..."

and don't know why ...

stephangrass commented 2 years ago

In which situation does this empty query occure? Did you submit a search before?

If the map is included before the search.

or via defaultContrains in TypoScript

And how to set the defaultContrains in TypoScript?

garbast commented 2 years ago

Please stick to the topic of ...must be an instance of TYPO3.....

garbast commented 2 years ago

I could not reproduce the array problem. If you could please recheck it and give me feedback. Then i would release the current state.

garbast commented 2 years ago

Closed due to lack of activity