New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reveal 'Open' Method throwing JS error #8482
Comments
I've opened the given URL, but I didn't find that error you have mentioned. |
I got similar errors while trying to dynamically create modals. As @abdullahsalem mentioned, one of the reasons why it happens is because the element is being added to the DOM after executing the I solved it by creating a Reveal instance, and then calling the
|
Pasting |
@tsquez It looks like this might be because of the way you are using |
@brettsmason - That seemed to work, now all I am getting is |
@tsquez Glad you got it sorted. That error is actually due to a bug in Reveal that has been fixed and is the dev branch. The patch 6.2.1 should be this week hopefully which includes the fix. |
Try to prevent rerendering of reveal element. if your reveal is a static value move it to more generic section. if it is not static, you can try to modify only reveal element's child. |
this issue is over 3 years old and was already resolved. Triggering notifications and answering very old issues which are already resolved is not so much helpful. |
I use Foundation for Sites mixed with WordPress in my theme WP-Forge. On my site I have a reveal window that pops up and allows the user to subscribe. You can see it here:
http://themeawesome.com/responsive-wordpress-theme/
Since I used the following from the Foundation Doc site (http://foundation.zurb.com/sites/docs/reveal.html):
jQuery('#element').foundation('open');
I get the following error:
Uncaught ReferenceError: We're sorry, 'open' is not an available method for this element.
on all the pages. Yes I replaced
#element
with the proper name. I even tried the following:$('#element').foundation('open');
Same thing. Any idea why this error is happening?
The text was updated successfully, but these errors were encountered: