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 10/22/2020 in Posts

  1. 7 points
    It's long ago. I have been here. I have a lot of ToDos on my list. I have taken the most relevant out and post it here: E-Mail: Core function with core template, that just allows to put in some array with content. That way you need just one html file. Each email looks the same and modules can easily add email functionality. Images: Add a cover_2 image to getProducts function In general it sucks, the way one has to get Cover Image as a coder Customers: A way to merge two customer accounts Login as customer (there are modules, but it would be a nice core feature) -> also if there would be an easy way to use it for devs. Imagine you can send email links with default login… Addresses: Clear way to define required fields Sometimes a line more, would help a lot Combinations Allow them for bundles and probably digital products Allow different descriptions for different combinations Allow different gtin for different combinations No forcement of using default combination Products Add archive column -> merchants often don't want to delete product information, but they often have products, that they don't need for ever or at least a big time span. If you have multiple thousands products, it helps a lot for filtering. Same could be helpful for Suppliers. Remove Tags and only use Features Remove on_sale checkbox -> what is it good for? Automate this by checking special prices… Accesoirces groups -> Imagine you sell Digital Cameras. You might want to define USB Cables as accessoires. But I don't think you want to update every camera, always when you got a new USB Cable. Define a default text for available_now and available_later Allow extra fields Product Features: Multiple Features (done) Add Feature types with units or allow at least suffix and prefix value. That way filter modules can work without any issues. A filter module could than easily group values or work with ranges… Create Product Listing Pages from feature values. Imagine you sell books. It would be cool to have a product listing page for "Stephen King" with one click. Categories Allow extra fields or add at least a second description Voucher Allow to use it on product and shipping value. We sell vouchers and customer still need to pay for shipping even if his voucher value is bigger than product+shipping. That's not acceptable. Checkout: A clean checkout with ajax Adress saving Drop the two different checkout system. It's just a mess. Customer Service: Clean forms and handling in the BO. Nowdays you don't even know from where a message comes. Sometimes you get an email sometimes not. Have a good sync with email folder. My wish would be, that I can 100% handle customer cases in BO. Allow shortcodes on predefined messages and include attachments Handling returns Order Status: Remove some functionality and implement clean processes. Imagine you have a Status: "Service in progress". How could you say if the order ist paid or not? This should all be handled by order payments What is logable status good for? In my opinion an order should have two bools: paid and shipped. This should be handled auto by modules. Then you have a status canceled. The rest of status should just be for displaying infos to merchant/customer, no funcionality should be involved imo. Order Edit: Give more flexibility on invoice and delivery_slip generation. Why can't I edit an order after I genereated an order_slip. That makes no sense to me. A merchants knows best, when he needs to change/generate something. In my opion merchants should be able to generate as much invoices as they want per order. I don't see any need for invoice tables at all. I would just save a pdf. Maybe it's naive, please tell me. But I believe for us it would work perfectly. Allow to delete an order state. Sometimes you set it by mistake. Remove "tracking status" What is it good for? Remove "customer more" button. You can just click on the name… We have already too many buttons. Having to buttons to save address "Save as new Address" and "Override". Right now it's always saved as a new adress. In our case we want 90% of the times the "override". Either integrate a usable "return system" or remove it Allow to edit shipping costs (I have actually almost done it) Allow to edit payment method, allow to edit/delete payment lines (right now, you can only remove). On the otherhand the "details" can probably removed. Anybody really wanna save credit cart data on his server? Allow to add a cart rule by code. Order Add: Allow to select the real payment method. In fact you can just select the payment module… Use a real shipping free stuff. In fact it just adds an ugly voucher. Stock: Oh I better don't begin. It doesn't make sense as long as combinations and bundles aren't handled cleanly. Captcha: Simple Usage of Captcha for devs. So that not multiple captcha version are used. Backoffice List Allow better filtering (>=2) Allow better sorting (two columns) Allow custom display of columns -> every merchants wants a bit different columns. Modules: Right now you have to set controllers, where you don't wanna show a module output. In my opinion it would be better if you would set where to show. Why is Payments under modules but Carrier has it own menu in BO? What we don't need: Full Cache Page System -> TB is fast, if you aren't greedy on saving money for a good webspace.
  2. 6 points
    This is just a short FYI: We are currently integrating various features to main branch (aka bleeding edge) in preparation for release of thirty bees version 1.3.0. Some of these features require special initialisation, for example creating entries in database tables, new menu items, etc. Unfortunately, current version of Core updater do not support this functionality - only code is updated, and potentially database schema is fixed. But no data fixtures can be inserted into the database as part of update. This is serious limitation that prevents us to roll out of new features. Therefore, we have decided to extend Core Updater and implement this functionality. New version will be released soon. This new version allows us to introduce new core code together with all data fixtures it needs, nicely wrapped together. New functionality in 1.3.0/bleeding edge already depends on this new core updater functionality. Unfortunately, this also means that in order to update to upcoming version 1.3.0 (or current bleeding edge), you will have to first update your Core Updater module. Current version of core updater CAN NOT be used to update to this new version, because the system database would end up in inconsistent state. You can still use current version to update to 1.2.0, but not to main (bleeding edge). This is wanted behaviour. Once new version of core updater is released (hopefully this week) and you update to it, you will once again be able to update to bleeding edge and/or 1.3.0.
  3. 6 points
    Hello! Thank you very much for all this work. I am part of an NGO, the Gisti, which has been happily using TB for the past 3 years, instead of PS1.6, for the sale of its books (paper and PDF ebooks), goodies, registration to study days, and to allow our supporters to make donations. We would now like to allow subscriptions to our publications. This little email is to tell those who are hesitating that if the TB organisation has gone through some turbulence in the last year, on our scale, this software has always proved to be much more efficient than PS1.6 (and even PS1.7, whose multitude of malfunctions pushed us to change cremerie for TB), so we have decided to support the momentum given by the new team by starting today our support to the project, 100$ per month. Long term support. Have a nice day Marc
  4. 5 points
    Hmm, why another fork? Wouldn't it be better to gather all forces and try make TB better instead of two different versions?
  5. 4 points
    Dude, you're becoming very annoying. Please stop your negative criticism, it's getting the project nowhere!
  6. 3 points
    Hi everyone, Elasticsearch module received some love lately. A lot of bugs were fixed. Module should now work on php7 version without issues, and ES versions 5.x, 6.x, 7.x should be supported. Before we release the module officially, I would like to ask community member to test it. You can download pre-release version here elasticsearch-v1.1.0-pre.zip For testing purposes you can start up elastic search in docker using command like this: docker run --rm -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" elasticsearch:7.11.2 Many thanks to @zen for his contribution. Most of this release is based on his work.
  7. 3 points
    Thanks for the support and contributios @zen Looking forward to an exciting future together 😀
  8. 2 points
    Obviously I don't know what happened here. But what I know is, that merchants have to high expectations on DEVs. Devs don't understand the needs of merchants properly. Merchants think: oh lets improve "return handling" or "we need a modern theme". It's not enough to say that. You need exactly to draw, what of the current process is not working or is bad. How it should be designed in the future. Merchants don't even take the time to articulate this things. I have started many initiatives to make progress, but almost nobody joined. So dear merchants: stop crying and start to deliver. What does it mean in practice? Everyone can say it!? It's like a consulting says: oh just offer the best products with best service to the lowest price - then customers will love you...
  9. 2 points
    This is how selling virtual products worked for years, and thirtybees supports it correctly. Look at 'EU VAT For Virtual Products' tax rule. Once you hit 10k euro limit, you should set this rule (or its clone) to all your products, and it should work properly
  10. 2 points
    You are right, making it not visible really break javascript. That's insane. Please file bug on gitub (although that will fix the issue in niara/community theme) You could try to fix it yourself. Edit file product.js, find function findSpecificPrice, and remove this: .not(':hidden'); This is second similar issue I've seen lately. We really need to implement some javascript data layer for themes, and not depend on data stored in dom.
  11. 2 points
    Well you won’t get help like that. This is a community support forum, main contributors are other sellers like you just trying to help in their spare time. You will not get instant answers, and sometimes no help at all. You need to have some patience Most visual things are in the modules section. Look there for sliders.
  12. 2 points
    When someone wants to build a module from Prestools product-edit I would be happy to cooperate. The most popular mass edit module on Prestashop Addons (https://addons.prestashop.com/en/fast-mass-updates/19965-bulk-mass-editing-products.html) looks like it took quite a lot of inspiration from Prestools. If such a module was made both for Thirty Bees and Prestashop it could pay for itself. As I see it mass edit and cronjobs are areas that have a broad appeal and could help TB too. One of the latest additions to Prestools was image edit that allows you to add images by drag and drop. You need to generate thumbnails afterwards as otherwise it would take too much time. However, for Prestashop 1.7 that is not necessary as it generates its thumbnails on the fly. It might be a good things to have such a thing in Thirty Bees too. Also for mass import by csv. Many of the latest additions to Prestools concern maintainability: integrity checks and cleanup procedures. My main inspiration was that I had to deal with some old shops with quite a lot of decay. As I see it, such old shops should play some role in the discussion about stability.
  13. 2 points
    P.S.: ganz ohne Cookies wird es jedoch auch in Zukunft nicht gehen. Für Login und Warenkorb braucht man einen. Das lässt sich jedoch DSGVO-konform ohne Cookie-Consent lösen, da technisch notwendig.
  14. 2 points
    @Smile I can understand the feeling of @wakabayashi and I suppose some others. What we hope for (i talk only for me but I have the intuition is the same for some others), was not only to tell us if you would continue with TB name or another one new, but what was going to change and what we could we expect from this new path. People has been waiting for these news a lot of months. Now a communicate to tell, TB is going to continue but wait again up to 2 month more to know the details.... The feeling is: ok... I know plans take time, but the plan I suppose (i hope) has been developedduring this time. I suppose, most of the changes and roadmap were not going to be alterate because of the name... why not to communicate them to the people? What is going to be the revenue business model? What is the draft of the roadmap (even if it changes)? is the new image/website has been prepared? when is going to be released?, What about people concerns about 1.6 limited in time compatibility?....
  15. 2 points
    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.
  16. 1 point
    Looks like this commit is the culprit: https://github.com/thirtybees/niara/commit/6abc6b7e555caadb48b02e662ffd8da105a927f8#diff-25beb89b157fe43848421e7b4cf456c7fa1a603879047d3c1e5c636aa5dff62e For some reason the working templates were overwritten with this mess. Probably not an intention. I will revert this commit
  17. 1 point
    Thanks. I will try. Well. I finally got it work.
  18. 1 point
    What I meant with PHP is that module developers might not opt for using templates for some views. Sometimes it makes sense to generate html markup directly from PHP. For example, I've seen markdown interpreter module -- this allowed you to write your product description in markdown language, and the module converted it to html. For that, some php library was used, only customized to inject proper css classes to the output. Bootstrap css classes, mind you. Such module would not work properly on different tech stack, not without rewriting this php customization. With js -- a lot of modules use javascript to construct and replace DOM tree dynamically. In that case, bootstrap classes and building blocks are hardcoded inside javascript code. How hard it would be to rewrite this functionality to work properly with different css framework depends on how similar these frameworks are. For example, bootstrap's rows/columns abstraction are not always available.
  19. 1 point
    No, full page refresh would result in resetting javascript objects -- your selected carrier / payment options, filled in text fields (name, email,....) would be lost.
  20. 1 point
    In the meantime, I contacted Involic and they requested the backend credentials to fix it. To be honest, I didn't expect TB to be supported in my case. I will let you know the outcome.
  21. 1 point
    @datakick thanks for the reply. We've modified Chex a bit, so it doesn't require people to create an account on our website, and we're generally not forcing people to do it in any way, so there are very few clients which have accounts. Moreover, we sell products, which people buy in vast majority only once, therefore the problem with distinguishing between returning and new customers should not happen in our case. Regarding the abovementioned, I would imagine a solution in which Chex mechanically shows all the fields in the default configuration (for the new client, 99%+ in our case) and eventually, after recognizing account, fields are getting changed (it will happen very rarely in our case). The same thing is happening now in the background (as far as I understand), I would just like to show that to the client. Do you see any smart option to implement such a workaround?
  22. 1 point
    Tenés razón, al parecer no puede hacerse... estaba buscando por las dudas en algún foro de prestashop, pero no...
  23. 1 point
    I am sorry for your feelings 😥 You seem to have a lot of fear from the future 🙀
  24. 1 point
    @Mark I am not either agree with the way TB is being managed, but there are more constructives ways to talk and express ideas. And also, sometimes if your/mine/others ideas are not implemented, we need to accept that things are not like we want, and take the decision we think we have to do. There is not more.
  25. 1 point
    If this do work on you I think @Mark has been successful.
  26. 1 point
    I have resolved the issue. I installed the currency update module ECB Exchange, and enabled the US dollar (was disabled in screenshot above). It did not work right away, but the next time I logged in and processed an order the ECB Exchange was next to the US currency line item and the payment processed correctly.
  27. 1 point
    https://github.com/thirtybees/thirtybees/issues/1326 he's alive 😊
  28. 1 point
    The same thing has happened to me. I have no answer yet, but am posting in solidarity.
  29. 1 point
    Solved - I think When I checked the server I noticed that PHP-FHM was disabled. Not sure if i had that enabled or disabled previously. So I think an update over night changed something Anyway, enabled it and all seems to be working - fingers crossed PHP-FHM does not actually introduce any other errors
  30. 1 point
    Hi everyone, I wish to have a watermark module supporting .webp. The current version of the modul (actually migrated from Prestashop) supports only .jpg. The .webp format is getting like a standard and is being supported by almost all web browsers. Google loves it givving web shops with .webp (much) higher ranking. On the other hand, I am in a creative industry, organisations are spending a lot of attention to copyright. Especially in Germany it could be very easier to get a nice email from a lower. So to have a watermark is a must for me. Is it possible to extend the module to support .webp?
  31. 1 point
    bankwire module set order status to the (configurable) value PS_OS_BANKWIRE. Look into the tb_configuration table and check what status id this reference to. https://github.com/thirtybees/bankwire/blob/master/controllers/front/validation.php#L64 select name, value from tb_configuration where name = 'PS_OS_BANKWIRE'; +----------------+-------+ | name | value | +----------------+-------+ | PS_OS_BANKWIRE | 9 | +----------------+-------+
  32. 1 point
    If you already run 1.1.x then there is no big difference to 1.2.0 (of course, depending on what commit exactly your 1.1.x is, but I assume it's recent one) I don't see any reasons why Panda theme shouldn't run on php74, or on thirty bees 1.2.0.
  33. 1 point
    Buenas Tardes YANIV14. Al parecer, al actualizar a TB v1.2 LIMPIO, primera instalación. Todo funciona muy bien!!!! NO se borran los atributos color (excelente!) y NO hay error al editar productos (excelente!) Muchas gracias por la Ultima Actualización !!!
  34. 1 point
    That's a good question 🙂 I guess it was the easiest solution at a time. I agree we should get rid of these third party service dependencies. I filed an enhancement request on github for this one to not forget it
  35. 1 point
    Hard to tell what's wrong. It works for me fine. If you really don't have any core modifications, I suggest you update to latest bleeding edge - 1.1.x using core updater module. Then try again.
  36. 1 point
    I have no problems importing the file. Do you have any modification to the tb? What version of tb are you using? Do you have any overrides for Product?
  37. 1 point
    Carrier delay is stored in the database, it's not dynamic at the moment. I guess we could create new hook that would allow modification of carrier list returned from Cart::simulateCarriersOutput. At the moment, I suggest you to create override of this method, call the parent one and modify it's result. Something like this: public function simulateCarriersOutput(Country $defaultCountry = null, $flush = false) { $carriers = parent::simulateCarriersOutput(defaultCountry, flush); foreach ($carriers as $carrier) { if ($carrier['id_carrier'] === <myID>) { $carrier['delay'] = '<delay_from_webservice>'; } } return $carrier; }
  38. 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!
  39. 1 point
    Thank you for that - I'm fine, have used the above solutions to fix the the problem, I just think it's poor that Niara is still shipping as a "Responsive theme" without proper responsiveness in the shopping cart.
  40. 1 point
    Some idea of a more general nature: I just read through some articles about bootstrap alternatives and stumbled across an interesting article which is targeted at mobiles. I know TB is mobile friendly etc, but how about changing your strategy in general (not that I had any idea of your strategy^^) to deliver a mobile-first application that is made for mobiles but also works great on desktop. We ourselves have already over 50 or 60% mobile users and this number will be going up even more for everyone in the future. So I think design and code wise it should be created with mobile-first thoughts, ideas and strategies in mind and just make it work for desktop afterwards. I believe this to be very future proof and a step before so many others. Maybe what it would need first is just a new theme that is first only created for mobile view, maybe a completely different interface that is most easy to use on a mobile device and then try to adjust that layout to desktop. Or make a theme for desktop (current ones) and one additional for mobile that is lightweight. Codewise I can't say anything about it, I know only little about the full prestashop core, just enough to make some most simple modules myself or make slight core adjustments (which I have actually left behind with prestashop :'D). But maybe it's possible to not use the full extent of the code when a mobile is recognized to make it more lightweight, no idea 🙂 Just something to keep in mind I guess, mobiles will be the top devices for viewing websites, they ofc already are. Thought of sharing that as I have to get used to the mobile first fact myself, I always forget about these tiny devices and love visiting websites much more on desktops myself, yet there are other people out there and they tend to do the opposite :'D
  41. 1 point
    there is a lot of code waiting months to be merged. I hoped that after take over github will be flooded with commits, but last one was 4 months ago.
  42. 1 point
    for export there is the datakick module. But easy import from csv would be nice
  43. 1 point
    I would stay away from Siteground, I had endless problems with them.. They have awful limits and my 1 script which updates google shopping was a nightmare. I do how ever wish I had gone over to A2 rather than who I am with now
  44. 1 point
    I was thinking more Tb specific actions. Already got EORI as we are VAT registered, Our carriers Royal Mail and parcelforce automatically print CN22’s and CN23’s as necessary. Again, we already add harmonisation codes where relevant as we do sell globally. Consumer or B2B does not matter they will still have to pay VAT in whatever country they are in (though there may be a lower threadshold of 22 euro before that kicks in). You can also send Duty Paid but that would not work for us
  45. 1 point
    Don't know of any module but that must be possible to track with stock movement and a sql-script.
  46. 1 point
    well he was asking about OPC so a gave my answer, i bought chex too, and im not using it too (unable to aply changes - and make search not working for us..) 😄
  47. 1 point
    data inconsistency in database. You can download my consistency check module, that might help you fix it
  48. 1 point
    Theme exporter got a lot better with thirty bees 1.1.0, but it's not perfect yet. There are a few bits missing in the theme configuration. Easiest way to duplicate a theme is to duplicate its directory with all its content, then editing its config file to change 'directory' and 'name'. That done, the duplicated theme can get installed, it shows up in the list. And yes, installing themes on disk was broken before 1.1.0, they simply wouldn't show up in the list of installable themes.
  49. 1 point
    Sorry. Already found it by myself. There is a new (when comparing to the Smartblog module I used in PS) selection box that has to be ticked for each post: the available language box. If ticked, the posts show up!
  50. 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...