Jump to content
thirty bees forum

the.rampage.rado

Silver member
 View Profile  See their activity

  • Posts

    1,152

  • Joined

  • Last visited

  • Days Won

    98

 Content Type 

Everything posted by the.rampage.rado

  1. the.rampage.rado
    Latest Warehouse for PS1.6 works like a charm.
  2. the.rampage.rado
    If you switch this setting it messes with .htaccess file. I would suggest to backup it with working settings and then delete it completely. Then set the required settings in BO. If this does not work try clearing all caches - 2 TB caches, manually all your theme cache files and smarty files and if you have some serverside caching enabled it too. Refresh couple of times or try new browser or incognito mode. Some combination of those items should solve your issue 😉
  3. the.rampage.rado
    I have only the basic configuration from the module for pages: And here the configuration is as follows:
  4. the.rampage.rado
    No complains from clients here. Using the latest PS module with the latest TB on php 7.3 and latest PS1.6 Warehouse. No settings for punches are needed for the theme.
  5. the.rampage.rado
    When you change those URLs you have to recreate your htaccess file if you use Pretty URLs function. It's not a bug.
  6. the.rampage.rado
    I looked twice and I don't see it. Whatever... If you're selling TB compatible module on TB store at least it would be nice to present it working on TB... (or PS1.6 at least...).... Otherwise the idea is cool, let's see how it's implemented.
  7. the.rampage.rado
    In your demo the backoffice is in PS1.7 and there's no such module (not enabled for demo user at least)
  8. the.rampage.rado
    With the current dev onboard you can be sure that every commit is tested and he knows the ropes very well. I think in the past 6 months I saw one reverted commit. Feel safe to update to edge when you notice something cool that you want to be fixed in your installation. Bugfix versions will come too.
  9. the.rampage.rado
    And for further security make two backups - one from your hosting and one by FTP. Also make 2 backups of your original DB.
  10. the.rampage.rado
    There were absolutely no design changes in 1.3 compared to any previous TB version. :) If you had some manual changes to the core files of Niara or other theme or BO then it's up to you to fix them in 1.3.
  11. the.rampage.rado
    It will be released but until then you can update to edge. It's tested almost daily.
  12. the.rampage.rado
    Why don't you update to 1.3 and see if there's anything that's better? The update is harmless, no new features, no removed onse. Just lots and lots of bugfixes.
  13. the.rampage.rado
    Turn debug mode on and tell us what's showing when you experience an error.
  14. the.rampage.rado
    Dollibarr is pretty much dead in the water anyways... Try some newer CRP and find the proper connector. I know it's hard and probably that's why you went with dolibarr. EDIT: Dead in the water is little harsh, obviously the project is alive but I believe you should consider other options.
  15. the.rampage.rado
    The suggested edit will never solve your issue. It was in connection to your 'in development' installation. To try and solve your issue you should try the following: 1. Clear all caches 2. Update your store to the latest version (1.3) 3. Regenerate your thumbnails (in Images menu) 4. If still no images present in Front End please right click on some missing image and find the complete URL. Copy and paste it in new tab and see if it opens. If it opens please clear your .htaccess file and regenerate it by disabling and then reenabling pretty URLs (in URLs menu section).
  16. the.rampage.rado
    You can't use slider in text field and currently TB does not sort according to length. The other option is custom work on this module which makes future improvements and bugfixes harder.
  17. the.rampage.rado
    Preferences->Themes->(active theme) Advanced settings->bottom of page, find CMS and turn left column off. Cache clearing may be needed to see the changes.
  18. the.rampage.rado
    You can use the preset for Weight (if you're not using it currently). Make all your values a number (it won't take any other characters) and rename your weight to length. It will show only if there are products with set parameters for it in this category.
  19. the.rampage.rado
    No it won't help. Uploading the theme does not change anything in Images other than making 2 more sizes. If you don't understand what I mean please contact somebody that can make this tweak for you.
  20. the.rampage.rado
    Check your Warehouse documentation, there's part for images in which the proper names and sizes are shown as screenshot.
  21. the.rampage.rado
    I think Warehouse for PS 1.6 does not support .webp so no need to fiddle with this. The problem is caused by the file names that Warehouse expects from PS/TB. With TB there were changes in this logic so you should fix the file names under Images according the theme documentation. Then everything will be fine (after you clear all caches, TBs and your browser).
  22. the.rampage.rado
    Just compare few of them. I had similar issue with injection from WP site on the same host. It was putting php files in img category and the updater caught them. If there are couple of discrepancies outside of the files for your module I would manually compare for changes in those files, merge and update my whole site. TB 1.3 is a charm!
  23. the.rampage.rado
    7.4 should still has some issues (warning in the core and bugs in themes). I've tested up to 7.3 and it worked for 1.2.x. I'm running on litespeed, mariadb, ssd, and php 7.2 with apc and litespeed cache module. 3 stores, 1 WP site. It all depends on what amount of customers do you expect and you can upgrade from here but this is working just fine for me.
  24. the.rampage.rado

    1.2 vs 1.3

    the.rampage.rado replied to nickz's topic in English

    There's no difference with customization in both versions... We prefer the latest - less bugs, faster.
  25. the.rampage.rado
    On top of my head here's the most pressing issue with TB that can be fixed with this solution - order finalizing. When customer clicks on "Confirm my order" it usually takes up to 5-10 seconds to refresh the page. In the meantime emails are sent, order is made, etc. This mechanism could potentially reduce the time in this vital step and improve UX. I had numerous questions about this issue from inpatient clients clicking numerous time or even 'having issues on the last step'....
×
×
  • Create New...