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 05/07/2021 in all areas

  1. 3 points
    we have been using TB for a number of years now and I never looked back at PS. Most old PS bugs are ironed out by now and it's a solid and stable solution to run your eCommerce shop. Also we've used lots of modules and only had very minor incompatibility issues that could usually be solved by the module developers within minutes. We have been down the track of Magento, Opencart, Zen Cart (jeeez...remember that), Wordpress with Woocart, Joomla with Virtuemart and J2store and Hikashop and from all the 'free' solutions we've never had anything better than TB. The TB team and still rather small community is active and very helpful. You can report bugs and they don't get ignored like with PS. So in my opinion TB has got to be hands down the best and most feature loaded system out there. But to be honest, if you zero web dev experience you will have to hire someone at some stage unless you run an out of the box system which practically doesn't exist in a real world scenario. Updating modules and themes is not the easiest compared to say Woocommerce and there aren't as many modules and themes available that officially work with TB. Said that most modules will work fine if they are 1.6 compatible. For themes, there aren't that many options I think. We have used the IQit Warehouse theme and recently switched to Sunnytoo Panda which works great with TB.
  2. 2 points
    Hello @Smile @datakick Just to inform you that TB has another opportunity to take a PS piece of cake. They just send a newsletter today that every module will need an annual subscription option. And even minor updates will not be available if you do not pay it. This can make angry some people and also make it less affordable to small merchants. You could try to capitalize this. Regards
  3. 2 points
    Since I've been making modules to make ThirtyBees work for me I've come up with one that adds extra variables on to $product for use in your templates. I call it Extra Product Functionality (link to GitHub). It adds this tab to the product edit page in the back office: Setting these values will add/update variables on the $product in your template. So if your product is a service, you could show a contact button, or list the price as a starting at price. If your product is coming soon, you can use $product->coming_soon to add an additional label. (setting coming soon to Yes will automatically hide the price and make it not available to order). I added the force new option because I can definitely see where someone wants to list a product as new even though it's not new (in terms of date it was created). You can add it to your theme by adding this at the top of your product.tpl file: {hook h='actionModifyProductForExtraFunctionality' product=$product} And to get these values to be set in your product list, add this to wherever for-loops through your products: {capture name="newProduct"} {hook h='actionModifyProductForExtraFunctionality' product=$product capture=true} {/capture} {assign var="product" value=unserialize($smarty.capture.newProduct)} That might look dumb, but I tried for several hours to get my hook to be able to modify $product when inside of a for-loop (or wherever it is an array and not an object) and I couldn't. Nothing I was setting in smarty was getting out of my module. So I came up with this clever capture method. This module definitely has potential and I look forward to expanding it. If anyone has any suggestions, let me know.
  4. 2 points
    Hi This is my opinion, it is not about keeping on the 1.6 version, but about getting rid f the amazing amount of troubles and lacks in prestashop + getting rid of a company that did a good job creating/developing prestashop but also kept in it a lot of nonsense and caused many troubles in the time. One of the things they did that the more kept punching in the eyes is how version after version same bugs and inconsistencies where left there and how bad was their update system. Personally I always had a double feeling about prestashop, good on a side and a nightmare on the other. When then they did 1.7 and tried it I deemed it terribly bad and soon understood that could not become any better for me in the time, that because the languages translation system, which just horrible, rigid, lengthy, slow, absurd I would say. In PS 1.7 I saw no special improvements, on the contrary I saw a regression to worst standards, I just could not understand the choice to cripple the translation system in such a bad way. I do not know about the other users' experience in this respect, but for myself I learnt to not trust at all the prestashop company and their marketplace, I had many frustrating experiences, became allergic to them. That's my 5 cents about. Happy that TB was done and that is kept alive.
  5. 1 point
    In my opinion, when customer goes to checkout page, they need to be reassured first. They really want to know is what carrier they can use what payment method they can use the final price And chex tries hard to answer these questions. Customer is not required to log in or create an account before these questions are answered.
  6. 1 point
  7. 1 point
    Hi, I am new to work with this shop but seems great! Much better than Prestashop, and much faster. Now I am editing my new store but I cannot find anywhere where I can edit the stor info in the footer of the default theme. How do I do that? I need to remove that info from defult and replace it with my correct information. Please help Found it! HTML blocks was the problem. Removed that and now I only have one information about my shop. Have a great week!
  8. 1 point
    It worked! I took it slowly, on backup copies, and the new version still doesn't connect to a PHP 7.3 database, but the main thing is that it works. I tried a vanilla update module as well (thirtybees not merchants edition) and it didn't work. Thanks.
  9. 1 point
    I cannot as I don't have a Samsung device either. According to @Mike1 it is likely trailing spaces causing the issue. Can we autostrip/ignore trailing spaces from the email to eliminate that issue first?
  10. 1 point
    Is this discussion also relevant for Thirty Bees? https://www.prestashop.com/forums/topic/1045112-is-prestashop-able-to-cope-with-new-european-tax-laws/ Implementation would mean that you can set the price incl VAT while the price for each EU would be different depending on its VAT rate.
  11. 1 point
    I don't think that the newsletter module get a lot of attention. Neither do I think that TB should compete with prestashop but rather develop a model where Prestashop falls short. Smaller buniess with 300 to 1500 articles are ignored by the market. Woocommerce and shopify take on those. Less features but easier to handle and ultra stable in questions of updates is the future IMHO.
  12. 1 point
    I think I've got it now. thirty bees' version of Core Updater chokes when being asked to update from an unknown version, AFAIR. Core Updater 2.0 has this issue fixed: https://github.com/merchantsedition/coreupdater/releases/tag/2.0.0 (install the .zip file manually in your back office) This version of Core Updater comes with not two, but four channels. Channels 'thirty bees Stable' and 'thirty bees Bleeding Edge' are fed by genuine thirty bees sources, so you get a genuine thirty bees installation after updating.
  13. 1 point
    Hi. I think you have to change order-address.js in your theme. I'm not sure if this is the way to go or is preferable to add custom javascript. In order to see more information like in the screenshot above you have to right click the element and then choose 'Inspect element'. Good luck!
  14. 1 point
    thanks @Wartin what is the TB file that I should modify following this instructions? This one? /themes/theme/order-address.tpl
  15. 1 point
    Yes, it was another module messing up
  16. 1 point
    Check out @datakick’s module : https://www.getdatakick.com
  17. 1 point
    Changing product template files A more direct answer to your question. The nearest I can think of is to do it for certain products, by using an edited prduct template. Product templates look like this: https://github.com/thirtybees/niara/blob/master/product.tpl If you can get to the file on your server (example.com/themes/niara/templates/product.tpl if your theme is Niara)... You can copy and then edit the template. What I did was to delete equivalent lines to 435 to 463 on the githb link. The loop of code that begins "<div class="box-cart-bottom">". If your server has built-in editing software it might compact the loop of code into one line before you delete it, so you can be sure of getting the right end point, which is difficult otherwise. Your new product template will no longer show a shopping cart and can be enabled from any product page in the back office. If your product is "fresh bread", Backoffice > Catalog > Products > Fresh Bread > Template Manager > choose your new template from the drop-down menu (There is probably a way of editing a product template to ignore "catalog mode", which you can turn on or off from Backoffice > Preferences > General > Catalog Mode | Off The edited template would ignore the switch, but all the products using the standard template could have their shopping carts switched on or off in one go. I haven't tried it though - you'd have to experiment). (I don't know a way of doing for a category)
  18. 1 point
    Es un camino a veces un poco largo, hasta que más o menos encontrás las cosas que buscás. Pero no te desanimes! Hay una buena comunidad que en general responde las preguntas. Por lo menos en inglés, en castellano se mueve menos.. Si algo no está traducido podés ir al mismo lugar y elegir el módulo en cuestión. Hay un botón de 'Expandir' que te muestra todas las oraciones, que muchas veces es muy práctico si buscás cambiar alguna traducción que no te parece correcta. Sobre el error, si te lo da la tienda, podés ponerla en 'modo depuración', para que te muestre errores lo más detallados posible. En el Backoffice, es decir el administrador de la tienda, tenés un buscador, hasta que te habitúes a los menúes. Saludos y suerte!
  19. 1 point
    My thoughts, are to build from scratch but using the community theme for reference. (Although I am very much open to the general perspective of those with experience working on developing the platform and those who have been using it). Why? Efficiency Personally, I find it is quicker and more straight forward to follow a single coding practise or style throughout a project than to patch old code and designs. Technology The community theme appears to be using old CSS standards for layout (still using floats). Building these layouts is a lot easier now that CSS has developed. I expect that I will be able to help create a theme which is of a high technical standard, which is very light. CSS Grid, Flexbox, inline SVG, CSS animations, CSS & SVG sprites, srcsets, localised web fonts etc. Freedom The old theme doesn't need to be scrapped. Maybe it can be patched up, but a new theme should, in my opinion, help to support those who the current theme just doesn't serve (that isn't to say it isn't useful for reference). Maybe a new theme could give the platform some (more) wind in its sails. I know that @datakick and others are putting in a lot of work behind the scenes, and I think that the front-end of the project needs some attention to motivate the community and to encourage other developers to support the team. The new theme doesn't have to be twenty themes in one, but I see no reason why it shouldn't be designed to a commercial standard, while still being in the hands of the tb community. I haven't been on here for long, but I love open source, I enjoy contributing, and I don't stop until a job is done. @cienislaw I agree with @zen, if those who are interested in a new theme vote on what features they want to see, this would be a good start. Something you love in another commercial theme?... anything is possible! So I would love to see what features you have in mind. One thing to keep in mind While the perspective of each individual in the community is important, for the theme to be competitive (so tb sites can compete with those built on other platforms) there must be a consistent, professional style throughout. Many ideas can be good ideas but some ideas conflict. Aiming to serve everyone will likely serve no one. So there should be a clear objective, mock-ups, approval from those who have been working on this project and a single-minded collaborative approach. ---- I am nobody, so no one has to listen to me. But when I come over for dinner, I like to wash up. I use open source software, and I feel I should contribute to say thank you to those who give their time to serve others (including me). At the end of it, if I have a new theme to use with my clients or for a personal project... Awesome!
  20. 1 point
    I have a separate module that handles the shipping discount issue with gift cards. Also on the PS store.
  21. 1 point
    Salut à tous, Le module n'est pas une nouveauté mais je viens de le tester sur le site d'un client et il fonctionne donc je vous informe que vous pouvez le télécharger directement sur mon site. Pardon, j'ai oublié de vous préciser à quoi sert ce module. Ce module gratuit développé par Samdha va vous permettre d'avoir accès en 1 clic au gestionnaire de base de données Adminer directement dans le backoffice après installation du module. Vous pourrez alors gérer la base de données comme avec phpmyadmin. Télécharger le module
  22. 1 point
    Got it. @veganline kindly gave me access to the server. The TLSv1.2 message is a red herring. Test fails, but it's an optional test, which doesn't prohibit installation. Actual issue was a missing error message. The test for ensuring PHP's fopen() takes URLs failed, but didn't report an error, because there is no matching error message. Setting allow_url_fopen in php.ini to 1 should allow installation. And I'll add the missing error message to the sources, of course.
  • Create New...