The new feature issue has been fixed and turned out to be a problem that's been in the system for almost a year. However, it is a very rare scenario and has never been reported by users.

GEEK-SPEAK
In any case, the scenario is now accounted for on all requests and won't be an issue from now on. This may have affected some requests, only when using javascript/AJAX/etc WITH lock to account enabled AND the referrer was setup properly, that the script may not have properly reported the primary referrer. In that case, we had to substitute an alternate referrer, which we already made available, but I did not realize was required in some cases.

One important note that I should make:

If you are using a 3rd-party plugin (i.e. WordPress, Drupal, JV-Extensions, etc), then you won't need to worry about the changes. We are working with (or will be soon) all 3rd-party integrators to update their code. They will provide an easy upgrade that will handle it all for you.

p.s. And I'm very excited because we are finally in a position to give back more to the community (mostly due to all the recent and upcoming changes). So we will be making a big announcement in the coming weeks. Stay tuned!

I am about to take the system down for a few minutes (3:00am ET) to make some database updates. These changes are needed to pave the way for "Bandwidth PLUS" and should not affect any current services. I post an update once everything is tested and confirmed working.

Alright. It looks like those changes went well.

I have launched the next part of Phase 1 for this project.

That is the new STW Preview Verification code for non-paying users. It is not yet locked down but that code will be provided within the system now. It looks like that code is working well, but we may tweak it once we receive feedback from users.