Jump to content
thirty bees forum

the.rampage.rado

Silver member
  • Posts

    912
  • Joined

  • Last visited

  • Days Won

    62

Posts posted by the.rampage.rado

  1. 1 hour ago, unica e-shop said:

    @the.rampage.rado Thank you very much that did help with the secound issue, but the issue no 1 is more serious, do you have any idea of how to fix it? 🙂

    This error might be caused by many factors. Did you make any changes to the core (overrides, etc.)?

    Is it actually uploading it under this error or not at all?

  2. That's because Core updater is made to guard you against updating TB to version that does not support your current php version. Minimum for 1.5.1 is php7.4


    So first update to TB1.4 and php7.3, then switch to php7.4, update to TB1.5.1 and iron out any issues, bugs, warnings, errors with your modules and theme.

    After that update to php 8.0 - check once again for bugs, if none, update to 8.1 and you're super fast, secure (TB1.5.1 come with many bugfixes and security fixes) and happy.

  3. 7.3 to 8.x is quite a big step.

    Downgrade to 7.4 and fix all errors, exceptions, warnings. The notices you might leave until 8.x because they should not break your shop.

    Your theme could not support php8 or some of the third party modules.

     

    You have collect logs module, right?

  4. Regarding the second error - you can safely uninstall this module (tbupdater, NOT CORE UPDATER, they are 2 different modules) and update to 1.5.1

    If doing so does not fix your first error please come back and we will try to help.

    Regarding the 1.5.1 update - you have to do couple more 'fixes' - you have to install the minify module that comes with this version and also choose, install and configure one of the two email transport modules that take care of email since 1.5.

  5. As we're talking in another thread just now - remove image magic module, check if it left it's override in the override folder, remove it, clear your caches and redo all your images again as it's clashing with the webp implementation currently in core and it will not work properly.

    Glad that you managed to update and now your shop is working again! Monitor for errors and share with us so hopefully the community could help and make your life easier!

    In general the current thumbnail regeneration process should never timeout but it's speed depends on many factors - number of images, their size, server overhead, etc. Image magic override does not help too.

     

  6. 24 minutes ago, 312erik123 said:

    Hello,

    Problem solved, or kind of solved... The overrides from ImageMagic remained eventhough i had disabled the module. With them removed I now get webp-images, most of them are quite a bit bigger than the jpgs...maybe a quality setting...

    And for anyone else looking to trouble shoot php code using Logger::addlog(""); works well!

    So basically I was right!? 😛

  7. 9 hours ago, movieseals said:

    Wow.  Guest view set as Yes is indeed incredibly fast!

    I used to get the crawler working under 1.3.  Have not yet tried with 1.5 - can update you when I do.

    I managed to fix my issue: the cache works properly with group and logged in mode in 1.5 - it has issues only under 1.3.

    Really enjoying what was done to 1.5 so far!  

     

    By 'cache' you mean the full page cache?

  8. Did you do experiments with  "Enable Guest Mode"? If I set "Yes, guest view" the home page loads nearly instantly but sometimes I receive a popup related to product availability (probably it shows some information regarding a previous order in the shop). With First page only it's also fast but not so much.

    Also the crawler - I'm unable to set it up on my shared hosting, tried on three domains and gave up. It simply does not want to index the pages, but when I open them it ways X-Litespeed-cache miss. If I reload it of course works (hit).

    Otherwise the cache is definitely working but has it quirks... 

    • Like 1
  9. 3 hours ago, movieseals said:

    We no longer need to use Imagemagick?  First time I hear of this.  Any reason why?  I just want to understand the logic behind dropping it.  I was currently using it to automatically generate webp since my theme did not create them at upload.

    My theme also did not create any webp 😄

    But the core does since 1.4 so no need for this module. It had some nice features like white background trim, etc. but in my case it was causing exactly the same issue as the topic creator.

    I also removed the watermark modules from my site - I don't sell unique items so I decided this overhead is not needed too.


    @movieseals Could you check your jpg and webp files if they are not exactly the same size?

  10. The target setting in Core updaters points the module to which PHP version of the core files you want to update next, not what version you're currently running on your server at the moment. This is VERY useful you are debugging modules errors moving forward with PHP and you need to roll back to php7.4. You should always set this to 'Server PHP version' if you don't do some changes (updates of the core or testing newer php version).

    As datakick advised:

    • 1.4 is compatible with php 7.4
    • 1.5 is compatible with php8+ but many modules will not be. It runs on 7.4 also.

     

    • So first install collectlogs module (or regularly read you error_log manually), roll to php7.4. If you have any issues with your module (errors, warnings, etc - fix them now!).
    • Roll to 1.4 if you're using an older version - fix errors and warnings on php7.4. Make db changes and fixes in Core module.
    • Roll to 1.5, remove tbupdater module (NOT Core updater module, they are different), update all native modules (if update is available), choose, install and configure email transport module (1.5 will not send emails out if this is not done, 3 minutes), install minification module (this was in the core, but was moved to a module for compatibility reasons, check if your code minification settings are proper in the old place where they were before, 1 minute). Make db changes and fixes in Core updater module. Look for new errors with your modules in Collectlogs module (core and native modules should work perfectly on php7.4).
    • Then update to php8.0 - again look for errors, if any - fix them.
    • And proceed to the latest php8 version you wish to use in the same manner.


    DO NOT UPDATE directly from 7.3 to 8.2 - your shop will crash 99% (99% because of installed 3rd party modules).

    At each step - make a USEFULL backup of your DB and file system.

  11. 16 hours ago, movieseals said:

    With the cache module and all the other caches in TB 1.5, it is quite faster.  The only one I am not sure if we can use or not is Full page cache in TB.  It does not seem like a typical full page cache, but technically, according to the documentation for the Litespeed cache, it should be off as it may conflict.  Other than that, nothing to say except the separate view for mobile in the LS Cache does not seem to work very well.  And different views for groups or views for logged or non logged individuals crashes some PS modules.

    I also noted that vanilla Litespeed was still considerably faster than Apache and even Nginx as Proxy, which is what I had before.  And our store was significantly smaller back then.  So Litespeed is definitely an improvement for us.  I also like Cyberpanel, which is like a cpanel for Litespeed and Openlitespeed. It has its growning pains but now works mostly very well for most usages.  It loads quickly and it is pretty versatile and simpler to understand than cpanel.

    image.thumb.png.c014ba06d00ee5946a021ddf1ed7d9c2.pngThis is my config. v.1.4.1 (I used 1.4 for quite a long time and also had no issues (I could find) with my setup). Could you share yours?

    I use Warehouse and I have no separate mobile view.

  12. 11 hours ago, Cassim said:

    Are you looking into a way of doing some kind of update prices based on a external price?
    A pricematch system? 

    IMHO - price matching is the most toxic way of making business. If you can't offer constant lower price try to attract customers in a different way.

    The module - 10/10 - statistics that every merchant needs but if you don't use external system you were stuck up until now.

     

    A feature proposal I have is if we can add global catalogue statistics in the module:
    1. Global average and median values for the catalogue.

    2. A list of products without available statistics, so in general without added wholesale price - this will make the adoption for the module lot quicker for sites that did not enter this valuable metric per product up until now. (as my old shop, where all profit calculations were done outside the shop).

×
×
  • Create New...