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.


Popular Content

Showing content with the highest reputation since 01/13/2021 in Posts

  1. 6 points
    Hello everybody and happy new year. I spent a lovely Christmas / end of the year with my family, without access to internet, computers, and so on. I feel fully charged and ready for this new challenge. So let's do this. I must confess that I was a little dishearthed with the cold response to the announcement. While I understand you guys don't really care if this project continues under the same name, it's a big deal to us. Fork would be a very different starting point. It's very nice to have hundreds of active websites using our platform already. And it's amazing to inherit existing thirtybees infrastructure (forum, websites, demo, api servers, mail servers, translations, deployment, testing). If we were to start from scratch, it would take us a year to get to this point. The effort to achieve this would be huge, and nobody would really benefit from that. Especially not you, merchants. After a lot of mundane work we would end up at the very same spot we are now. If we weren't able to close a deal, I'm not sure if we would even try to do this. So yeah, we were really excited about it. But I am fully aware that you don't really care about all of this. You expect roadmap, business plan, etc... and it's a fair point. So let me talk a bit about this. Monetizing strategy: Our team have talked a lot about different ways to earn money that are needed to keep this project afloat. Realistically there is only a handful of them that we can pulled off, considering our limited resources. For example, we have dismissed the idea of providing SAAS or PAAS service. In the first few months, the majority of revenues will come from the support services that we will provide to merchants. This means that portion of my development time will be allocated to paid support. We believe that this is the best way to bring in some money right away. Also, the existence and availability of official support will surely make platform more attractive to undecided merchants. Support services revenue model does not scale well, though. There is only finite amount of time we can provide. Even though we want to bring other developers aboard, the time will still be a limiting factor. We are fully aware of this and we have few other plans for a long run. Development: First of all, I want you to know that I will devote 100% of my time to this project, starting February. Currently I'm finishing my current development contract, and closing my existing activities (for example support service I provide via datakick agency). That means that this month I will work on thirtybees only part time. But come February you will start to see some real progress. As I wrote above, part of my time will be dedicated to support, something between 30% and 40%. The rest of my time will be dedicated to github maintenance - I will scrub and address each and every issue, pull requests, doing code review, etc. bugfixing - issues will be categorised by severity, and some of them will be fixed. Not all - that's just not possible. I expect to spend 15% of time on this. That should be good enough to fix around 40 serious issues per release. new feature work - for every release we will select (with your help) some new features, and we will commit to implement them. I expect to spend around 25% of my time on this area. If you have some ideas what you would like to see in the core, or idea for new module, let us know (unless it's multiple feature value, I've heard that one 100 times 🙂 platform enhancements - the rest of my capacity will be dedicated to platform enhancements. These are development tasks that you, as merchants, will not immediately benefit from. But they just need to be implemented. Some of these tasks will not be very popular, I'm sure. For example, I want to implement some tracking in order to have good knowledge about system usage. Such information will allows us to focus our efforts on areas that are heavily used. (But don't worry, we will be very correct. No data without your consent will be sent to us). Other tasks from this area will be more appreciated, such as php 8 support. Or tool to create custom field for product or customers, or to edit properties of existing fields. Release cycle: Our main focus always was, and will continue to be, on stability. Based on our experience we strongly believe that merchants don't really want, or need, too many releases. So we decided to have just two major releases per year. Other than that, we will have monthly bugfix releases, that will contain high severity bugs only. There will also be bleeding edge release that will always point to the latest development (just for brave). Bleeding edge is de facto Release Candidate. All of these releases will be available for download, and of course via core updater. The first official release will be prepared in a few days. It will be branched from current bleeding edge. Partnerships: For thirtybees to succeed we need to have thriving ecosystem. That means both merchants and third party developers. We have quite a lot merchants using our system already, which is a good news. Unfortunately the situation with module and theme developers is more worrying. Sad fact is that there aren't many developers that support our platform at the moment. And we need to change that. We have a plan to actively outreach to them, offer our help with adapting their modules and themes, make it easier for them to become part of our platform. If you know about some module you would like to see adopted, PM me details!
  2. 4 points
    Hello. I've been using TB for almost a year now. I believe in free software and that's why I try to make my little part helping new users with my very little knowledge of this platform. It's really nice to read the good news, as just a few month after starting my project I read that long thread and was really waiting to see what will happen with development. Good free software is made not just by code, but with the people who use it, and found here a lot of good users that helped me a lot. Enough for the introduction, show me the features ;) A nice ready to use mobile friendly Niara is mandatory. I had to do a lot of modifications to use it, it was pretty horrible out of the box. As somebody said, it's nice to have a little product picture in the search box, as you type. I managed to do so pretty easily: https://forum.thirtybees.com/topic/4213-solved-add-images-to-ajax-search-override/ Another thing would be to have a ready configured Pick up at store carrier that is not counted as a free shipping method (as it is not shipped anywhere, just waits to be picked up) An easy way of export the list of products ready to be imported again. I had issues with HTML in description fields not being exported, so i had to do it the php+sql way. One vote more for 3 step checkout. I uploaded a .zip with some modifications for Niara in the thread already posted here. Fixing Product Customization, besides autosaving, it's not working at all, making it unusable: https://forum.thirtybees.com/topic/4139-error-in-cart-with-products-with-custom-fields/ A lot of things have been discussed in the forums and already fixed by some of the users. It would be excelent to have those modifications into the new version. Thanks again, and see you over here :)
  3. 2 points
    Add a default way to have a guest customer create an account at or after checkout just by clicking a checkbox. Similar to what many large retailers do now.
  4. 2 points
    I hope that all forces will be joined together, it's always better to remain a solid group than being seperated and alone in the jungle of the web 🙂
  5. 1 point
    oh cool, thank you! weird that I haven't found the user or repo by searching github... Thanks! I'm very new to ps/tb module dev and am not a programmer but more a content creator/designer/scripter. So the time I can spend on coding is a bit limited but I'll see what I can do, I need this too asap 🙂 I'll surely update you as soon as I know that there's any chance of me getting it to work/done, or maybe i'm just going to pay someone to develop it for me, in any case I'd make it publicly available, hopefully as open source. But I sadly cannot guarantee you that there will be a module in the end 🙂
  6. 1 point
    Here it : https://github.com/vblanch/cryptocurrency_ps_module The underscores made the ps into italics and messed up the URL. 🙂 Would you mind sharing how your attempts at a new module go? Coingate is such an idiotic company I'd also prefer to go a different route. But they have so many different currencies. Lots of potential there.
  7. 1 point
    In my last post, I naturally had various suggestions as a wish. Who wouldn't want one or the other? However -> this back office improvement would be an absolute dream: I just looked through this topic again, but haven't read anything about the back office menu. Many months ago I saw it here in the forum, but now I haven't found it. If the menu bar is too long, the lower menu items cannot be reached outside of the viewing area. Scrolling etc doesn't work either. I'm not sure if this is maybe already marked as a bug somewhere.
  8. 1 point
    Links to the Royal Mail click and drop system. Lot’s of requests on the Royal Mail click & Drop feedback system, but being ignored. Although nice if it was inbuilt, a paid module would be good also
  9. 1 point
    Fail2ban will solve this problem. Also, not using Fail2ban to protect again brute force login attacks, your site will be hacked - sooner than later. https://www.fail2ban.org/wiki/index.php/Main_Page
  10. 1 point
    What datakick suggested here:
  11. 1 point
    I have noticed this bug myself long time ago and have always payed to much taxes on shipping to the government. Will try to push this bug to be fixed a.s.a.p.
  12. 1 point
    I would say a decent return/dispute system and a fixed asm.
  13. 1 point
    You can probably still log in to your backend (hopefully) if you can, log in and go to Menu >> Advanced Parameters => Performance On that page, enable debug. Then reload your frontend You should see the error that is being encountered. Post whatever is relevant here.
  14. 1 point
  15. 1 point
    This is related to php8 and it's Attribute class. Even if you don't run on php8 there is already a polyfill that introduces this class, and that breaks the whole tb store. I'm currently working on this issue, it will be fixed soon.
  16. 1 point
    In case not tried already... Seobility.net keeps me occupied, used about once a week as the free scans can run-out. Also Gtmetrix.com. The Seobilty dashboard page has tabs for onpage, backlinks, and rankings. Suggestions for ranked pages are hard to find at the bottom right of that page, but worth a look if some of your pages already rank on page two. Backlinks aren't much listed on the free account, but if you use the site without an account from another browser the listing is better and you can check your own site and similar ones to see who links. Onpage tests never quite come-right for me but get gradually better. I often score badly for duplicate content but the similar test site ahrefs says I am OK so this isn't a precise measure. The ebbs and flows of popularity are as rapid as tides and should not cause panic.
  17. 1 point
    Yes,I decided to completely rejig the zone structure to better arrange carriers Then it got messy and I ended up disabling ASM and then the site till I could sort it out. The big thing I learned was ... that if you deactivate ASM, it has to be reactivated again, product by product....... So Im doing that now, should be ok after that.
  18. 1 point
    Have you tried Consistency checks by datakick. It can often solve issues ,,it has for me in the past Also which payment methods are not showing up , knowing which 1 may get more help
  19. 1 point
    I normally say Gift sector .. As it's tankards/hip flasks etc
  20. 1 point
    Hmm, why another fork? Wouldn't it be better to gather all forces and try make TB better instead of two different versions?
  21. 1 point
    Hi guys, I'm a merchant from Poland, running TB from the first versions. I'm also an IT pro with an additional developer on board. I'm planning to use our experience into a small e-commerce business this year, and I'm thinking about supporting TB in some way, as it's been good for us :) We can help with some dev, infrastructure, maybe some marketing. Shoot me with a PM if there's any way I can be of an assistance. All the best! Daniel
  22. 1 point
    One thing I have considered - but I believe should be done with direct access to the backoffice - is price calculation. You should enter a cart number or an order number and see a complete explanation of how the pricing is processed and what system settings play a role. The script should both make its own calculations and retrieve the values that the TB functions have calculated. Rounding questions regularly come back on the forums and with such a functionality people could provide a screendump with all the relevant information.
  23. 1 point
    @30knees this actually got me thinking about combination selection. I come up with the idea of having some sort of intermediate page for products with combinations (well, some of them). If customer clicks on product, this page would be displayed instead of standard product page. It would work somehow like category, showing all combinations within product. One attribute could be primary to let visitor quickly decide on some main characteristics, in your use case it could be gel or capsules. If he click on any of this, standard product page with pre-selected attribute would open. Or he could scroll down and see all possible variants of the product. Something like this: This flow could be interesting for some products I believe. And it shouldn't be that hard to implement as a module. Just a morning brainstorming session to get me started my week :)
  • Create New...