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.

Leaderboard


Popular Content

Showing content with the highest reputation since 02/26/2021 in all areas

  1. 15 points
    I'm very happy to announce that we have officially released thirtybees version 1.2.0. This version consists of a lot of enhancements and bug fixes that were implemented in the last (almost) 2 years, including stuff like: PHP 7.4 compatibility - this version is fully compatible with PHP 7.4 Object model audit - database and php model are now in sync. This fixes a lot of weird issues and problems Ability to auto migrate database during update - missing database tables and columns are automatically created by core updater Installation fixes - a lot of bugs were fixed in installation process. Installation should now run more smoother Bug fixes - many issues were solved and more... You can simply use core updater module to update to latest stable release. Or you can download installation package and install it on your test server. I will deploy this version to the official demo servers in upcoming days, so you will have an opportunity to test this version even without the need for installation.
  2. 15 points
    The reason for the delay was caused only by me only, and I apologise for it. The plan was for me to start working on thirtybees full time at the beginning of February. I used to work as an independent contractor for a big client in a bank industry, and I was contractually bound to deliver a lot of work for them. Since the team didn't meet the delivery timeline I was forced to work for them until the end of February. I officially ended that contract last Friday. So, finally, I'm free and able to work on this project 100%. Right now I'm working on initial release, it will be done by the end of this week, probably Thursday or Friday. And then there is a very big backlog of things waiting to be done.
  3. 2 points
    I have finally succeeded, I attach an image. In case anyone is interested, the position is line 234 of product.tpl of version 1.2 thirtybees.
  4. 2 points
    As I outlined in other post, the plan is to have 2 major release a year. We believe that this is the frequency that most merchants will find a-ok. Too many releases can be a big headache -- most merchants don't want to update their store every month or so. It can be dangerous, etc... However, 6 months is a long time to wait for a fix of a serious bug to be released. Therefore, we will have couple of bugfix releases as well. These releases will have a very limited scope, containing only a few code changes that fixes these serious bugs. It will contain only fixes that we understand very well, and we are 100% sure that they don't break anything. This should make updating to these bugfix releases very safe and simple. On production servers, most merchants should keep their store updated to the latest bugfix release, for stability and security reasons. On testing servers, it would be amazing if you would run on bleeding edge, as it would give us an early feedback, bug reports, etc. We will release updated version of core update soon -- this new version will make the whole update process more straightforward and easier to understand.
  5. 1 point
    Most Prestashop 1.6 themes are compatible with thirty bees, yes.
  6. 1 point
    Activate payments for the carrier in Modules and Services / Payment / Carrier restrictions
  7. 1 point
    Couple of thirtybees modules (paypal included) uses psr-0 autoload functionality, but with incorrect file structure. This was allowed in older version of composer (with warnings). Newer version of composers does not allow this, resulting in 500 error code. I have fixed the paypal module. Will have to go over other modules that uses composer autoload functionality and check if they work or not
  8. 1 point
    Glad to see there's finally a release. Competition is encouraging. It's about the same as 1.1.x as of two weeks ago. On a quick glance, two commits actually affecting code, a dozen commits affecting the build system and source code comments.
  9. 1 point
    Done, new version 3.2.0 has been released. You should see it in your back office https://github.com/thirtybees/advancedeucompliance/releases/tag/3.2.0
  10. 1 point
    Nice work. I would just suggest you don't use check (70 == $idCarrier), because $idCarrier will change every time you save carrier in back office. It would be better to modify this check and base it on different information from $data, maybe carrier name or carrier reference id
  11. 1 point
    It should work normally with any template.
  12. 1 point
    Culprit found for fontawsome, at least for my shared server / cloudflare site... header.tpl starts with special work-arounds for the extinct Internet Explorer 7 & 8 which mention fontawsome. I cut them out. Now fontawsome is on my site! The next step is to delete all that is not needed from it, maybe everything but the magnifying glass, but that will take thought and time. @Traumflug "fonts.googleapis" isn't in the code so I suppose Cloudflare injects it, which I use for SSL so for now that has to stay. I did find something to disable but it made no difference - a font chooser in the Stripe module. (I duplicated my site in site in softaculous, unzipped a downloaded copy on Onedrive, and used the search box there before it said I was out of space and I deleted it all again). Thanks to all for help including Lesley for checking source code.
  13. 1 point
    You can modify the module, and save the information to the database, for example by using something like this: Configuration::updateGlobalValue('MY_CARRIER_DELAY', $webserviceResponse['delay']); And in override you can load this information back by calling $carrierDelay = Configuration::get('MY_CARRIER_DELAY'); $delay = [ 1 => $carrierDelay ]; Or something like that
  14. 1 point
    Hi! I hope this is the right place for my post. I want to share with you my thoughts on Thirty Bees. Let me start by saying I like it. It is fast and more stable than Prestashop. However, there are some serious problems with this project. Exposure I have researched the hell out of free e-commerce but found exactly ZERO references to Thirty Bees. The way I found you was via SUNNYTOO, the maker of one of the most popular Prestashop themes. The self advertising word-of-mouth approach has been tried in the past. How many people are using Essentials phone or how many have even heard of it? Lack of themes This issue is on par with the lack of exposure IMO. It is all good that 30bees is customizable, but if a bird doesn't display its feathers it simply won't get a lot of action. Name The name is just horrible. At least establish an acronym that doesn't sound like a disease. But preferably change the name. 30bees is much better than spelling "Thirty". Why? Because the bulk of your developers and users won't be native English speakers and spelling "thirty" is just awkward. You won't find many languages where "Th" is a sound. And have you tried to google for "TB" or "TB e-commerce"? Once I made a shop for a customer who despite my best efforts to explain the marketing side of things insisted on calling her shop "Prideandjoydogcouture". You can imagine how that ended. I just know my marketing. Unless you're willing to invest heavily in advertising, don't use more than 3 syllables or names with high probability of spelling errors. Reluctance to change approach So, without trying to sound overly critical, I have read a thread here in the forum where a top representative of Thirty Bees gave his take on Why TB over Presta. And I understand the sentiment, but sentiments won't boost a business where exposure, vibrant community and choice are the main attractors. You don't win customers over by saying how inept the competition is and that you're here to fix it for everyone. Please, don't be offended by this, but that's the impression it left on me. I seriously dislike Pretstashop for their shady business practices, abysmal support and unstable code. You can break that thing by simply updating their own modules. However, I must choose to use their solution, because I don't have a month to spare to play around with designing the store from scratch. I need to use a theme that I'll just modify and be done with in a few days. It is also nice and good to have a section called "Shops using Thirty Bees" but it doesn't do you any favours when those shops are down. It makes Thirty Bees look like an abandoned project. Why don't you guys get together with some decent and proven designer and aim for the stars? For example Panda is such a versatile theme, but SUNNYTOO have 90% of their business riding on Presta. Unless you become popular, they won't bother updating the old version for TB. I find it astounding they even released the old one for TB. You've been around long enough now to make some headlines in the e-commerce world, so what's holding you back? There surely is a way to incentivize theme makers. Even if it's just one. Bundle a decent theme with the shop that shows off the main features. It doesn't need to be polished and fully featured, just usable, but also pretty. Something to get merchants and developers interested and talking. If you're afraid of diverting revenue to the developer, then look at the current situation. It is already the case and you've no control over it at all. You could at least become selective about the developers officially utilizing your solution. With that and superior stability, you'll steamroll over Presta in a year or two. I wish you good luck and I'll check back every now and then to see how this project is doing, but for now, I reluctantly have to go with the other crowd. Peace!
  15. 1 point
    Here is some modifications you can do for Niara theme modify the "../themes/niara/css/global.css" file starting at line 1848 and replace all the content of the @media for mobiles by this @media screen and (max-width: 767px) { .table-responsive { width: 100%; margin-bottom: 15px; overflow-y: hidden; -ms-overflow-style: -ms-autohiding-scrollbar; } .table-responsive > .table { margin-bottom: 0; } .table-responsive table, .table-responsive thead, .table-responsive tbody, .table-responsive th, .table-responsive td, .table-responsive tr { display: block; } .table-responsive tfoot { display: inline; } .table-responsive > .table > thead > tr > th, .table-responsive > .table > thead > tr > td, .table-responsive > .table > tbody > tr > th, .table-responsive > .table > tbody > tr > td, .table-responsive > .table > tfoot > tr > th, .table-responsive > .table > tfoot > tr > td { white-space: nowrap; border-bottom: 0; } .table-responsive > .table-bordered { border: 0; } .table-responsive .unvisible, .table-responsive thead tr, .table-responsive #cart_summary .cart_total_price #cart_voucher { display: none; } .table-responsive .cart_total_price > td#total_product, .table-responsive .cart_total_price > td#total_price_container, .table-responsive .cart_total_delivery > td#total_shipping { border-top: 0; } .table-responsive #cart_summary > tbody > tr.cart_item > td.cart_quantity { width: 50%; float: left; border-left: 0; border-right: 0; padding: 0; line-height: 34px; } .table-responsive #cart_summary > tbody > tr.cart_item > td.cart_quantity > .cart_quantity_input { float: left; width: 55px; border: 0; } .table-responsive #cart_summary > tbody > tr.cart_item > td.cart_quantity::before { content: "x"; float: left; left: 13px; line-height: 34px; position: relative; } .table-responsive .cart_quantity_button a.btn { border: 0; background-color: #eee; margin-top: 1px; } .table-responsive .cart_quantity_button a.button-minus { margin-right: 10px; } .table-responsive #cart_summary > tbody > tr.cart_item > td.cart_unit { float: left; border-right: 0; } .table-responsive #cart_summary > tbody > tr.cart_item > td.cart_delete { position: relative; bottom: 109px; border: 0; float: right; margin-right: 15px; } .table-responsive #cart_summary > tbody > tr.cart_item:last-of-type { border-bottom: 1px solid #ddd; } } It will do the trick....
  16. 1 point
    Okay, I have actually worked out how to hide it in all three places that it appears. The following lines need to be added to the Add extra css to your pages section in the Preferences/Custom Code area of your TB back office: /* For desktop browser account creation, add this line: */ .account_creation .date-select { display: none; } /* For mobile browser account creation add this line: */ #opc_account_form .date-select { display: none; } /* For the user's "My account" page that they can see after they sign up, add this line: */ #identity .std .date-select { display: none; } The commented lines (/* ... */) do not need to be added, only the code lines that start with . or #. Copy & paste to avoid errors. I have tested the above on TB 1.0.8 with the standard community theme (obviously) and it is working without trouble.
×
×
  • Create New...