My Facebook Access Token stopped working


EME helps you to achieve GDPR compliance. While some things (like alerting your visitors of the fact that you use cookies and also inform them about your privacy policy) remains your own responsibility, you can put the eme_gdpr shortcode on a regular wordpress page (with all the explaining you want to do) so people can easily and safely request their personal info stored in EME. The link generated by using #_GDPR_URL in the email the form sends out (the form is created by this shortcode) is only valid for X hours (the lifetime of a wordpress nounce, typical 24 hours).
The content of the generated email can be changed in the EME GDPR preferences.

So in fact it is a 2-step procedure:
1) create a wordpress page and put [eme_gdpr] in it. Then let people know of this page (privacy policy, mail, …).
2) after the user enters his email and submits the form, he/she gets an email with a link towards the personal data stored.


To allow people to change some of their personal data, you can use the shortcode [eme_change_personal_info]


Will show a list of all categories. Accepts the following arguments:

  • eventful: if set to true, only locations with events planned will be shown. Default: false.
  • scope: see the explanation for [eme_events]. You need to set eventful to true for this to have any effect.
  • event_id: only show categories for a specific event id.
  • template_id, template_id_header andtemplate_id_footer use predefined format templates for the category listing, header and/or footer. See See the doc concerning placeholders for more info on which placeholders you can use in these format templates for categories.

[eme_categories template_id=3 template_id_header=7 template_id_footer=9]
[eme_categories template_id=3 eventful=true]

How to create a Facebook App ID

In this tutorial I’m going to walk you through how to create a Facebook App ID to be used with Events Made Easy Sync Facebook Events

A Facebook App ID is required to use the Events Made Easy Sync Facebook Events add-on…

I. Register as a Developer

You need to have your personal Facebook profile registered as a developer before you can create an App and App ID. If you already have a Facebook account and are registered as a developer you can skip these steps and go to the “Create an App” steps.

1. First navigate to and login with your personal Facebook account if you have one. If you don’t have one, you’ll need to create one. Note that if you are simply using Facebook to manage pages, these instructions will not work – you need a personal Facebook account before you can proceed to step 2.
2. Next go to and click on the green Register as a Developer button in the upper right. You will likely have to verify your Facebook account via phone, so please also do that if you haven’t already.
3. Once you’ve verified your account, clicking the Register as a Developer button will display a popup similar to this:

4. Check the Accept Terms box and click Continue.
5. Either skip or complete all the information on the next screen as best you can, the answers are not too important.
6. Click Done on the next screen. You are now a Facebook Developer!

II. Create an App

1. Browse back to
2. In the upper right corner click on the green Add a New App button:

Screenshot - 10182014 - 12:36:05 AM
3. In the popup that appears, give your App a name (I’m using “E-Dynamics”) and click continue (leave the other options empty).
4. Next, complete the Captcha verification and click Continue.
5. You app has been created

III. App domain

For your facebook app to actually work on your site, the “app domains” should list the domain of your server. For example, for the site I have the app domain set to “”

IV. Plug In Your App ID & Secret

Now that you’ve created your App (feel free to create more), enter your App ID and Secret in the Events Made Easy Sync Facebook Events settings tab in WordPress:

Screenshot - 10182014 - 12:39:39 AM

Screenshot - 10182014 - 12:40:35 AM

Legacy syntax and deprecated placeholders


In the past, there was an inconsistent behaviour when placeholders needed options:

and others

This resulted also in some unwanted behaviour where square brackets of wordpress shortcodes were matched as possible options for placeholders. This has now been made consistent and the syntax for #_ATT{…}{…} is being taken as a reference.

Legacy placeholder syntax

The following 4 event placeholders are now deemed “legacy”, which means you should avoid using them and also the usage is by default “off”. The new syntax is described next to it each placeholder. The only placeholders here are event placeholders using square brackets:

  • #_EVENTPAGEURL[xx] becomes #_EVENTPAGEURL{xx}
  • #_EVENTCATEGORIES[..][..] becomes #_EVENTCATEGORIES{..}{..}
  • #_EVENTIMAGETHUMB[MyCustomSize] becomes #_EVENTIMAGETHUMB{MyCustomSize}

The old syntax can be restored by checking the new option “Re-enable legacy placeholder behaviour” in the EME general settings tab, but I encourage everyone to switch to the new notation if/when possible. If you enable the old syntax, the new syntax is not possible. This option does not influence in any way the new syntax for the deprecated placeholders mentioned next.

Deprecated placeholders

Some placeholders are now deemed “deprecated”, which means you should avoid using them but you’re still allowed to use them so as to give you the time needed to switch to the new syntax.

For event placeholders, the following changes:

  • #_PRICExx or #_EVENTPRICExx becomes #_PRICE{xx} or #_EVENTPRICE{xx}

For RSVP placeholders, the following change:

  • #_RESPSPACESxx becomes #_RESPSPACES{xx}
  • #_TOTALPRICExx becomes #_TOTALPRICE{xx}
  • #_FIELDxx becomes #_FIELD{xx}
  • #_FIELDNAMExx becomes #_FIELDNAME{xx}

For booking form placeholders, the following change:

  • #_SEATSxx becomes #_SEATS{xx}
  • #_CAPTCHAHTML[..] becomes #_CAPTCHAHTML{..}
  • #_SUBMIT[..] becomes #_SUBMIT{..}

You can still use them, but a warning will be shown until you deactivate the new option “Allow deprecated placeholders” in the EME general settings tab, but I encourage everyone to switch to the new notation if/when possible.
Remark: the newer placeholder notation for the deprecated placeholders is not influenced by the new option “Re-enable legacy placeholder behaviour”, so whether or not you activate that option, the new syntax for these placeholders will always work.