lassoteam

Hey there! Thanks so much for reaching out about this.

We removed the click counter from the revamped version of Lasso Lite and added it as feature called Performance. Performance is included with Lasso Pro plans. This reporting includes detailed page and link analytics, so you can see exactly where those clicks are coming from.

However, we do still offer the standard click counts from Simple URLs if you’d prefer. If you’d like to keep those, you can navigate to Lasso Lite > Settings > General. Then, toggle off the ‘Enable New UI’ button at the bottom of the lefthand column and hit ‘Save Changes’ at the bottom of the page. That’ll put you back on the Simple URLs layout you’re used to.

Best of luck, and please let us know if we can clarify anything!

@wordpresssites Hi, Brad. Is this for the notice: Earn 3-5x Higher Amazon Commissions for Free!

If so, there should be an ‘x’ icon on the right side that will permanently dismiss that banner. If that’s not showing, or if it’s a different notice, can you please send over a screenshot?

Either way, I’ll get it taken care of. Thanks!

Hello again!

We’ve just released an update, v124, where we fixed the issue of the banner not being dismissable.

Thanks for using Simple URLs!

Hey there, thank you so much for the initial report and for following up.

We have a priority list of issues and improvements we’re working on, and this is definitely on the list.

I understand it’s more than annoying, and the team is working on a fix for you.

I’ll report back here as soon as that fix is officially live!

Hey all! We’re happy to announce this is officially fixed in v123. This issue will be resolved once you update. If the issue persists, please let us know!

Hi there, @rssddave!

Lasso Lite 121 just released today, with a security fix patching the CSRF vulnerability.

We deeply appreciate your patience and trust while the devs were resolving this issue.

Thank you, and feel free to continue to reach out with any feedback/questions you may have!

• This reply was modified 1 year, 1 month ago by lassoteam.

Hey @spabav,
Just wanted to say I hear you, and I hear your frustrations. Admittedly, while we do think what we are offering here at LassoLite is awesome as is, we’re still growing and learning every day.

We’re striving to make this a killer free tool for people that are just starting out, so we take any feedback seriously.

Could we do something to make this better?

Hey there, @srikat!

Thank you so much for working with us on this matter, and for your patience while we got it resolved.

Pleased to update that the devs have improved the Shortcode rendering content to prevent the XSS, and your issue should be resolved!

Feel free to reach out with any other comments or questions on this matter, or any matter ??

Hi again @spabav ??
Thanks for reaching out, and for hanging by for a reply.

To clarify: in the new version v118, the permissions you are looking for are for paid users only, so not a bug but instead just not possible!

If you are not looking to upgrade your subscription, totally fine! Completely your decision, and if version 117 suits your needs then feel free to stick with that ??

Hi again @pinkivy,

Thank you so much for your patience and understanding while the ticket was resolved!

Pleased to officially report everything should be good to go regarding those deprecated notices.

Thanks again, we appreciate you ??

Hello again, @spabav!

We again wanted to thank you for bringing this to our attention, and also thank you for your patience while we’ve been working with the devs. We are so happy to have you as a part of the Lasso team!

Here to report that for the time being, custom user permissions are an exclusive feature of Lasso Pro.

However if you should need any other assistance or have any other feedback, we are absolutely here to help.

We thank you for your continued understanding, and appreciate you deeply!

Ah, we’d be happy to take a look at that, too! Could you please send a screenshot of this to [email protected]?

I’ll add that to the vulnerabilities ticket, so we can clear that up ASAP as well.

@rsddave Indeed! We are looking into this vulnerability and will have a fix ready to go in v119.

I’ll reply back here as soon as that’s ready.

@spabav Thank you for the detailed write-up! That’s far from what we want to happen, and I’ll make sure that gets taken care of it.

I’ve opened a ticket with our devs, and we’ll investigate this issue with v118.

I’m glad to hear that reverting to v117 did the trick and will send a message as soon as v119 is released with your fix.

Thanks again!

@pinkivy Thank you for sharing this.

Our devs are on the case. I’ve created a ticket in our internal system for this, and I’ll reply back here as soon as it’s resolved.

If anything else comes up in the meantime, please let me know!