Jump to content
thirty bees forum

SLiCK_303

Trusted Members
  • Posts

    1,200
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by SLiCK_303

  1. @datakick, thanks for reporting it on github for me. oh, and while we are on the subject of Specific Prices, is there any way we can get an edit button so we can edit those in the furture, instead of deleting them and remaking them?
  2. I dont know if it's a bug, or I have something else going on, but I seem to have an issue with my Specific Prices. I have a 1.1.0 live site, then I have other copies of it I test with. Well in 1.0.8 my Specific Prices for this particular product looks like the 108.png file below, and my 1.1.0 site is the other pic. Notice on the Fixed Price line, the info is missing on the 1.1.0 site, but on the 1.0.8 site it shows. Also, if I use the core updater on my 1.1.0 site, and bring it back to 1.0.8, when I goto the Prices tab on the product, the tb's busy dealie on the upper left of the screen, will just spin, not letting me into the Prices tab at all. It looks like this with all my products like that one below, not just this one product....
  3. I'm on tb 1.1.0, with tb's Paypal module v5.4.2. It happens so infrequently, i'm not sure how it could even be troubleshot.... Come to think of it, I probably shouldnt have even brought it up again, as I dont recall if this is still happening since the 1.1.0 upgrade. Would be nice to have the product breakout again on Paypal invoices again tho. Sometimes less info makes things better.......sometimes....not. But thats for another topic...
  4. This bug has been happening for me for a long time, just some orders dont seem to go through to the system, but show up on your paypal. I hope it gets fixed at some point.....
  5. You would want to use the Prestashop 1.6 version, or install instructions, as thirtybees is based off 1.6. As for if it's compatible, ask the creator of the module if it works on thirtybees or not.
  6. make sure there is a config.xml file in the themes root folder. also, if you are installing via a pack, there need to be a config.xml file out in the zips root. or, if memory serves me, you should just be able to ftp the theme to your site, and assuming there is a config.xml file in the root, tb's will pick it up, and let you install it from there.
  7. so...then like i said...simply ftp the files to your server and reinstall. If you think the community theme is corrupted, then un-install it and delete it first, then re-upload, and re-install.
  8. If you deleted both themes, then simply ftp them back to the theme folder, and re-install....
  9. bo>modules>blocktopmenu>configuration, change maximum level depth. thats for the top menu. For the side menu I believe its, bo>modules>blockcategories>configuration, change maximum depth
  10. hahaha, no trouble, all is good. 🙂
  11. Gotcha.. thanx for explaining. Nice job on the update too..... 🙂
  12. @led24ee Glad you got it working. Anyone with any thoughts on the message towards the top of the page saying: Cron is not set up correctly. Please follow set up instructions I've reset the module, that was fun, it erased all my cron jobs, and I had to put them in again. Now it is saying an execution date, but still has that error on the top.
  13. you have to use something..... Or is this a localhost setup?
  14. Do you use Cpanel or Plesk for your hosting?
  15. since the upgrade to 2.2.0, I get this, anyone have any idea why?
  16. @led24ee Assuming those modules files are on your server, and you just really have to have these modules, and cant wait for the developers to change it, you can do this.... All three of those modules have the same problem and need the same fix. edit the main .php of each module, for instance in the Tawk.To module you would edit tawkto.php, and look for something like: $this->tb_versions_compliancy = '1.0.x'; now replace that line with the following two lines: $this->tb_min_version = '1.0.0'; $this->tb_versions_compliancy = '> 1.0.0'; Do that in the main file of each of those modules, and it should let you install them. edit: I did a github pull request for all three of these modules, seems to work for me anyways....
  17. @vzex If you do a fresh install, Niara is installed and the default theme. If you do an upgrade to v1.1.0, it seems as though it doesn't copy the new theme over. At least that's what happened for me.
  18. Congrats to all of you who contributed to this project, to get this release done, this is a big step.....
  19. wow....thanks for the hard work guys!!
  20. Looks like Google+ has been gone for a long time? I would think if that's the case, that it's time to remove it from the social modules, and theme product pages....
  21. hmmm, maybe its a weird caching issue on my side, dunno.
  22. @yaniv14 works like a champ...good job!
  23. So, if you goto the BO>Modules & Services>Positions, goto the bottom of the list, which should be 'Header'. Now move a module up or down, make it at the bottom of the list for fun. Now after moving goto Positions again, and look at the order at the bottom of the list, at the module you just moved. It seems, on my server and setup ect, that the module will not be in the place you expected it to be. Make sure to try to move a module up, have it save, then go back to Positions, and do the same moving it down. The results seem almost random....... Also, make sure you are doing a drag and drop, not using the arrows to move up and down.
  24. I'm thinking that it's because of.. $this->confirmUninstall = $this->l('Are you sure about removing these details?'); bankwire module has this line in it's main php file, the modules that have no message do not have this line. So I recommend that there should be a default message, or make this line one of the requirements for module writing. I think it would be more accurate, at least in english, that it reads something like.. $this->confirmUninstall = $this->l('Are you sure about removing this module?'); ..or something similar.
  25. I noticed this same behavior on my 1.0.8-1.0.x site too, not sure now long it's been like this...... edit: i have a 1.0.6 test site (dont ask), and it does this same thing. So this behavior has been going on for a long time.
×
×
  • Create New...