I use a self developed module on my page that checks the first upcoming events location against google for lat and lon so it can be used the get the correct map from Windy. I discovered the columns geolon and geolat in the db.. reading https://www.jevents.net/discussions/geolon-geolat it is stated to be a remnant from the past.. I like this remnant as it may allow me to store the lat lon data so I don't have to call google each page visit.
Next as I import the calendar items from remote .ics, they are all stored each scheduled cron to get the .ics calendar.
(Awsesome and works like a charm. Thanks again for the support on this)
Now I wanted to create my own plugin or maybe use the one from Nordmograph to store the coordinates.. but as I discovered each entry is (re)saved. jevents stores 0 (zero) again in both geolat and geolon.
Google not always properly returning results causes it to store true data ánd zeroes at random...
Reading this
https://www.nordmograph.com/extensions/index.php?option=com_kunena&view=topic&catid=99&id=16289&Itemid=40
Made me comment out the following lines: 32, 33, 174 and 175 in IcalEventDetail.php.
With these changes it works as expected.... but... maybe I overlooked something?
Is there a better way to avoid jevents resetting to zeroes? Or can it be taken into a next version that it doesn't save zeroes so the columns are open for other developers?
Tx
Next as I import the calendar items from remote .ics, they are all stored each scheduled cron to get the .ics calendar.
(Awsesome and works like a charm. Thanks again for the support on this)
Now I wanted to create my own plugin or maybe use the one from Nordmograph to store the coordinates.. but as I discovered each entry is (re)saved. jevents stores 0 (zero) again in both geolat and geolon.
Google not always properly returning results causes it to store true data ánd zeroes at random...
Reading this
https://www.nordmograph.com/extensions/index.php?option=com_kunena&view=topic&catid=99&id=16289&Itemid=40
Made me comment out the following lines: 32, 33, 174 and 175 in IcalEventDetail.php.
With these changes it works as expected.... but... maybe I overlooked something?
Is there a better way to avoid jevents resetting to zeroes? Or can it be taken into a next version that it doesn't save zeroes so the columns are open for other developers?
Tx