mb

Great info about the php option.

ok, paolo, thanks!

Just updated yesterday!

The widget works great now! And really no pressure on the Google daily limits.

Thank you, Stiofan!

Thanks, Guust!

How can I further explore the error to eliminate the reason of its appearance?

mb

Hi Stiofan and support,

I didn’t receive any further comments on the logic. Anyway, I started to play different scenarios and tests. Here are some comments:

1. Looking for a keywrod ‘kinder’ (kids) in Events

Result URL:
http://iallgaeu.de/?geodir_search=1&etype=upcoming&stype=gd_event&s=kinder&snear&event_start&event_end&sgeo_lat&sgeo_lon

Presuming that the user is looking for children events in general.

Regarding the general usage, I would presume that the logic is Ok, but not great. If the user chooses Events to be arranged by Coming Up, the general expectation is to be arranged by following coming up date, not just by keyword strength. The user orientates thus, what is really coming first and what is coming next regarding events for children.

The best as a result from this point of view would be to show the keywords relevant events but arranged by coming up date (with the closest dates coming first).

2. When there are recurring events coming in the search results

Looking for local weekly markets in general, not related to 1 place. User keyword ‘wochenmarkt’ (weekly market)

Result URL:
http://iallgaeu.de/?geodir_search=1&stype=gd_event&s=wochenmarkt&snear=&event_start=&event_end=&sgeo_lat=&sgeo_lon=

The user intends to find different weekly markets. If he wants to see the dates of the weekly markets in a special city/village or around this village, he can use the location filter to specify this. If he doesn’t use the location filter, means that he is interested in more general overview and information.

But the result at the moment doesn’t match such expectation. Because it returns regarding keyword match only. The logic can rank always 1 event as the strongest keyword match, then the next and the next.

This is good when the event is not recurring because it will show 1 listing and then more will follow up on the first page results.

But When the result is recurring event, the logic lists all instances of the same event (because the same keywords are attached to all the recurrences !! and no other event can outrank the first match !!) and finally after 2-3 pages with the ‘same’ result it lists another event.

Here the problem is that the result doesn’t match the search scenario and the user expectations – the user is looking for multiple options, not how often the same events repeats.

From both scenarios above, I think that arrangement regarding the event data has to be taken under consideration.

It will greatly improve the search results in Scenario 2. Otherwise, all recurring events have to be entered as single and separate events to somehow control the keyword search results, thus making the helpful recurring feature useless.

Solution 1: If the recurring events are arranged by coming date, then the search result make sense.

Solution 2: Or for recurring events when using a keyword search to show ONLY the closest by date instance of each recurring even.

May be, Solution 2 is easier to implement (otherwise I suspect that two loops are requested – you can comment better on this Stiofan).
Anyway, if the user doesn’t see all the dates of a recurring event in the results is not a panic, because once he clicks on the Details page, he will see all dates for this event.

I believe the event diversity is more important then checking all dates when the event happens. More often people are interested to see options and possibilities. And how often and when recurring, they can see on the details page of the event.
Does it make sense?

Looking forward to hearing your comments.

Hi Stiofan,

Thanks for your message.

Difficult for me to debate when I am not sure what exactly the logic is.

May you explain how did you build the logic, please?

May be it is a great logic for everything with keyword search except the recurring events. May be just for the recurring events can be a bit different.

Looking forward of hearing the logic line and I am more than ready to think of scenarios if it can be improved and write down only the good suggestions 🙂

Cheers.

@magnaromagn
You should check with CloudWays then.

By the way are you happy with CloudWays? I tried it but I found DigitalOcean with ServerPilot far easier and user friendly.

Good luck with solving the issue!

Hi Stiofan and support,

any updates on my last message?

Also, when it is expected the changes to take place and we can make an update?

Thanks.