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 03/05/2020 in all areas

  1. 6 points
    UPDATED May 10. Theme file added for download Github link with latest changes. https://github.com/toplakd/thirtybees-modifications community-theme-modded.zip
  2. 6 points
    @rubben1985 gave me access to his back office, so I had a look at the issue. Indeed there was some weird stuff going on. For example, cache was not flushed when you clicked on Clear cache in Performance tab. My investigation showed that this problem was caused by missing /cache/smarty/cache directory. Recreating this directory using ftp seems to fix the issue (pending confirmation from @rubben1985) Thirtybees codebase never checked existence of this directory, so this issue is hardly 1.1.x injection. But it's an issue nevertheless -- the system should recover from this situation. The fix is already committed in bleeding edge
  3. 6 points
    I uploaded a new Prestools version: 1.24n. It contains a new version of the image plugin too. The new version fixes a few issues with image edit: - you could not add an image to a product that didn't have any images. - when you marked a newly added image as cover it wasn't registered as such. As a consequence the product ended with no cover and you didn't see an image in the backoffice product list. - when you made the image field editable and the cover image was not the first one it displayed on the first position the cover image too. The editing is now more wysiwig as it makes that you to always have an active cover product. If you find any more problems please let me know.
  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. 5 points
    These recommendations were discussed many times on the forum, for example this flame from two years ago. Unfortunately, not much was done in the last two years, other than code implementation. Stable and nice codebase is important, of course, but it's not what will attract users. When I look at the last two years, I see a lot of wasted opportunities. There should have been massive campaign to attract ps16 merchants when support for their platform was ending. There was none. Third party developers with ps16 modules should have been contacted, and some incentive should have been offered to them in return for maintaining their modules compatible. For example, their modules could have been highlighted in the 'modules' page in your back offices. Again, this didn't happen. And since then, most of these developers either completely migrated to ps17 platform, or quit the presta-world completely. And there are so many other things that could have been done. Instead, the platform stagnated. The only area that was worked on was codebase. And that just not enough. Two years ago, I wrote: I wonder how accurate builtwith.com data are - they track ~576 sites Now, this web tool tells us there are 509 active thirtybees sites. These two years should have been the best time for attracting new users. Instead, we lost some. This inactivity is what drove my decision to quit. I have no problems working for free on an open source platform. I have problems seeing this work being wasted. If the situation changes I might revert my decision. But I don't see how it could change, unfortunately. Also - I don't want to 'take over', as some of you suggested. While I'm flattered, I don't want to do that. I would really hate doing all those things that I've just complained above. I'd be terrible at that, I'm sure.
  6. 5 points
    I did some investigation, and this area is pretty fuc*ed up. There is a column total_paid_real in order table that tracks how much money was actually paid. This column has been deprecated for a very long time, because this information is primarily stored inside tb_order_payment table. However, for backwards compatibility reasons, this column is still there, and thirtybees tries to keep it in sync with records in tb_order_payment table. Needless to say, it does this very poorly. The issue I've mentioned in my previous post is just one problem. There are others, for example currency issues. Some code expects this column to be in shop currency, other code expects it to be in order currency, and this can lead to totally wrong amounts (apples and oranges added together) We need to fix this. The first item is to remove all *read* usages of this column from core. Core code should always use data retrieved from tb_order_payment, and not use this deprecated column at all. Then, we should fix all *write* usages, so modules that depends on this column continues to work. Unfortunately, even with all of these, we will still have consistency issues, only not so frequently. It's just not really possible to keep things in sync. For this, we should have some scheduled task that automatically fix the data. https://github.com/thirtybees/thirtybees/issues/1161
  7. 4 points
    I am generally very open about things with our community. Some people might not like the answers I have given at any given time, but I have always tried to be forthright with them. I am unsure where you recent hostility against me or thirty bees has come from. You contacted me last year about partnering on a project roll out. You asked several different questions / opinions and I told you what I thought. You mentioned you might want to invest in thirty bees, but never anything past that, until you contacted me a week or two ago just to tell me to fuck off basically. You were mad because your bug reports were not handled satisfactory. Here is the last conversation for the people reading and wondering. But yes, I am up for whatever works, as long as it works for our mission and our community. I am not up for scaling module prices based on how much business a shop is doing. I am not for selling code that thirty bees produces. From the start of this company / project those have been the values. I might not be capable of piloting the company or project much longer, but I am not going to turn it over to someone that will exploit the community. These people have been awesome to me and thirty bees over the last several years and I am trying my best to leave them in capable hands with my integrity intact.
  8. 4 points
    @datakick I was going to write you in private but I think this community deserves to give their opinion but also to know what others think too. I honestly think that you (and the rest of the actual actives contributors), should "take the the helm" and create the new staff. Without all of you (and specially you in the last months) there is not TB because community is great but we need someone more involved than standard merchants. Community growth around a solid core. I can understand Lesley is ill and we hope he will recover soon, but it is also true that we are in a professional environment and any project needs a leader. Why not you? You have been the leader anyway this last period. It can be at TB or a TB fork if necessary. I am not developer, but I am quite decent in management and marketing (that was always the biggest problem for TB growth). I would gladly give my inputs (there are so many easy things to fix in the communication and branding...), even collaborate with designers from my team for free. Not talking about intensive work, but more that testimonial, for sure. If you think about the possibility, I think could be an inflexion point in TB history
  9. 3 points
    Thanks for the support and contributios @zen Looking forward to an exciting future together 😀
  10. 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.
  11. 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.
  12. 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.
  13. 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?....
  14. 2 points
    Thanks so much for this. It worked. pb4sc
  15. 2 points
    No, it would not. It would be a huge step back - from seo perspective, from accessibility perspective,... Alt tags are very useful. If you really need them go away, you will have to edit your theme and remove them.
  16. 2 points
    As far as I know he is not. And the deal being worked out is no where around those numbers.
  17. 2 points
    Hi all, we have some news on the future of Thirty Bees! https://forum.thirtybees.com/topic/4194-thirty-bees-future-announcement/
  18. 2 points
    @datakick New Bug with TB 1.1.x and Panda: Got a strange new bug after I updated my 1.1.0 site with Panda to latest TB Bleeding edge: On Product list / Category page: For some reason the Left Column disappears when a Sub Category is selected. Main Categories are fine. I noticed that the var left_column_size is set to 0 instead of 3. Weird, as this worked before the update. Because I know the Left Column should always show on the Category page, I've created the following to 'fix' it, albeit temporarily. And obviously this isn't a real fix, as it doesn't address the cause. Just helps for now. <!-- /// No Left Column on Subcategory Fix /// --> {if $page_name == "category" && $left_column_size == 0} {assign var='left_column_size' value = 3} {/if} <!-- /// *** *** /// ---> Insert the code before: {if isset($left_column_size) && !empty($left_column_size)} Thought I'd point this out. I have notified @Jonny as well.
  19. 2 points
    @Traumflug There is also another thing. There are not many people wanting for TB to rise for one simple reason: Having to maintain compatibility for 2 shops. A lot of devs dream of 1.6 being put to rest (yes, they also hate Prestashop 1.6), as 1.7 takes over. Maintaining backward compatibility with 1.6 (and/or TB) is additional work. So basically it's not personally aimed at TB or you guys, it's aimed at lowering costs and maximizing income. Because of state of 1.7 I'm seriously thinking about changing my business model. I don't want to be held responsible by my clients for bugs in 1.7. Still, my clients I migrated to TB expect FROM ME modules for prestashop to work or fix them. Their mentality is like: "If I had Prestashop, it would surely work". So either I go on war with them or comply with their insane requests. It's a shame, but this brings a lot of regret to devs like you and me. PS: Also, when I recommend thirtybees and explain all differences, I'm being held responsible for recommending it to clients. Some people are insane, and blaming their decisions on others. And saying "Prestashop would be better". That's where "brand" part comes in.
  20. 2 points
    OK.. so since january 2nd we have NO news from Him.. what to do ? Where are you going Datakick.. may I follow you ? LOL more seriously.. let's start or continue with a fork of TB with people really motivated, why not ?
  21. 2 points
    https://github.com/seigieu/watermark/tree/thirtybees Here is version of PS 1.6 watermark module that also generates webp images. Also, thank @Smile for this 🙂
  22. 2 points
    @Chandra you are mixing two things. The settings on Order Statuses has impact on 'Order Status Changed' email only (ie. Awaiting bank wire email) What you are talking about is the 'Order confirmation' email, and that has nothing to do with order status. This email is always sent, and it contains all current information available. I guess we could change the current semantics, and attach invoice to 'Order confirmation' email only if current order status has the send invoice checkbox enabled. However, I'm sure there would be plenty of merchants that would not want this behaviour by default.
  23. 2 points
    For hunting down small bugs (or my mistakes) I always have 3 installation of thirty bees on the server. All latest bleeding edge One is live, one is exact copy of live shop for testing, and 3rd is always the clean stock thirty bees installation. So if something does not work on live but it works on stock install, i can compare testing shop with clean stock, and make adjustments or fixes until it works 100% like stock. Only after that, I apply it to the real live shop.
  24. 2 points
    Hi. Yeah, but you don't need Warehouse 😀 Thankfully, one of the best and insanely feature rich and customisable PS themes, Panda, has been updated for TB and is actively maintained by the Theme developer @Jonny Which is great and it gives you the "AAA" quality theme that you need for TB that is actively maintained and updated.
  25. 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.
  26. 1 point
    I think you also should consider to make the theme heavy configurable like many of the paid successful themes like Transformer and Warehouse. I know @zen started to make a module or something earlier. Maybe he can be a part of the collaboration.
  27. 1 point
    Gerade ist mir die Ankündigung auf der Bundespressekonferenz über den Weg gelaufen, ab Minute 1:50: https://www.jungundnaiv.de/2020/09/02/bundesregierung-fuer-desinteressierte-bpk-vom-2-september-2020/ Da werden unter anderem einige Änderungen im Steuerrecht vorgestellt, 2 Minuten lang. Darunter die Änderung, dass Plattformbetreiber in Zukunft für die Mehrwertsteuer haften, nicht mehr der tatsächliche Verkäufer. Das dürfte wohl für Shops eine Änderung bedeuten, die als Vermittlerplattform agieren, z.B. Amazon. Auch eine Änderung bezüglich der Steuererklärung. Die müsse man nicht mehr in jedem EU-Land einzeln erklären, sondern könne das alles in Deutschland machen. Allerdings war mir bislang keine Pflicht bewusst, in Frankreich, Polen oder Spanien Steuern zu erklären.
  28. 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
  29. 1 point
    Het hamburgermenu is hetzelfde als het standaard menu in de desktop versie. Het wil nog wel eens gebeuren dat mensen een speciaal menu hebben en dan het standaard menu leeghalen.
  30. 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..) 😄
  31. 1 point
    data inconsistency in database. You can download my consistency check module, that might help you fix it
  32. 1 point
  33. 1 point
    sure just add another carrier named PICK UP ONLY and as delivery lenght put adress or so then in product settings allow only this one carrier
  34. 1 point
    It was forked from the 1.6.1 branch, 1.6.1.12 to be exact.
  35. 1 point
    Haggling: Seller: I want 10 x income and a farm! Buyer: I'll give you 10 x income and a potato. Seller: [something bullish] Buyer: Talk next month then; see if you can find a better offfer
  36. 1 point
    Das ist kein Fehler, sondern völlig richtig so. Da braucht man auch nichts "reaktivieren". Steigt die Mehrwertsteuer wieder, wird der Steuersatz erneut kopiert, alles ist prima. Keinerlei Grund, in der Datenbank herum zu fummeln.
  37. 1 point
    Who is chasing? Who says you have to be?
  38. 1 point
    Once again, I will answer myself, because may help others resolving own issues: in my case, I just uninstall the module and install it again. worked like a charm.
  39. 1 point
    Turns out the original problem with the missing checkboxes in group restrictions was due to a corrupted database. I copied the database from a similiar store we have that worked edited it for the problem store and when attached the the new database and the check boxes appeared. As for the custom payment module Toplakd's solution worked:-) Thanks Dejan!
  40. 1 point
    When you have tracking number from any carrier, just go to its site and enter the tracking number. If their system shows the number also in their http://nameyour.mail.com/somethingTRACKINGNRsomethingxyz than copy that url to your Carrier "Carrier Settings / tracking url" and replace TRACKINGNR with @ so it will look like this: http://nameyour.mail.com/something@somethingxyz Then everytime you add tracking nr to the order the customer will get the link which will open the tracking directly on carriers website.
  41. 1 point
    Do you see Edit button on the right? Try clicking on it. 🙂
  42. 1 point
    To add a technical datapoint: page caching of any kind can only cache the HTML part of the page, the initial page load. That's where all the PHP voodoo gets executed. All the stuff after that initial page load, CSS, JS, images, whatever, isn't subject to page caching, no matter how it's configured. And one can easily measure how long this initial page load takes. Instrument #1: use Curl on the command line. Like: time curl https://librairiezbookstore.com/ Instrument #2: browser's developer console. Open it, click on the 'Networking' tab, then reload the page. This generates a list of all the resources loaded, look at the very first one. It should report loading time. With both instruments I get between 540 milliseconds and 590 Milliseconds on librairiezbookstore.com. That's what one can gain. Very good setups take like 350 milliseconds, so even the best imaginable page caching could never improve page loading performance by more than 0.2 seconds. If one sees more improvements for the complete page load, it's the result of content no longer displaying.
  43. 1 point
    Mobile experience is not good on any of thirty bees default theme. For good mobile view a lot of things have to be changed. Mostly css styling for different media widths ... Once done it can look similar to this picture
  44. 1 point
    Surely this could be implemented without core files modification. - The changes to ProductController are fine (from backwards compatibility point of view), as it's just addition. However, I think it's not necessary, as there is already a functionality that saves the customization -- we could simply call this existing one using ajax. - The change to tools.js is more severe, as it might impact other themes that does not implement this 'auto save' functionality. I'm sure we could maintain the original tools.js, and add some more preparation inside theme-specific ajax-cart.js If we could do that, than this would be theme-only change, with no side effects or compatibility problems
  45. 1 point
    This is a JavaScript issue. JavaScript is used for display during editing. After a round-trip to the server ('saving') everything is fine.
  46. 1 point
    additional: there was a discussion some time ago 'to have a field in BO in each product' for 'essential product features' and merchant can use it or not (also here in this forum). A lot of merchants will prefer such a thing, but there was no reaction from PS and also not from tb. If they will not use it in shopping cart, then maybe for other things. It's just to have an separate field for such details and maybe shop developer should have an ear for these things, then 1. required laws can be covered and 2. this is maybe an additional nice to have other shopsystems dont have... not only for this German regulation.
  47. 1 point
    you need to go there, and turn on (green check) the left column on Index
  48. 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.
  49. 1 point
    @ssimard you can override module core files, see this http://nemops.com/override-prestashop-modules-core/
  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...