|
Marcia Chadly
|
September 22, 2015 at 10:52 pm
The featured image on our registration pages is not being used when the page is posted in Facebook. I checked a page with the Facebook Open Graph Object Debugger and get the error: More Than One OG URL Specified. Object at URL ‘http://creativelifecenter.org/event-registration/?ee=138’ of type ‘website’ is invalid because it specifies multiple ‘og:url’ values: http://creativelifecenter.org/event-registration/?ee=138, http://creativelifecenter.org/event-registration/.
I searched the forums and found a similar thread: https://eventespresso.com/topic/social-media-share-not-working-correctly-for-me/ The problem there was a setting in Yoast SEO. I’m using a different SEO plugin – All In One SEO. I don’t see the same setting. Is there a known problmen with All in One SEO and EE3 that causes this issue?
Thank You, Marcia
|
|
Josh
|
September 23, 2015 at 3:55 pm
Hi Marcia,
Does the issue go away if you deactivate the EE3 social sharing add-on? If so, if so, I can look into sharing some code that will disable the social sharing add-ons og feature so that All in One SEO will be the only plugin adding the OG tags.
|
|
Marcia Chadly
|
September 24, 2015 at 11:23 am
Hi Josh,
When I deactivate the EE3 Social Media plugin, the error goes away and these warnings appear.
Extraneous Property Objects of this type do not allow properties named ‘article:published_time’.
Extraneous Property Objects of this type do not allow properties named ‘article:modified_time’.
og:image could not be downloaded or is too small og:image was not defined, could not be downloaded or was not big enough. Please define a chosen image using the og:image metatag, and use an image that’s at least 200x200px and is accessible from Faceboo… See More
Parser Mismatched Metadata The parser’s result for this metadata did not match the input metadata. Likely, this was caused by the data being ordered in an unexpected way, multiple values being given for a property only expecting a single value, or property values for a given property being mismatched. Here are the input properties that were not seen in the parsed result: ‘og:title, og:description, og:image:url, og:type, og:site_name, article:published_time, article:modified_time, og:locale:locale’
BTW – I didn’t get any email notification that you had responded to my support request. (Not in spam either.) I did check the Notify me by email box, so not sure why I didn’t get the email.
Thank you,
Marcia
|
|
Josh
|
September 24, 2015 at 1:13 pm
Hi Marcia,
It turns out that Event Espresso 3 doesn’t add any OG meta tags (they do get added by the social icons add-on) Any errors generated by OG tags might be best addressed by the other plugin and/or following the suggestions from the error. ie, if the image is smaller than 200x200px you can use an image that’s at least 200x200px in dimensions.
|
|
Marcia Chadly
|
September 25, 2015 at 12:18 pm
Hi Josh,
So are there two levels of issues? One with the social icons add-on that causes the error. And then another underneath that will need to be addressed once the social icons add-on issue is resolved?
Do I need the code to disable the social sharing add-ons og feature?
Thank you, Marcia
|
|
Marcia Chadly
|
September 25, 2015 at 12:21 pm
This info from the FB tool is interesting too. This was from scraping a URL with the social media icons add-on deactivated.
To find the object, these are the redirects we had to follow
original http://creativelifecenter.org/event-registration/?ee=161
og:url http://creativelifecenter.org/event-registration/
The following will be treated as a redirect by the crawler:
A HTTP redirect
A <link rel=”canonical” href=”..” /> tag
A <meta property=”og:url” content=”..” /> tag
The final URL, which we tried to extract metadata from is highlighted in bold
|
|
Marcia Chadly
|
September 25, 2015 at 12:26 pm
I just checked the size of images on http://creativelifecenter.org/event-registration/?ee=161 There is an image that is 275 × 206 – so the og:image warning with the social media ad on is not that there isn’t an image large enough. Based on my last message, I’m wondering if http://creativelifecenter.org/event-registration/ is being used for the scrape rather than the page with the image?
|
|
Josh
|
September 25, 2015 at 6:00 pm
It likely is scraping event-registration instead of /event-registration/?ee=161. You could work around that by using the “Create a Post” feature, so that your Facebook links all point to the blog post for the event instead of the registration form page only. You can use the “Create a Post” feature by scrolling to the bottom of the event editor page, then set “Add/Update post for this event?” to Yes, “Post Type” set to Post.
|
|
Marcia Chadly
|
September 28, 2015 at 11:22 am
Hi Josh,
I do have related blog posts for seo but that doesn’t help people who are on the registration page and want to share it. Also sharing the blog posts means people have to do an extra click to register. Is there a way to fix the scraping? I’m assuming switching to EE4 fixes this? I wasn’t ready to take that on yet, but might have to?
Marcia
|
|
Lorenzo Orlando Caum
|
September 28, 2015 at 11:43 am
Hi Marcia,
You won’t experience this issue in Event Espresso 4 as the events are custom post types which means they can easily be shared on various social networks.
—
Lorenzo
|
|
Marcia Chadly
|
September 28, 2015 at 12:13 pm
Is there any way around this issue in EE3?
|
|
Lorenzo Orlando Caum
|
September 28, 2015 at 12:25 pm
Hi Marcia, the other suggestion is to use the post option that Josh shared.
—
Lorenzo
|
|
Marcia Chadly
|
September 28, 2015 at 12:31 pm
Bummer, but good to understand. The post option does do what we need for social media sharing. Thank you both for your time.
Marcia
|
