Hi, thanks for your hard work on this module. I'm experiencing long loads and most often simply a load sign (on mac a watch load sign) after having closed the first popup. I've posted the javascript errors below. Obviously this has something to do with Facebook Style Statuses. I have a view setup displaying Facebook Style Statuses with a delete button. So when I click on the popup enabled delete link the popup loads fine but then if I select close or cancel (not confirm) I get a hanging load sign (watch) and next time I click on a popup I get a long load time.
Now my question, considering the output (below), is this an issue I should bring up with the maintainer of Facebook-Style Status?
Sometimes I get this:
Drupal.settings.facebook_status is undefined
anonymous()facebook...atus.js?N (line 6)
anonymous()drupal.js?N (line 42)
anonymous()jquery.js?N (line 13)
anonymous()drupal.js?N (line 41)
anonymous()popups.js?N (line 920)
anonymous()popups.js?N (line 866)
success()jquery.js?N (line 13)
anonymous()jquery.js?N (line 13)
[Break on this error] fbss_maxlen = Drupal.settings.facebook_status.maxlength;\nAnd sometimes I get this:
Drupal.settings.facebook_status is undefined
anonymous(Object length=1 0=div.popups-body prevObject=Object)facebook...atus.js?N (line 6)
anonymous()drupal.js?N (line 42)
anonymous(Object, function(), Object name=c)jquery.j...val/seq/1 (line 1)
anonymous(Object length=1 0=div.popups-body prevObject=Object)drupal.js?N (line 41)
anonymous("statuses/712/delete", "Delete status", "<form action="/londonfuse2/statuses/712/delete?&destination=user" accept-charset="UTF-8" method="post" id="-facebook-status-delete">\n<div><p>Are you sure you want to permanently delete the status <em>Dusty Peas book launch tonight at Forest City Gallery, 9pm. Expect radical music, art and some good food.</em>?</p><input type="submit" name="op" id="edit-confirm" value="Confirm" class="form-submit" />\n<input type="submit" name="op" id="edit-back" value="Cancel" class="form-submit" />\n<input type="hidden" name="form_build_id" id="form-1f3e66205fbec45a371d134bbaf27140" value="form-1f3e66205fbec45a371d134bbaf27140" />\n<input type="hidden" name="form_token" id="edit--facebook-status-delete-form-token" value="4b4661d80fb30b142190cfe92d8c999b" />\n<input type="hidden" name="form_id" id="edit--facebook-status-delete" value="_facebook_status_delete" />\n\n</div></form>\n<div><a href="/londonfuse2/statuses/712/delete?formfilter_id=_facebook_status_delete" class="active">Filter this form</a></div>", a.popups-processed delete?des...ion=user/1, Object updateMethod=reload updateSource=initial, Object name=parent)popups.js?N (line 920)
anonymous(Object title=Delete status path=statuses/712/delete)popups.js?N (line 866)
success()jquery.j...val/seq/1 (line 1)
anonymous(20)jquery.j...val/seq/1 (line 1)
[Break on this error] fbss_maxlen = Drupal.settings.facebook_status.maxlength;\n facebook...atus.js?N (line 6)
Comments
Comment #1
AtomicStudios commentedI'm experiencing the same issue... The JS settings aren't getting set on the popup... Did you figure out a solution to this?
Comment #2
pribeh commentedNo luck so far GrAfiXoNeR. I wish I could figure this one out. Some sort of response/guidance from the maintainers of this module would be greatly appreciated since I'm still waiting on this before I can implement using this module a priority site. This is a superb module.
Comment #3
adam_c commentedsame problem
Comment #4
icecreamyou commentedHi, I'm the maintainer of Facebook-style Statuses.
This issue is not the fault of FBSS, unless the API in the dev build is different than that in 2.x-alpha5 and the documentation. This is the total sum of everything FBSS does to integrate with Popups API (facebook_status.module lines 1989-1997):
Also, I can't reproduce this using Popups API 2.0-alpha5.
Comment #5
pribeh commentedThanks for responding to this IceCreamYou. I've actually done some more research just now, plus reinstalled the latest build of popups 2-beta5, and realized that this is probably a duplicate of 425954 (http://drupal.org/node/425954). I only seem to experience this in Safari - which is oddly my primary browser for testing.
Comment #6
icecreamyou commentedAh, yes. And I only test on Safari if it's a browser-related feature I developed myself. Sounds like this can be marked as duplicate but I'll let someone else confirm since I haven't actually tested pribeh's hypothesis.