My Tab Page says this:
App temporarily unavailable
FBML Error (line 5): illegal tag "base" under "fb:tab-position"
CSS Error (line 151 char 214): Error in parsing value for property.: 'font-family' Declaration dropped.
CSS Error (line 152 char 448): Error in parsing value for property.: 'font-famil
It doesn't like loads of the CSS, it also says I can only have 2 CSS files as a limit. No problems with the limit, I'll change it and this is best practice for SEO anyway, BUT the rest of it...
What's the deal? And the first line? What's the deal?
Please make sure you've read over the Page tab and Canvas integration guide:
http://www.sourcecoast.com/jfbconnect/d … nvas-setup
Specifically, the note about migration settings that the "iFrame Page Tab" setting must be Enabled.
That should do it for you, but if not, let us know.
Yep, that did the trick. I could only find the iFrame part of the advanced, but it now has a new error
403 - K2_ALERTNOTAUTH
uglyeoin wrote:Yep, that did the trick. I could only find the iFrame part of the advanced, but it now has a new error
403 - K2_ALERTNOTAUTH
does this happen from within the canvas of on the site as well?
this issue seems to be strictly related to K2: http://getk2.org/community/New-to-K2-As … ERTNOTAUTH
I think I understand. If anyone else has this issue I'd love clarification.
My menu is set to "guest" which although perfect for me as when people log in, the usual sales spiel does not appear but some tailored spiel directed as current customers, and also their content that nobody else can see.
Either that or it is JUST a K2 issue, or a third guess... the dreaded SEF!!!
I can't follow the K2 solution posted because that involves making my article permissions "editable". Not something that the Facebook community really needs now is it!!
the easiest of them to test is the SEF.
temporarily disable it, and see if this is the cause for the issue.
Let us know if that helped.
uglyeoin wrote:With SEF turned off there is a change. It becomes a 404 page not found instead of a 403 - K2_ALERTNOTAUTH
Logically speaking, the fact that there is a page not found, is the cause K2 is not letting you access it.
try solving the 404 issue, it'll probably solve the 403...