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. As said before - before migration you should turn off all external modules and disable all overrides. Then migrate, then update according to your list (you can update all internal modules at once, no need to be one by one), then turn back on your external modules one by one and observe for problems (blank screen, issues in FO and BO, functionality issues) and then introduce your overrides (if needed with TB). I think updating in 7.3 should not be an issue (for PS and TB core) but you may encounter issues with modules that are old. Regarding your restored shop - try clearing all internal caches, the host cache (if present) and your browser cache and check if it solves the problem with the tabs. If you backed up all files by FTP and db is OK this should be the only problem (caching issues).
  2. If by deleting .htaccess you see your images then dig deeper here. Delete the old file and leave the CMS to create blank new one.
  3. It says so to everybody that updated to bleeding edge. This is not 1.3 final.
  4. Seems like some sort of cache issue. Try clearing all enabled caches in BO. If it doesn't work disable them. If this doesn't work clear your browser cache. If this doesn't work check if you have some sort of server side caching and clear/disable it. At every stage the fixing of the issue is different so please come back with findings and we will be able to help.
  5. All bugs will be considered when their time comes. At the moment there's push for 1.3 and I doubt non-blocker bugs will be considered in it.
  6. If he/she doesn't know basic sql sintax and does not know what should be replaced it's better to leave it as it is. I doubt there will be any issues.
  7. Disabling modules by htaccess file should be enabled but you can at least try... https://www.google.com/search?q=disable+apache+module+htaccess&ei=tMofYbbyK-OnrgSeuY-QBA&oq=disable+apache+module+htaccess&gs_lcp=Cgdnd3Mtd2l6EAMyBggAEBYQHjoHCAAQRxCwAzoFCCEQoAE6CAghEBYQHRAeOggIABAWEAoQHjoECAAQEzoICAAQFhAeEBNKBAhBGABQrCNYvlVgy1ZoAXABeACAAawCiAG-E5IBCDIuMTYuMC4xmAEAoAEByAEIwAEB&sclient=gws-wiz&ved=0ahUKEwi2nLDW9b_yAhXjk4sKHZ7cA0IQ4dUDCA4&uact=5
  8. I don't want to ban the whole country. From regular spam it may escalate to attempts to hack my site just for banning them. And also there are vpns... Still receiving some spam every day.. 😞
  9. Bugs, bugs everywhere... 😄 😄 😄
  10. Today I managed to be on my PC when this happened: 212.107.27.6 Blocked, will see if I would need to ban the whole country. Also, american IPs are browsing for out of stock items. When the email is registered for notification does TB send out an email? @datakick do you have any stats if this feature is used at all? I imagine very little people use it.
  11. It might be just the case. Too busy these days to search the logs but will find time asap. One or two emails a day.
  12. @datakick since your last update to this module I had no issues. In the past few days I'm getting spam on only one of my 3 shops. Module version: 1.1.2 (with 0 at login settings, but it should be fixed, right?) But I had 'disable captcha when logged in. Could a bot keep a cookie?
  13. Wait for @datakick to bump coreupdater version in the api and then update. Bumping it in github does not do so in our BOs, this is separate setting and I believe it's done manually.
  14. This should 'solve' your problem.
  15. Dude, you're becoming very annoying. Please stop your negative criticism, it's getting the project nowhere!
  16. 1. The tax rules should have been created already. 2. The tax rules must be applied according to customer address (not yours) if you sell more than XXXXX Euro in that country.
  17. And they are containing....?!?!
  18. He wrote couple of weeks ago that he was very sick and will get back when he's feeling better.
  19. I have updated to bleeding edge - everything works fine
  20. Yes it works but the oposite situation is much more important imho. And simply they can be build in the same place for ease and simplicity.
  21. I would be happy to see a tool which scans db and shows images that are no more associated with the shop and some easy option for review and bulk removal from storage. Also the reverse tool will be cool also - scan for missing images.
  22. Bleeding edge is now called dev, right?
  23. I think he will issue his own Core updater which will be able to switch between the software.
×
×
  • Create New...