Jump to content
thirty bees forum

the.rampage.rado

Silver member
  • Posts

    1,183
  • Joined

  • Last visited

  • Days Won

    100

Everything posted by the.rampage.rado

  1. Same. A user can purchase 'as guest' numerous times with exactly the same details. They enter the same information. What is bothering you, do you think there's something obstructing them to complete the order?
  2. If the first one is a guest order and during the second one he/she made an account this happens. "New account' for the user type. All details might be the same.
  3. Go to Advanced -> Logs and upload this file at the end of the page. It should decode it and give you the error. Probably some module is not compatible with your current TB version. Any recent changes in TB or your modules?
  4. Yet, again, you can use a google font locally. There are plenty of tools that assist in the code and the process. I do so on each on my stores.
  5. I don't believe I understand quite what you say but... :) I use webp from the second day TB introduced it in the core and I don't know how Google will prohibit you from using this free file format :)
  6. What do you mean 3rd party? Like CDN? All webp images are generated, controlled and served locally. But im south of the Danube, so it might be different :P
  7. This is not a bug. If you have small image why should you enlarge it and present a blurry mess to the customer. If you want higher res image - just start with one if such is available. The system will shrink everything down to your images settings but will not enlarge smaller images. EDIT: Regarding webp - your theme should support it. Go to your theme's config.xml and try to enter <webp>1</webp> <webp>1</webp> just at the end. Then go to Images, enable the now visible webp setting. Regenerate your images, wait until the regeneration is done then clear your cache and check if your front end displays them correctly. MAKE A WORKING BACKUP BEFORE THAT, most themes work but some badly coded ones might ask for jpg! About lazy loading this setting is heavily dependant on your theme and is not set in Images but in your theme configurator (if such support is present). If there is no such setting you might try to use some module but I can not recommend a viable solution as my theme have it embeded.
  8. Try this: https://github.com/thirtybees/thirtybees/commit/136017aedcbf46f708b31df96ea2c11fd8acecf3 This fix is part of 1.5 but you could try it, just keep a backup of the original file.
  9. You definetly should not stick to 1.3. What is your current php version? After 1.3 you should switch to 1.4 then switch to php 7.4 and update to edge. Currently edge is compatible with php8 but you should be careful around your installed 3rd party modules with php 7.4 and 8. Step by step and with our help you should be able to update it to the latest version. Just always keep a backup of your files and your DB on each step so you can revert back. Reasons to update to edge: - code optimization for modern php versions - speed and compatibility imrpovements - bugfixes - at least 10 security fixes since 1.4 - new features
  10. So you're open to loosing orders if users don't have gmail or yahoo mails instead of once in maybe 25 times you have a user with wrong email?
  11. Do you have a list of all registered domains everywhere in the world?
  12. You can remove all categories thumbnails. I would not modify core or theme files because after an update of those the changes are gone and have to be redone.
  13. So you solved it? If so, please write how so we keep it as resource!
  14. Single or multishop?
  15. How did you manage to achieve that? 🙂 Try this free module: https://store.getdatakick.com/en/modules/consistency
  16. 1. Could you describe what glitches you observe? I believe I have nothing like that. 2. This might be treated as duplicate content by google if you have /en/product1 and /jp/product1 exactly with same desc, title, etc.? 4. Oh, yes, my bad. I was refering to the min quantity. :) :/
  17. 1 and 4 are available currently to TB and 3 I believe is anti-customer practice. 2 is available for names of products but not other fields.
  18. This is my setup as of yesterday when I installed the module, no changes and this is the default status I receive when a bank wire order is placed:
  19. Same issue here. I use Cyrillic and long thought that this is the issue but obviously this is the same for all users. When I paste the composite link generated by the layered navigation or I put it as a target link for banner, slider, link it get's truncated. I would like to show different preselected options like sizes, gender, etc., but no bueno. Any hints? EDIT - related to my previous question, @Traumflug suggested a fix but it does not work for me regarding manufacturer checkbox, only for slider and size - https://github.com/thirtybees/community-theme-default/commit/c7c317123325aacf6096296d4b06b735adf8eb06.
  20. Yes, but you could disable it only when you edit this CMS page then reenable it? TinyMCE is driving me nuts, on each save it puts more and more blank paragraphs...
  21. Do you have this turned on? Yes, I'll move it there. Thanks for the suggestion!
  22. Yes, attribute class that was changed in order to continue to php8 might refuse to play nicely with this module. You tried but it's not working, right?
  23. Here's a simple and short guide to make a simple accordion style FAQ section using HMTL5 and few rows of CSS. Not the perfect solution but a workaround for those waiting to find it. https://www.stechies.com/create-accordion-html-without-javascript/ I combined it with section headers using h2 as title for the sections and it looks pretty fine. It's a simple list, but it's working on all modern browsers and very easy to implement. Adaptation: Put the custom CSS in Thirtybees' Custom Code section or your theme's custom CSS code field (Warehouse has one). If you have a theme solution go with it, as it will combine the custom rules with the main css file and not embed them in the html. Adjust to your liking. details { border: 1px solid #d4d4d4; padding: .75em .75em 0; margin-top: 10px; box-shadow:0 0 20px #d4d4d4; } summary { font-weight: bold; margin: -.75em -.75em 0; padding: .75em; background-color: #5f75a4; color: #fff; } details[open] { padding: .75em; border-bottom: 1px solid #d4d4d4; } details[open] summary { border-bottom: 1px solid #d4d4d4; margin-bottom: 10px; } Open a text editor as Notepad++ and format your html code for your CMS page there. Every Q&A is a separate <details></details> tag. When you're done with your code go to tinymce's source code editor and paste your code. Using the usual WYSIWYG editor does not work (you can edit the text after you imported the source but you can't make the element). EDIT: HTML purifier might have to be disabled in order to save this correctly in TinyMCE, but if you don't make daily changes in this page this could enabled after the page is complete. The only fault is that this workaround is not using .js and when you open new question, the already opened one does not close. But for its simplicity and robustness it's a solid solution for me, no bootstrap shenanigans, etc. <details> <summary>Question 1</summary> Answer 1 </details> <details> <summary>Question 2</summary> Answer 2 </details>
  24. 1.4 should work on php7.4 but push some notices. When you update to 1.4 you could try and update to 1.5 edge on 7.4, this will clear almost all core notices but you'll have to fix any theme/external module ones in order to proceed to php8. I had an issue with cart module tpl files in Warehouse theme, they are fixed now but I'm still not updating to php8.
  25. There should be no breaking changes regarding the theme when updating from 1.4 to 1.5 edge and soon to 1.5 final. There are some inner working 'fixes': Mailer functionality was extracted from core and you should duplicate your settings in one of two new mailer modules Code minification also was extracted from core and you should install the new code minification module (no adjustments needed here), all settings continue to be in Performance tab. You should uninstall tbupdater (not core updater, it should stay), now it's not needed as the module update mechanism was changed and moved to core. Other than that - plenty of performance, security and futureproofing changes that I'm sure you will enjoy. Keep an eye in your error collection module - you might have few notices there but there should be no exceptions.
×
×
  • Create New...