Jump to content
thirty bees forum

Mark

Members
  • Posts

    277
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by Mark

  1. Im wanting to revamp the look of my site and am mulling over themes.

    Ive only ever used the community theme plus Datakick's one page checkout module and so I'd say thats one key reason why the site isnt very good especially in the eyes of site analysers who often find things wrong with the site. I acknowledge its pretty cr*p looking, even if it is functionally pretty good the front end does not cut it to the point where I want to push this website because people go there and I never see them again.

    But I want to change that so its smart, fast and looks great and looks trustworthy and try this again. (In terms of fast I use cloudflare CDN already so its not bad, but faster still is better still)

    So who uses what theme successfully and happily? and all the indications are your customers love the theme?

     

  2. I appear to have a working version of 1.4, but Core Updater seems to not be updating to 1.5+

    Error message

    Details
    Module 'thirty bees Updater' [tbupdater] is not compatible with target version of thirty bees

     

    v1.6.7 - This is the Updater Version I have, it doesn't seem to be updatable further than that.

     

    ALSO: PANDA- Apparently Sunny has released an update of Panda, is this true, does it work ok?

  3. Ive managed to get the majority of things working again @datakick. Still getting double display of payment options Credit Card and Paypal (that's been ongoing since I got the cart ), this is just a normal bugfix. Still had the "Registered Hooks are executables" message in Consistency Checks, which I fixed manually. this bug will of course be ignored, but just advising anyway.

    image.png.5b89af80defd2c0703612dc713dc9dd3.png

  4. On 5/19/2023 at 5:02 PM, datakick said:

    Enabling debug mode will NOT help you decrypt your existing error txt files. When you enable it, and encounter some 500 error on your website, you will see error directly on the screen. There will be no prompt to download some error txt file and decrypt it. 

    There can be many reasons why your back office don't want to decrypt your error txt files. One of the images in your previous posts shows that your server cant creating files in /tmp folder because of read only filesystem. The same probably happens when you try to upload the error file -- your php server can use /tmp dir to temporary store file during the upload.

    What methods can I use to check the difference between my files inc permissions... And what they should be? I had a full disk the other day and that generated 500 errors which I subsequently fixed when disk space was restored... but perhaps something happened to code/ data when that disk got full?

    Using Core Updater it suggests my files are correct, is there any other way to double check... Note... My earlier post showed that there may be also be executables publically accessible.

  5. Not even slightly true. I download the file generated by the 500 error and upload that into the decrypt function and nothing gets returned. It always used to decrypt fine. This is the file, and here is the image of me decrypting it. The file is not empty or non existant.

    After the decrypt runs, I get the attached message saying "settings have been updated". which sounds weird as no settings should be updated by this process, I should simply be seeing the errors @datakick

    Screenshot from 2023-05-19 10-04-08.png

    exception_202351910017(1).txt

    Screenshot from 2023-05-19 10-08-20.png

  6. This from the Console, also attached is Consistency Checks Output.

     

    NOTE: Enabling Debug mode added no obvious information on the pages concerned.

     

    Exception { name: "NS_ERROR_NOT_IMPLEMENTED", message: "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIAppStartup.secondsSinceLastOSRestart]", result: 2147500033, filename: "resource:///modules/BrowserGlue.sys.mjs", lineNumber: 1611, columnNumber: 0, data: null, stack: "_collectStartupConditionsTelemetry@resource:///modules/BrowserGlue.sys.mjs:1611:9\nBG__onFirstWindowLoaded@resource:///modules/BrowserGlue.sys.mjs:1717:10\nBG_observe@resource:///modules/BrowserGlue.sys.mjs:964:14\n_delayedStartup@chrome://browser/content/browser.js:2029:18\n", location: XPCWrappedNative_NoHelper }
    BrowserGlue.sys.mjs:1620:15
    Some cookies are misusing the recommended “SameSite“ attribute 8
    Cookie “ips4_noCache” has been rejected because it is already expired. login
    update.locale  file doesn't exist in either the application or GRE directories 2 UpdateUtils.sys.mjs:138:13

     

    Screenshot from 2023-05-18 12-05-35.png

    Screenshot from 2023-05-18 12-13-19.png

  7. Currently experiencing quite a few 500 errors it seems, have made no code or server changes, haven't had time to debug yet, but also getting this read only error when trying to update Core Updater.

     

    EDIT: Also when I tried to update Chex, in the modules folder it said "Missing a temporary folder".

    EDIT: Also nothing of any note in "Logs", nothing above severity 1 for weeks.

     

     

     

    Screenshot_20230518-082011.png

  8. My suggestion is to involve more people in the decision making about this website.

    It isnt fair on Datakick that everything rests with him, and it isnt fair on the rest of us that he alone decides everything... even if he does his best. This isnt Datakicks' website or Smile's, its all of ours.

    We all have businesses tied to this, it isnt just about Datakick and Smile and we should all have some right to have some say over some aspects and we certainly should not have NO rights as Datakick has said. WTF?!! Overlord alright! I dont care who "owns" the company, we should all have some involvement and input into some things.

    All TB owners should be able to participate in some aspects of this so that its more democratically decided and less of a burden to Datakick to decide for all of us.

    There's obviously software around that can do this job so its not a big deal, probably it can even be enabled in github. Owners can feedback about features and see and contribute to these, priorities and to some degree some bugs.

    Personally I scarcely notice anything that gets done on the website, its all just countless little things not visible to the user's eye, nothing significant as far as features ever seems to change much and the bugs Ive always seen and kept quiet about still mostly exist. If I report about key things like GeoLocation it gets chucked out because it doesnt matter to Datakick!

    More resource is needed!

    Much stuff we have no idea about whats coming up, such as warehousing changes and info about the forthcoming warehouse module datakick and smile are working on.

    We don't we get this info?? Why should it be cloak and dagger? I put a post out seeking details... noone replied... ASM Warehousing is major.... I certainly want to get an idea of what's planned there....

  9. 18 minutes ago, Mark said:
    12 hours ago, datakick said:

    There are two distinct things we do in thirty bees company. Firstly, we maintain open source project. This means:

    • we are keeping the codebase afloat - we adjust code to run on newer versions of php, database, php extensions, new versions of dependency libraries. Without this, nobody in 2 years could run thirty bees project on any up-to-date server
    • We fix bugs in core and more than 100 modules, as we assumed responsibility for this code
    • We maintain github repositories for core and those 100 modules.
      • We do code review for new pull requests.
      • We scrub new issues, deciding if the report is bug or enhancement request, trying to reproduce the issue, etc
      • We investigate and implement security patches that are reported by third party security advisors
      • We play the gatekeeper card here, and decide what makes it to the codebase and what not. We hate to do that, because every line that makes it to the codebase becomes our responsibility, and we have to fix all bugs it might cause. So if the PR have tendency to cause a lot of grief, it will not make it to the codebase.
    • We maintain set of api services that provides
      • core updater functionality
      • translations
      • module updates and distribution
    • We maintain forum, trying to help as much as possible
    • We maintain store, web, demo, and other websites.
    • and more

    If you look closely, you will notice I did not mention new code or features. We don't do that. At least not as part of thirty bees project maintenance. This maintenance is actually what you are paying for, if you are a backer.  

    We do create and release new code under open source license, though. But that code is actually not part of open source project maintenance. Thirty bees company offers paid support and custom development services that anyone can purchase. Smile does exactly this. His private company purchases a lot of support time from thirty bees company, and invest it into the area he is interested in. It was warehousing feature are, packs, feature management, multistore, etc. Some of this new code development is done in core and released for everyone to benefit from. Some of it is implemented in new modules, that are either private, or ready to make available for everyone to buy. 

    This custom development is a private initiative, not a public project by thirty bees. It is paid by third party company. Decision what features will be implemented or enhanced is entirely up to the company that purchased support time.

    Note that I play the codebase gatekeeper card here as well. I do not allow new code that could break the things for others. Some requests could be implemented very easily in a few minutes, but because they need to be reusable for everyone, it can actually take a few hours or even days to implement that in generic way. Smile is paying for that extra time, even though he does not benefit from it directly.

    Anyone can contact us, purchase some custom development time, and implement any feature they want. We will be happy to provide that service. Or they can hire third party developer to do that for them. We will do the code review, and merge any PR as long as it does not break things for others. 

    Everyone can contribute to the open source project. And if they do not like the way we do the gatekeeping, they can fork it and maintain their own version. @Mark says that I'm playing the overlord and decide for everyone, and it's true. That what open source maintainers do. Somebody has to be the bad guy that rejects bad contributions. I'm comfortable being that asshole, I'm doing my worst for a good of thirty bees community, at least I believe I do so.

    Why are we maintaining this open source project? We don't really have to, now do we? I mean, Smile could fork and create his own version of thirty bees, hire me or other developer directly to maintain it for him. He would save a ton of money on development time, as there would be no backwards compatibility issue to solve. We could change anything and tweak everything directly in core. No modules, no overrides. No bugfixes for modules we don't use. No maintanance of code we don't use.

    We are maintaining the thirty bees project because we like the community, and we like to give back. We will continue to do so as long as we feel that there is a community to work with, and that the community cares. Being a backer means a lot in this context. It helps offset the expenses directly related with code maintenance, and it shows that there are people invested. It's a nice and tangible metric. 

     

     

    All of this is true and well stated, thanks and we all certainly do appreciate the work that goes on on just keeping the animal alive.

    If you read between the lines, we are saying similar things in many respects.

    What I'm saying is that I think the project deserves much more resource than it gets, and that means others directly contributing more to it and getting paid to do so, or some other tangible benefit, by helping. This includes module developers as well as core.

    I realise its a nice community and that I'm the only asshole here because I say challenging things, but I wouldnt bother with this if I didnt also care and want better things for the site.

    There's far too much work here for just one man to both manage everything and be lead developer for.

    There's vast teams out there working on much smaller codebases than this one.

    The whole thing is far too under resourced for what it is.

     

  10. 11 hours ago, datakick said:

    There are two distinct things we do in thirty bees company. Firstly, we maintain open source project. This means:

    • we are keeping the codebase afloat - we adjust code to run on newer versions of php, database, php extensions, new versions of dependency libraries. Without this, nobody in 2 years could run thirty bees project on any up-to-date server
    • We fix bugs in core and more than 100 modules, as we assumed responsibility for this code
    • We maintain github repositories for core and those 100 modules.
      • We do code review for new pull requests.
      • We scrub new issues, deciding if the report is bug or enhancement request, trying to reproduce the issue, etc
      • We investigate and implement security patches that are reported by third party security advisors
      • We play the gatekeeper card here, and decide what makes it to the codebase and what not. We hate to do that, because every line that makes it to the codebase becomes our responsibility, and we have to fix all bugs it might cause. So if the PR have tendency to cause a lot of grief, it will not make it to the codebase.
    • We maintain set of api services that provides
      • core updater functionality
      • translations
      • module updates and distribution
    • We maintain forum, trying to help as much as possible
    • We maintain store, web, demo, and other websites.
    • and more

    If you look closely, you will notice I did not mention new code or features. We don't do that. At least not as part of thirty bees project maintenance. This maintenance is actually what you are paying for, if you are a backer.  

    We do create and release new code under open source license, though. But that code is actually not part of open source project maintenance. Thirty bees company offers paid support and custom development services that anyone can purchase. Smile does exactly this. His private company purchases a lot of support time from thirty bees company, and invest it into the area he is interested in. It was warehousing feature are, packs, feature management, multistore, etc. Some of this new code development is done in core and released for everyone to benefit from. Some of it is implemented in new modules, that are either private, or ready to make available for everyone to buy. 

    This custom development is a private initiative, not a public project by thirty bees. It is paid by third party company. Decision what features will be implemented or enhanced is entirely up to the company that purchased support time.

    Note that I play the codebase gatekeeper card here as well. I do not allow new code that could break the things for others. Some requests could be implemented very easily in a few minutes, but because they need to be reusable for everyone, it can actually take a few hours or even days to implement that in generic way. Smile is paying for that extra time, even though he does not benefit from it directly.

    Anyone can contact us, purchase some custom development time, and implement any feature they want. We will be happy to provide that service. Or they can hire third party developer to do that for them. We will do the code review, and merge any PR as long as it does not break things for others. 

    Everyone can contribute to the open source project. And if they do not like the way we do the gatekeeping, they can fork it and maintain their own version. @Mark says that I'm playing the overlord and decide for everyone, and it's true. That what open source maintainers do. Somebody has to be the bad guy that rejects bad contributions. I'm comfortable being that asshole, I'm doing my worst for a good of thirty bees community, at least I believe I do so.

    Why are we maintaining this open source project? We don't really have to, now do we? I mean, Smile could fork and create his own version of thirty bees, hire me or other developer directly to maintain it for him. He would save a ton of money on development time, as there would be no backwards compatibility issue to solve. We could change anything and tweak everything directly in core. No modules, no overrides. No bugfixes for modules we don't use. No maintanance of code we don't use.

    We are maintaining the thirty bees project because we like the community, and we like to give back. We will continue to do so as long as we feel that there is a community to work with, and that the community cares. Being a backer means a lot in this context. It helps offset the expenses directly related with code maintenance, and it shows that there are people invested. It's a nice and tangible metric. 

     

     

  11. On 1/15/2023 at 9:18 AM, wakabayashi said:

    Do you know that this project is dead tomorrow, if datakicks or smile "have enough"?

    Your behaviour is very disrespectful and without any reason. Datakick does merge a huge amount of PR in a fast manner. You seem to have no idea, what it means to lead this project...

    This is a serious ecommerce site and it should be setup properly with website owners represented in the decision making process to at least some degree and there should not not be such huge responsibility on Datakick alone. I agree he does an excellent job to a high level of skill and commitment, but he does whatever he likes since there's noone else involved.

    Although I dont code I have been paying as a "Generous supporter" but going forward I won't be again until there's a proper process for getting bugs and enhancements fixed that gets decided on by multiple people representing different angles including site owners. Hasn't anyone heard of project management/ agile/ scrum? And understands the importance of balance instead of one guy doing everything?

    Geolocation is an absolute no brainer in terms of getting country location exactly right since so much depends on country be accurate.

    People need to stop taking things so damn personally and get key things sorted like Geolocation and get running things far more professionally. This is not an attack on Petr so much as it is a desire to get this thing the focus it deserves instead of it being a few geeks doing whatever they like and telling me to go stick it because I raise questions.. when all Ive ever wanted is for this site to be awesome.

    The problem really is that this site is not managed properly, its far too big for it to be a one man band.

    I realise Smile has bought this off Lesley because he's able to and is a nice guy and it keeps Petr going, but this needs a bigger view so it brings in money and it can pay people to help, attracts module builders... instead of it being just a "good guy" type scenario. You are quite right wakabayashi, at some point that arrangement will die. Its far too fragile already if I can say a paragraph that terminally upsets everything and everyone bails. Something needs to be done now if things are THAT fragile. The codebase wont die though, it will live on.

  12. On 1/5/2023 at 7:21 PM, datakick said:

    Again, there is NOTHING to fix here, from the thirty bees perspective.

    Thirty bees / ps16 always performed geolocation using maxmind database. Because maxmind stopped supporting database version 1, we had to fix it. When we were doing that, we though that it's a good thing to make this 'detect country' functionality pluggable, instead of depending on single implementation. So we extracted it to separate maxmind geolocation module.

    We support both this new module, and geolocation functionality in core core. If you use these two together, you will have the same functionality that always existed.

    This new pluggable architecture allowed ME (not thirty bees) to create another module that gets the geolocation information from cloudflare. This module is mine. I made it myself, in my free time. It is new functionality. It is not part of thirty bees native modules. From thirty bees perspective, this is just ordinary module by third party developer.

    You don't have any rights to go on this forum and demand changes to that module. It is absurd. It is like you creating a new issue in thirty bees project demanding changes to Panda theme. 

     

    One person controlling this entire website should never have been permitted. There should always have been a few people deciding what goes on on this website in a transparent process and certainly a feedback system to allow site owners to feedback about features.

    I never claimed to have rights nor have I demanded anything other than important concepts to be considered instead of thrown out without due care..  but you have no consideration for site owners .... just your own plans and power and you refuse to listen to anyone.

    You don't own this site so far as I know, but you do control it and you shut out others saying commonsense things like "get geolocation accurate'

    Stop acting like an overlord and listen to others.

    • Confused 1
  13. 3 hours ago, Briljander said:

    You must be this forums most negative person. 

    If you want to get it fixed fast why don't you just pay @datakick or any other developer to do it for you? 

    Because it's a core function for everyone not just me and always has been. Asking people to get on with things is positive in my my book, yours is obviously a shorty story not a book

  14. I don't know if we will ever see thirtybees evolve beyond a one man band just doing little fixes that suit him

    Some people have serious things they want to do and all that ever goes on is tinkerings without any consultation with anyone else, one guy deciding everything that suits him, ignoring anything challenging or important and just doing whatever is easy that he likes.

    Thirtybees isn't a proper thing professionally managed it's just datakicks way of getting paid to do whatever he likes.

    It's never had a commercial clue at any stage

  15. Been having trouble with geolocation.... I do not want to use maxmind (does it even work?) I only want to use cloudflare country headers since I know they are accurate.

    Its really important that the correct country is used in the system, for managing many things, including country management with google and getting countries exactly right.

    I have not figured out how to correctly use Cloudflare headers and the system is not reliably detecting user country.

    I put this request https://github.com/thirtybees/thirtybees/issues/1539 in to get this fixed but in classic @datakickstyle it gets thrown out the window as an enhancement, since country accuracy doesnt seem to be anything but a bother, probably never to see the light of day and get fixed, even if it is simple to do since its just data in a header.

     

    image.png.c6b0bf7d33b34c85a4e34ecc823bca89.png

  16. There's something odd about TB management structure they are not interested in the promotion of thirtybees. Everytime revenue ideas for the company gets mentioned they go quiet.

    The owner funds tb out of his own shop success and for him it's probably a case of being able to run TB at less than the cost of having his own private dev team, plus the work benefits all of us not just him and for that we are grateful. It means he can push tb in the direction he wants it to go and if that works for all of us then lucky us, if not then hard luck.

    But if there isn't a community of developers making money plus the business supporting itself then it will die the minute the owner gets bored with this or it no longer suits his business needs and that's a big risk for all of us.

    • Like 1
  17. Hi all, @datakickmentioned in the last newsletter about there being a new warehousing module coming up, which sounds excellent. I discussed with him about putting up a thread to get input from others regarding the module also.

    It will be a paid module and they are basing the new module around an existing TB implementation using the presumption that other warehousing systems will be pretty similar to the one they are using to build the new module with.

    Maybe we can use the opportunity to suggest things that we would like and maybe @datakick can run through what is being proposed.

    My first general question would be:

    Will the existing core free ASM change to any degree, if so how. Will there still be a free core ASM, or will we have to buy the new one?

     

  18. On 9/30/2022 at 9:28 AM, AndyC said:

    Thanks for replying Mark. I have been put off even trying but so many bad reviews about Tiktok.. If you have any luck please let us know

    There's a free tiktok module on Prestashop but its fairly sketchy in terms of what it could be doing tracking things, also its only Presta1.7 compatible and didn't work properly for me as a result. Ive asked devs if they would consider 1.6 version but no response, have also provided this feedback to Tiktok.

     

    Other than that I havent got much further @AndyC

    • Thanks 1
  19. 1 hour ago, x97wehner said:

    Seems they tend to go hand-in-hand with a theme, for styling and such. The whole front-end needs that overall out of the box package redone by someone who understands themes can make the whole standard TB experience much more rich. That person is not me. 😉

    Not me either 🙂 I suspect some of what I mentioned is back end and some will be theme, you are quite right.

    • Like 1
×
×
  • Create New...