I don't have any WEM segmentation rules or anything set up. The module is just installed on the system. I am seeing this on most pages. It seems the JS is trying to do callbacks for WEM info but nothing is being returned. I would assume this JS should only try to fire if settings are in place. This is a pretty big problem, I'd say - but probably an easy fix in JS.
Screen Shot 2013-07-24 at 11.09.34 AM.png

CommentFileSizeAuthor
#1 Screen Shot 2013-07-24 at 11.12.11 AM.png6.82 KBsaltednut
Screen Shot 2013-07-24 at 11.09.34 AM.png44.12 KBsaltednut
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

saltednut’s picture

saltednut
she/her
Primary language English
Location Chicago
CreditAttribution: saltednut commented
Title: Anon JS function firing tons of forbidden AJAX callbacks » Anon JS function (Drupal.wem.queue.run) firing tons of forbidden AJAX callbacks
FileSize
Screen Shot 2013-07-24 at 11.12.11 AM.png6.82 KB

More info:
Screen Shot 2013-07-24 at 11.12.11 AM.png

donutdan4114’s picture

donutdan4114 CreditAttribution: donutdan4114 commented

So, this issue exists when the WEM Token changes upon reinstallation.
On a true fresh install, everything looks fine, but if you reinstall the wem module with a different random token set, users who previously went to the site (and had a wem user id set) will have a bad token set.

I believe I can fix this by just updating the token on the client side if the token errors.

saltednut’s picture

saltednut
she/her
Primary language English
Location Chicago
CreditAttribution: saltednut commented

Ok so this happens because we were storing the WEM token in a Feature. Makes sense. But people will try to do this perhaps. Is there a way to tell it to stop firing the callback if the token fails? This would at least prevent the problem from eating up system resources.

donutdan4114’s picture

donutdan4114 CreditAttribution: donutdan4114 commented

I'll have to dig in more.. The way it is setup now, if the user's wem/api request fails, 2 new requests should be fired to recreate the user ID and new token. I'll have to play with the Feature bit to test this out.