Jump to content
thirty bees forum

wakabayashi

Silver member
  • Posts

    2,011
  • Joined

  • Last visited

  • Days Won

    168

Everything posted by wakabayashi

  1. @Domas search in file AdminOrdersController.php for the function "getProducts($order)" And try to add this before the return: array_multisort( array_column($products, "reference"), SORT_ASC, $products ); If it works, I would suggest to make an override afterwards...
  2. @piet thats probably not what he is lookin for. I believe he is talking about the BO. There you would need to change a controller, I guess. Maybe a tpl file could also work.
  3. @gandalf @gonssal I haven't thought in detail about it, but I would probably go the same way.
  4. Thx a lot! I will soon try it out :)
  5. I don't think you need to change anything then. Or do you have any issues?
  6. You still us ps? :S
  7. @nickon said in GitUpdater preview: This is a feature I always whished for. Especially the downgrade part. I would like a checkbox so I would be able to uncheck a specific file I don't want to update. (all files checked by default) I don't know how database changes are handled though. This is something I always wanted for tb. To be stable and add features missing in 1.6 Keep up the great work. This is an intersting idea. But I guess, it can also make troubles. Imagine a new function is added to a file, which you don't update. Once this new function is called, your shop will throw an error. But of course I see your point. Especially for theme files, it could be helpful.
  8. Maybe its related to this issue? https://github.com/thirtybees/thirtybees/issues/792
  9. Damn thats bad... Maybe somebody else can confirm the issue?
  10. I just don't think its a core issue, since we dont have it and @30knees also not. I would try two things: - disable overrides - do the same tests on a clean tb installation
  11. @30knees just refresh the page and it looks normal again...
  12. @30knees I can confirm, that this sometimes happens. I don't know exactly when...
  13. Do you have some overrides? Cause in general this is working for me...
  14. I use asm, so I cant tell. What is normal: the shipping cost never adjust! I would like to have it, but its not there...
  15. Is there any error? to me the src looks not very normal. but not sure if it's really an issue.
  16. Oh I just tried to install this module on my testsite. It doesn't even install for me correctly... Didn't expect that :O
  17. What do you mean with a floating social share? Can you show an example?
  18. Happy New Year guys!
  19. I think it could be some bots or something... @lesley knows surely better. What I can say: I have entries in Google Analytics from urls I also don't have at all...
  20. @CoffeeGuy I was just on your site and clicked a bit around. I got no error at all. Seems to work good. Hopefully "Swiss Miss Hot Chocolate" tastes as good as it sounds :D
  21. @Purity you are right, sorry! I haven't read the whole thread carefully. But on his site is still elasticsearch...
  22. @Purity he is using elasticsearch and you are probably (?) using the normal search. But his reaction is not legitimate: 1. lesley offered help, but he doesn't want to give access 2. he is using elasticsearch, which needs quite a bit of knowledge to handle it. 3. he "threats" to go back to ps. after all since when does ps offer elasticsearch?
  23. Lesley is ofc right. The hook called "displayHeader" is not really visual stuff. It's the part, which will be in html between tags.
  24. @movieseals these are just notices. Are you sure your shop was running in debug mode, when you used 1.0.7? Maybe the difference is just, that you switched debug mode on...
  25. @purity said in thirty bees getting better and better: release 1.0.8: Not sure why this needs said again, but if you are updating your shop, you should take a backup and/or test the update on a non-live copy of your site. There should never be a time where you update your site and then need to frantically ask for help to get your site back up. If you have problems, you should simply roll back and await a fix. You're liable to run into such problems updating even a CMS like WordPress... Completly agree. But was too tired to write, since it was said like 1000 times before...
×
×
  • Create New...