The Client wants to show store locator details page using YEXT integration on the website. If a user clicks on any search result on the store locator listing page then it should get redirected to the store locator details page with the store details and a map pointing to that location.
There is a training with that same use case. It is on Pages track, module 4, sadly no one has been able to make it work because an error on the source code provided. Iâd be surprised if anyone from Yext responds to any post.
The issues you are facing has been faced while working with pages-starter-react-locations repository, or it is starter repository which has been mentioned in module 01 unit03
Iâm not sure what pages-starter-location is. Is this a new repo included in the trainings? I guess not.
We are just following the training that uses: GitHub - yext/pages-starter-react-locations (which was archived since Feb 26) and isnât working at all, as simple as that!
Do you guys have a new repo and you forgot to update on the trainings? If you follow the flow with âyext pages newâ we will end with a repo cloned from the archived one.
Hereâs is a previous post of mine with more details:
We recently updated the track and documentation to reflect a few changes that were the cause of the issues you were facing. If you start over, you should be able to proceed through the track without issue at this point.
âpages-starter-react-locationsâ is the starter repository we recommend using when going through the learning track (as Tosh stated). If you run yext pages new, this corresponds wth âLocations Starter (Basic)â - which is the first option youâll see returned by the CLI.
So to confirm, we need to go through this module âPages | Hitchhikersâ in order to create a store locator detail page on the client website. Is this understanding correct?
Thank you Luc for updating here. Yes @Ebrahim_Manasawala, you can proceed with the Page Track you have mentioned. With the updates performed recently. you shouldnât face any trouble now. However in case you find any issue, feel free to write here.
Hey Luc - thatâs what Iâve been doing âso many timesâ. Runing âyext pages newâ and selecting âLocations Starter (Basic)â but internally the CLI was picking an old repo that was archived and with errors on it.
With the latest changes you guys made I can see now my new repo cloned from the new âpages-starter-react-locationsâ and after run my build I donât see the error about âmodule not defineâ that was blocking the entire Pages TRACK.
It took a while to fix a huge blocker created by Yext that was impacting so many people. Itâs VERY frustrating the amount of hours that some of us spent on trying to figure it out what was happening, knowing that the solution was out of our hands. But at this point Iâm gonna say - âBig Thanksâ and move onâŚ