Jump to content
thirty bees forum

Leaderboard

Popular Content

Showing content with the highest reputation since 09/09/2025 in all areas

  1. did you check size of database tables? if there was no cleaning made, you can be surprised how much data is stored there, and some of the tables can have huge impact on BO speed.
    3 points
  2. I use the Mollie module v 4.5.4. on TB 1.6.0 with php 8.0
    1 point
  3. You should go to the performance tab and switch profiling on. Then refresh the slow backoffice page and scroll down. There you will have the information what is loading slowly. You can also post a screenshot here, if you have difficulties to interpretate the information. IMPORTANT: after quick test you need to deactivate this setting asap. Cause this profiling information is also loading in your FrontOffice shop. So your customer would see it as well.
    1 point
  4. many people believe the that is not longer needed. Its a mistake to fall into that. There are other search engines not only Google.
    1 point
  5. It might be configured under the Admin -> Customer -> Customer Services (Bottom of the page). It's basically to create the ticket directly from the email.
    1 point
  6. I am creating a new thirtybees site. As am adding categories it is not displaying the images for subcategories. On inspection it is calling for 2x images for those, "Generate High Resolution Images" is not clicked and none of the other images are asking for 2x. What do I need to do to fix this? Thank you. Never mind - It was a browser cache problem. I had cleared the cache on the server, but not my local machine. Feeling foolish...
    1 point
  7. maybe you can try to manually run Category::regenerateEntireNtree()
    1 point
  8. @the.rampage.rado I'm now using this on my live site and all is well. Thanks again!
    1 point
  9. 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
    1 point
×
×
  • Create New...