Not a bug "Please post a valid message" error when skimlinks installed on anything but Default theme

I was trying to avoid using Viglinks. xenForo should be able to post a message even if a 3rd party has another instance of jquery included in their javascript. Seems a bit ridiculous for it to kill such an important part of the user experience.
 
Okey dokey, I'll post it up for anyone who has both revenue avenues available to them. :thumbsup:

Simply replace the asterisks with your own Skimlinks and VigLink keys.

Code:
<xen:if is="!{$visitor.user_id}">
<script type="text/javascript" src="http://s.skimresources.com/js/************.skimlinks.js"></script>
</xen:if>
<script type="text/javascript">
  var vglnk = { api_url: '//api.viglink.com/api',
                key: '********************************' };

  (function(d, t) {
    var s = d.createElement(t); s.type = 'text/javascript'; s.async = true;
    s.src = ('https:' == document.location.protocol ? vglnk.api_url :
             '//cdn.viglink.com/api') + '/vglnk.js';
    var r = d.getElementsByTagName(t)[0]; r.parentNode.insertBefore(s, r);
  }(document, 'script'));
</script>
 
I've just re-opened my ticket with Skimlinks about this, they looked into it before but couldn't see anything wrong, if it's two instances of jquery maybe this can be sorted!
 
Cool - hopefully they can get to the bottom of it this time :)
Peer pressure! I've a ticket opened for a month on the issue now, I keep dipping in with any useful info that I find on here but the more that speak up about it the better. Solving this issue surely has to be good for both Xenforo and Skimlinks :cool:
 
Skimlinks confirmed my ticket yesterday and advised they have added this to be investigated in the next sprint, I've asked if there's an ETA, hopefully I'll get an update on that soon, will post here when I do :)

Dave.
 
Skimlinks confirmed my ticket yesterday and advised they have added this to be investigated in the next sprint, I've asked if there's an ETA, hopefully I'll get an update on that soon, will post here when I do :)

Dave.
I was told the same thing. I've a ticket in on this issue with SL since 26th Feb, two months on a fairly critical issue.

Posted a link to this thread again in my ticket!
 
Just heard back:

Hi Brent,

A fix for this will hopefully be released this afternoon, at the moment it will be on a domain level but this may change.
 
Okey dokey, I'll post it up for anyone who has both revenue avenues available to them. (y)

Simply replace the asterisks with your own Skimlinks and VigLink keys.

Code:
<xen:if is="!{$visitor.user_id}">
<script type="text/javascript" src="http://s.skimresources.com/js/************.skimlinks.js"></script>
</xen:if>
<script type="text/javascript">
  var vglnk = { api_url: '//api.viglink.com/api',
                key: '********************************' };
 
  (function(d, t) {
    var s = d.createElement(t); s.type = 'text/javascript'; s.async = true;
    s.src = ('https:' == document.location.protocol ? vglnk.api_url :
            '//cdn.viglink.com/api') + '/vglnk.js';
    var r = d.getElementsByTagName(t)[0]; r.parentNode.insertBefore(s, r);
  }(document, 'script'));
</script>
This should be an "else" conditional, otherwise guests are getting both codes, which won't work as they'll conflict.

Try:
Code:
<xen:if is="!{$visitor.user_id}">
<script type="text/javascript" src="http://s.skimresources.com/js/************.skimlinks.js"></script>
<xen:else />
<script type="text/javascript">
  var vglnk = { api_url: '//api.viglink.com/api',
                key: '********************************' };
 
  (function(d, t) {
    var s = d.createElement(t); s.type = 'text/javascript'; s.async = true;
    s.src = ('https:' == document.location.protocol ? vglnk.api_url :
            '//cdn.viglink.com/api') + '/vglnk.js';
    var r = d.getElementsByTagName(t)[0]; r.parentNode.insertBefore(s, r);
  }(document, 'script'));
</script>
</xen:if>
 
Good news :)

Skimlinks said:
Update at last! Thanks for your patience while we were looking into this.
We just finished the fix for this and pushed this update to the JavaScript on your account earlier today.
This will resolve all of this instances of this occurring.
The error was related to the jquery being called twice and turned out to be very specific which is why it was tricky to replicate.
So, this is now resolved, let me know if you have any questions about any of this. I'll be updating other XenForo users and then the forum about this later.
 
This should be an "else" conditional, otherwise guests are getting both codes, which won't work as they'll conflict.
Yes that's true and thanks for the heads up. The "last" script called takes priority.
I'd since swapped mine over :oops:

Anyways...

Got got the same! :)

I'll get the users to test now!
The problem affects IE7 and IE9 AFAIK. Not too sure if this extends to Opera as well :unsure:
 
Top Bottom