essfeed

The daily auto-update seems to work now,
I close this ticket, if someone have a problem with the auto-update please open a new ticket.

Hi,
In fact ESS is not so complex.
Events are indeed very sophisticated so ESS try to handle any possibilities.

The current plugin doesn’t require any configuration.
Once installed, each time you save your events from Events Manager a XML feed is placed in the meta description of your events pages.

This feed can also be seen at the bottom of each event page (with the ESS logo).

The feeds are also pushed to search engines to improve SEO.

The pseudo-CRON task depends on the client wordpress server configuration.
Wordpress didi its best to make it works on most configuration but it still a bit hard to make it works.. (buggy?).

It works on my side on my DEV environment, if anyone have a fix for non working platform I will merge it with a next release

The problem is solved in the current release.
It appended because in the settings, the Organizer URL wasn’t properly checked and authorized URL that didn’t started by either https:// https:// or ftp://
This control is required to be sure to have a valid URL.

In the future other customizable schema will be authorized (ex: myprotocol://) for mobile uses.

HTTP 5xx errors are servers errors, it means that you are accessing images that could not be loaded from one server to another.

Are you trying to access to this images in a dev environment with IPs or localhost?
Maybe you can share the URL of the image that cant be aggregated to test on my side?
Otherwise, can you give me more details to reproduce this error?

Thanks for your message.

The ESS feed contain the URLs of the tickets (if any) so it should redirect your users to the original ticket sellers websites.

Your issue occurred between two websites using WordPress Events Manager?

A new Events Manager ESS have been release some hours ago, could you tell me if it works now?

Otherwise, could you list the other plugins that you have installed and your WordPress version.

Thanks

We have received several times this requirement.
It’s the first one on the list major improvement for the next release.
Having a filtering tool to select the appropriate events to export (/import?) makes sens.

Thanks for your suggestion.

Thanks for the message,

This “Notice” message indicate that the constant EM_HYPECAL_VERSION was not evaluated as a string.
In PHP: EM_HYPECAL_VERSION is a constant and “EM_HYPECAL_VERSION” is a string that can represent a constant.

I have corrected that.

Hi @tech4life.

the error you’ve go at the line 418 of /home/srwoods/public_html/wp-content/plugins/events-manager-ess/inc/libs/ess/EventFeed.php:418

comes from that the url you have used for your feed doesn’t match the Regular Expression:
/^(http|https|ftp):\/\/([A-Z0-9][A-Z0-9_-]*(?:\.[A-Z0-9][A-Z0-9_-]*)+):?(\d+)?\/?/i

Which mean that it have to start by https://… or https://… or ftp://…

Hi Cameck,

We have published a new release 1.2.2 of the ESS plugin for Event Manager on WordPress, this new release should have fixed the issue you were mentioning.

Could you tell me if it works for you?

Hi Robert,
Thanks for your message.
The bug tracking is manage under GitHub: https://github.com/essfeed/wordpress-events-manager-ess/issues/7

This issue can be solved by removing the unnecessary controlling function self::unhtmlentities().
Before WordPress 4.3 the internal WordPress function esc_html() didn’t handled all circumstances (international char encoding in strict UTF-8 XML file) and that’s why it was necessary to reformat some chars according to their decimal bits.
Now the esc_html() function do the job so the self::unhtmlentities() duplicate the encoding…

I’m checking and correcting other bugs coming from the WP 4.3 update and the EventManager update.

If those of you who knows how to code can come back to me to see if removing the self::unhtmlentities() call at the line 64 of the file ../wp-contents/plugins/events-manager-ess/inc/views/ESS_Feed.php work fine (and if you see other bugs),
I will publish the new version in some hours.

Thanks

Hi guys,
yes you’re both right, Mea maxima culpa..

To prevent the <id> to be empty a security control set this value to a wrong value that can be duplicated even if the event URL is different.

I’ve rewrite the feedID assigner to generate it from the event page URL.

It should respect the ESS DTD no, please update the plugin to the 1.1 release.
Thanks for your comment.

And (Bill or other) don’t hesitate to tell us all the bugs you’ve noticed.

Hi guys,
could you send me the URL of the ESS feed you would like to subscribe?
Like have mentioned Bill, in Events Manager, the URL should end by ?em_ess=1
e.g. https://yourdomain.com/blog/?em_ess=1

We are working to be also able to syndicate to other king of feed (ical, google calendar, facebook events) even if they are far less precise then ESS.

For the moment you can only subscribe to ESS feeds.

Hi Bill,
we’ve set also this $timeout_sec to 20seconds.

This IP is an open ESS feed directory connected to search engines and events portals
Each time an event is saved with a “Publish” status it ping the IP server to tell to the search engines that an update is ready to be crawled.

The ESS directory server is located in the Google Infrastructure (GAE/Cloud Storage) but still there is many pings/sec so it can timeout sometimes…

Leave this call to the IP server, it will be faster with time.
The idea is to simultaneously broadcast your events to Eventbrite, Meetup, Facebook, Foursquare, Timeout, Google, Yahoo Upcoming and so on once you’ve clicked “save” from your WordPress website.