Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.


  • Content Count

  • Joined

  • Last visited

  • Days Won


lesley last won the day on April 1

lesley had the most liked content!

Community Reputation

679 Excellent


About lesley

  • Rank
    Lesley Paone


Recent Profile Visitors

5,212 profile views
  1. @Briljander Just so we are on the same page, have you been trying to cancel since december but you are still getting charged? I can see in our system and on the forum that you do not have the flair, so I am thinking that is the case. SInce the forum is not open source there is only so much we can do with it, but what I suspect, if my earlier assumption is correct, is that when you cancelled it cancelled in the forum software, but it did not cancel the paypal billing agreement. Let me know if I am correct with this and I can refund you since december. Its nothing nefarious we are doing, we are just using forum software made by another company and doing our best with it it.
  2. Because every country is different and every platform is different, its hard to satisfy everyone and every law. Things are in weird places sometimes, but they are there. Let me walk you through finding the invoices, because they are kind of difficult to find. Click the arrow next to your name and manage subscriptions, Then from there click on view purchase, Then from there you will see a weird string at the bottom of the page called view billing agreement, click that link, Click that link and you can see all of the purchases you made. If you click into one you can download or print the invoices. Its all there, just is a weird spot.
  3. Sorry about that, the forum processes were going out of control, I changed the header cache setting. I did not realize that block was considered in the header cache. I have it set back now.
  4. As @Traumflug mentioned no native thirty bees code is affected by this, unless you are building from scratch and running that in production. If you are, make sure you are not using require dev in composer. It looks like there is another module that needs to be added to the list of modules with security issues, https://github.com/kuzmany/mautic-prestashop
  5. There is no way really. There might be a couple migration tools you could use, but I have not tested them.
  6. I know everyone is looking for a public update from me. I made a post on the supporter forum the other day about what is going on. My health has not been good the last 6 or 7 months. I have unfortunately had to reduce the amount of time I have been able to spend working on anything because of this. That is why I have not been around as much in the last several months. The things I have focused on when I do have the energy and am well enough are behind the scenes things like financing, taxes for the company, and things of that nature. I really wish I could give some kind of positive update, but the truth is I having a surgery next week that will determine how my life will go forward. I just cannot give a definitive answer on anything, or my role until after that and I recover a bit. I feel like I am letting you all down and that really pains me and has been stressing me out beyond belief these last couple months. I am sorry I don't have a happy update this time.
  7. No, it will be after the first of the year before we can look into it.
  8. We cannot decode it without your cookie key. It looks like that override could be the issue, I have not see that one before. Have you tried renaming it?
  9. lesley


    From what I read they are going to claim that the original OS license is not valid because a developer cannot license code that they do not own. So then they will start launching lawsuits against people using the code. That was the hot take I read on it.
  10. lesley


    I don't know if many people saw, but yesterday nginx was taken over by the russian government. That kind of leaves everything with their software in limbo now. https://www.zdnet.com/article/russian-police-raid-nginx-moscow-office/
  11. What @yaniv14 says is the truth.
  12. I wonder if something has been changed since we last updated the module. I will have to look and check it out in the next week or so.
  13. @musicmaster I filled out a bug report to other developers from another platform this week. Let me quote that report. "On line 223 of the /classes/productexport.php file I think there is an issue with the join you are using to retrieve the images. Something around there seems to create an infinite loop which is eating 200gb of drive space up." That is how one developer tells another about a bug. More fixes under the hood, things are broke, ect are what shop owners say to me. If you have specific problems and not vague concerns, please describe them in as much detail as possible. I know of the course of this project you have been pretty good at describing windows related bugs / compatibility issues and they were fixed because someone knew what to look for and how to reproduce them. For smartlook, all it is, is a snippet of javascript. You put it in a site and when a merchant contacts you and says hey a guy named bob said our checkout is broken. You can go through the user accounts and look for bobs account, see when he created a cart, then go to smartlook and watch the video. You dont need any customer interaction. Just a name or a broken cart number. Regarding backwards compatibility, let me give a great example. @Traumflug spent a ton of time rewriting the whole rounding system in thirty bees. He basically rewrote the way that thirty bees handled prices so they would be correct. Are you suggesting that he should have written a shadow system that still spit out the wrong numbers that module developers might have expected in some modules? That is insane to me. I am not sure if we are having an error in translation, or if we have different views on what compatible is. If we fix a bug and it breaks something, we do not consider that a compatibility problem 9 times out of 10. We consider that a core improvement. Now on the other hand, if we remove functionality or say change how the shipping system works and break all of the shipping modules, that is a compatibility issue. Fixing bugs is usually never a compatibility issue.
  14. Here is what we fight against. Fixing one bug in say shipping, that breaks a module that exploited that bug. When we decided to upgrade smarty so that we could be compatible with php 7.3, that broke some themes where the shipping exploited a bug. There was no way around that and also upgrading the smarty version. We try to maintain compatibility while moving forward. If we stopped supporting new php versions people would not be able to use thirty bees on many hosts. Its a tough position for us, but we have to move the software ahead. The easiest way I see to get at least two of your problems fixed is to reach out to the people that made the module and the theme. Ask them to update their software to support the latest versions. I feel @Jonny will likely update his. myparcel, I am not sure For your checkout issues, if it were me, and what I do constantly, is install something like smartlook on the site. That way I can see exactly what people are doing when the order fails so I can diagnose it. It makes repolicating the problem 1000% easier. You are not seeing the same thing that happened with 1.7 and you know it. If you look at most module and theme developers they release new versions when a new version of the underlying software comes out. We are not breaking things on purpose and telling people tough luck, we are fixing bugs. If a plugin or a module relied on that bug, that was bad practice. We can't bloat the software to leave bugs in it and try to detect when we think someone is relying on a bug.
  15. Argh, the messaging system must be broken again. Let me take a look at it.
  • Create New...