The way that we post about our monthly events here at SEMpdx, is that we create blog posts, we categorize them so they’ll appear in the menus and sliders where we want them to, and for the registration, we use a third party called Wild Apricot.
Before that we used Eventbrite, and now we’re starting to use Bizzbo, but one thing they all have in common is that we embed a widget – an iframe – in order to accept registration on our site.
The user experience while registering through the Wild Apricot iframe was less than stellar, so a couple of years ago, we came up with a simple solution, which was to redirect the page right to the Wild Apricot Event page. Users click to the upcoming event post, and get where they need to go. Problem solved – we thought – for about two years.
All of a sudden, in our Slack channel today, (that SEMpdx members can join) members were reporting that they couldnt view the details of Tuesdays upcoming event using Google chrome. Instead of being redirected, They were getting “Wrong Document Context” as the error message, but on a phone you can clearly see why.
Wrong Document Context
If you Google “Wrong Document Context” you get nothing very relevant as to why this is happening… seems like this default error message makes no sense. Why not say “The Redirected URL is blocked”?
More imprtant though, is that I want to know WHY this is happening. Is the mere fact that we’re doing a redirect somehow suspicious? There’s nothing in Google Search console that we’ve done anything nefarious. Why is Google stopping us?
Did Wild Apricot get flagged as doing something wrong? I don’t think so, or again, shouldn’t Google Search Console tell me something useful here?
Reading this article did explain that the user could decide to trust the redirect but aside from suggesting that their PC’s had malware, it wasn’t much help.
Try This For Youself in Chrome & Firefox
After a current event is done, we remove the redirects, but I put one back for May, so you can try it for yourself.
Here is the event URL: https://www.sempdx.org/sempdx-events/may-2019-members-appreciation-digital-marketing-consultations/
That URL should redirect you here: https://sempdx.wildapricot.org/event-3334388
In Firefox it does, but in Chrome it does not.
This is what’s in .htaccess:
redirect 302 /sempdx-events/current-events/may-2019-members-appreciation-digital-marketing-consultations/ https://sempdx.wildapricot.org/event-3334388
Granted, redirecting a page on your site is a rare use, but it’s weird. Got any ideas?
Scott Hendison is the CEO of Search Commander, Inc. and a recovering affiliate marketer. He is also one of the founding board members of SEMpdx. Find out more about him at his website, SearchCommander.com.
Hello Scott!
I am running into the same issue when I try to incorporate an iframe into my website designed using wix, I wanted to include a snippet of my wild apricot events list into the website but it is giving me the “wrong document context!” error, do you mind sharing how you were able to resolve this issue? Thank you!
Adam
I’m sorry, but we were unable to resolve the issue, and instead just stopped using iframes from Wild Apricot. Very strange…
Hi there …
I have the same problem when i use SNIPLY to link to a site or eventsite of WILD APRICO.
There is allready a solution for this issue?
Hi Scott!
I came across this too – seems to be a cookie issue. You can solve this using the following script:
XXX refers to the end of the link for the page you are looking to direct to e.g. events or sys/profile etc
Thanks!
Here is the code – just switch out the brackets and add in your info:
(iframe width=’100%’ height=’800px’ frameborder=’no’ src=’https://YOURSUBDOMAIN.wildapricot.org/widget/XXX’ onload=’tryToEnableWACookies(“https://YOURSUBDOMAIN.wildapricot.org”);’ )(/iframe)(script type=”text/javascript” language=”javascript” src=”https://YOURSUBDOMAIN.wildapricot.org/Common/EnableCookies.js”)(/script)
Keep these brackets though – I should have used [ ] for the – oh well:
onload=’tryToEnableWACookies(“https://YOURSUBDOMAIN.wildapricot.org”)
Great news! Found this series of posts yesterday while trying to solve our “Wrong document context” error and worked with WildApricot to fix this issue on our site. Hopefully it helps you guys, too.
We learned that the problem was with the link I’d used for an event… while it worked alone in a browser, in an iframe, it would generate that annoying error OR a redirect to the WA-hosted page.
Our original code was [iframe src=”https://stairways.wildapricot.org/event-3934068/” width=”100%” height=”1000″ name=”register” scrolling=”yes”]
But the tech support guy pointed out that the link was missing the word WIDGET and had me use this url instead: https://stairways.wildapricot.org/widget/event-3934068/
Worked immediately! Went back and checked the other iframe links on the site and found that others had the widget already, so this was just a simple mistake in grabbing the wrong embed link.
ALSO NOTE:
For those having trouble using iframes, they are not secure, so some https/http links cannot be used with them if the site has a different security level.
The workaround – at least on WordPress – is an iframe plugin that lets you exchange the usual wrapper for a braces [ ]. It’s a simple swap that made a HUGE difference for us (Divi was actually erasing our old iframe code every couple of days before this fix).
Also running into this issue when trying to Redirect to a calendar hosted on Wild Apricot. I’m putting together slides for a digital sign and thought it would be nice to include upcoming events. I think we have another sign that solves this problem. I’ll try to figure out how they fixed it and post here if I find a solution.