Jump to content
thirty bees forum

the.rampage.rado

Silver member
  • Posts

    1,061
  • Joined

  • Last visited

  • Days Won

    80

Everything posted by the.rampage.rado

  1. When you updated the file format was probably emtpy: You will have to select one of them (they are all supported by Niara (recent versions of the theme)). Then save. Then you will have to reset your indexation status for all types and regenerate all types: Clear cache and check if they show up on both places.
  2. Since 1.5.1 there is a huge image section rewrite, nearly everything regarding to images is redone so you will have to give little bit more details - where they disappeared, what theme are you using, little something to work with... Regarding the duplication issues - you can go to github and search for commits that mention product duplication issues and apply the fixes manually to your install if you're not planning to rolling back to edge soon.
  3. bleeding edge channel is 99.9% production ready as datakick makes the commits there and everything is tested before. So if it is the only issue you have with it you can backup your store and try. I only roll my shops on bleeding.
  4. For the social icons - uninstall the sharing module: The print link has to be deleted/commented in product.tpl in your theme. Regarding the stock counter - probably the same as above as I don't see where to configure this in Niara/Community theme (if you use one of those). Some themes have this as a switch.
  5. @datakick can you reproduce the following steps? 1. Install native thirty bees layered module in multistore. 2. During installation all indexes are obviously build and table XXX_layered_product_attribute is populated correctly with all combinations for all shops 3. Rebuild attribute index with the button. Expected result: 1. XXX_layered_product_attribute should contain all combinations for all shops (depending on association of course). Current result with edge test installation: 1. XXX_layered_product_attribute contain only combinations for shop id 1. This is with the native thirty bees and uninstalled the modded module from above (which uses the same table names) in my test instance where I have only 2 shops. If I click on the button I have to reinstall the module to reindex and never touch this button. All other buttons seem to work correctly (or at least they don't mess anything I can see).
  6. Hi guys/gals, if somebody can give an idea it will be greatly appreciated. I run multistore installation and I have 6 shops. Everything was working OK until recently - all products were displayed properly using the LNM filters in all shops. I'm sure because I did lot of work with the color filter in the additional shops where I added many clothing items and all of them have color combinations. Yesterday I noticed that only the color filter does not display in all non default shops. Then I saw that this applies for size too (generally all attribute filters, only the feature filters are visible in the addon shops). Here are the things I tried: - reindex all LNM indexes - reinstall the module - I had filter templates based on each shop - the issue presented with this setup. Then I removed them and made new template for all shops and all categories - no bueno. - in despair tried changing the button type of the color filter - as expected no effect 🙂 - checked all shop associations - in attributes (group and each attribute), in LNM - everything is associated with every shop. - tried regenerating the indexes in all shops context and in each one context - no affect (even not sure if LNM cares about this). When reindexing I noticed that the price index takes much longer than the attribute index and this led me to check the code and then the db. This is where I think I have some issue. In table XXX_layered_product_attribute I only have records with shop id 1. Because I use the modded version of the module that was part once of PS1.6.1.24 and comes with Warehouse theme I use I compared the indexAttribute function and they are 1:1 with the most current TB version of the module. XXX_layered_price_index has all shop ids. Any input will be greatly appreciated! Am I missing something? As this is my production instance and I can't replicate this issue on my test setup I am unable to test with TB native module currently. TB version: edge as of today
  7. There's a similar error recently here: datakick recommended to update to 1.5.1 and check if this error continues. You don't have to reindex after every new product for sure.
  8. If it was a module/core issue everybody would have this. 😕
  9. You'll have to install module Block Categories. By default TB (and PS in that matter) does not show categories to a set place. You can configure this module and place it where you want (left/right column, etc.) Same with Top menu - it does not automatically display categories if you don't configure it to do so.
  10. @datakick today I decided to check this module and it was showing this: (note: all images are there when I check them and all of them were uploaded after the image rewrite update). Can you replicate this or I messed something up again on my local setup? 🙂
  11. There is no need to migrate your shop. Core updater takes care of your files and db (if you think there are corrupted ones, etc.) You have to check what is causing this issue. Check if your shop is configured to run on the server php version (in Core updater -> Settings set 'server version' and update channel to Stable). Then check if you have some changed files when you compare your install to 1.4 in the module. Also if you don't have (as you don't know what this is) it is VITAL for debugging to have this module installed at all times: It collects nearly all errors, notices, warnings, etc. your shop produce so you can solve them. Nobody can help if there is no additional information on the core issue.
  12. I bet on some server issue. In any case this generic information is not enough to troubleshoot. Is there anything in your Error log module?
  13. You can update to edge (simplest) or update your files as follows: https://github.com/thirtybees/thirtybees/commit/e89c365731d095d971038d21d2e0310833e469b9 Regarding the discovered pages in the Search Console - I'm curious if they can be removed or should we leave them as is?
  14. 1. It's a known bug, some other parts are not duplicated also. 2. Are you copying products that have Specific price rules attached to them?
  15. I can't help for the PP issue but couple of notes: 1. Don't run your on Force compilation, this makes it slow. Run it on 'Recompile templates if the files have been updated' which is the golden standard in terms of speed and trouble-free operation. 2. After the recent image rewrite there are many new things going on in Images. You have to go to Images section, choose what format you want to use (best are webp and avif (if you are on php8.1 or later), select your quality (90 for best quality, 70 for good balance or less for speedy shop but lower quality images - see this post from datakick - https://forum.thirtybees.com/topic/6608-image-format-webp-vs-avif/#comment-49265 ). Then reset (reset, not delete!) your tumbnails and regenerate all of them. Don't close this page until the process complete. Then you will have to clear your cache and you should see all your images back online with no issues. If not - hard refresh the page in your browser (ctrl + F5 on win). 3. Regenerate your htaccess through SEO & URLs - switch Friendly URLs off, save and then back on and save.
  16. If your theme was compatible with PS1.6 this most probably means it will not work straight away on php8.2 If you switch Niara and test that your setup works on this server then you can switch to your theme and troubleshoot it. I bet block cart is not working (the files that come with your theme for this module).
  17. This appears like a server issue. Take a look here, something might help: https://stackoverflow.com/questions/38796807/smtp-error-550-sender-is-not-allowed https://www.hmailserver.com/forum/viewtopic.php?t=29135 Check if your 'from' email matches the real email that is used.
  18. In order to fix the first two errors - go to Advanced -> Performance and scroll down to CIPHERING. Currently you probably are on PHP Encryption since your last update. But there was a bug with the settings for this encryption (prior to tb) and the settings were not correctly applied. Switch to blowfish and save. Then switch back to PHP Encryption and save. This should populate the needed value in your DB and make those Warnings stop. You can delete those 2mln rows in Error logs module. In regards to your email troubles - have you configured one of the two email transport modules?
  19. Here is the fix for Community theme: https://github.com/thirtybees/community-theme-default/commit/b6584976b52d8e6a818fc031b621c554bdf9fdf5 It is recommended to update to at least 1.5.1 as soon as you can because there are other security fixes between 1.4 and 1.5.1, this time in the core.
  20. You can try https://github.com/tagconcierge/tc-prestashop-gtm-consent-mode-banner-free I'm using it. The only drawback is that is not multilingual but if you have a 2+ lang site you can use their paid module. I downloaded the js files and modified the code to work locally and everything in Google is OK so far.
  21. Exactly what I was going to say. The majority of users here don't know about Phoenix so probably first hand experience won't be shared. Instead I would like to guide you to the last 2 major release threads so you can check how much quality work has been done by the TB team in the last 2 years: version 1.5 version 1.4 And there are tons of new features, bugs and security fixes since. Regarding PhoenixSuite, yes, eolia is doing some fantastic job too. It's really a shame that those project are diverting away in every new release and he does not join the TB team with his knowledge.
  22. Recently I started playing with the embedded SQL manager to make queries that are useful in shop maintanance. I noticed that my products contain information for language ids that are not currently installed (or active). I can't remember if I used to have additional languages in this shop instance before. Currently I have: But this query: SELECT pl.id_product, pl.id_lang, pl.description_short, LENGTH(pl.description_short) as short_description_length FROM tb_product_lang pl WHERE LENGTH(pl.description_short) < 50; pulls the following table: My question is: as I don't have lang ID 3 and 5 could I safely delete all those records (and also every other record, even if larger than 50 characters) for those IDs? Could I use this query for doing so: DELETE pl FROM tb_product_lang pl LEFT JOIN tb_lang l ON pl.id_lang = l.id_lang WHERE l.active = 0 OR l.id_lang IS NULL; If I understand it correctly even if I had let's say Spanish as ID=3 and I remove it and I add it again it will get the next unused langID, not return to 3? In this case why deleting the language is also not deleting all records associated with this ID (products, image descriptions, features, etc.)?
  23. I would like to moderate/remove your message as it's your first here and it contained some bold claims about a company, and nobody here would have time to discuss with their lawyers, etc. For future reference if you wish to be part of this community please keep in mind that you can express your opinions freely, but not as anonymous user that just registered here just to say some 'nice' words against a person/entity. Best regards!
  24. And you have to uninstall the UA module as you will not need it that way.
  25. Thanks for the hint but a merchant permission is vital for this list.
×
×
  • Create New...