Joint Systems

The best solution I have found so far is is to copy all the images to a different folder you create for the purpose in file manager, and or download all of them. If you have already done the theme or slider upgrade and lost all the images, is to copy the images from a similar store, if you have one or upload them in mass through the file manager.

If you are using the default theme you have to delete the homeslider.tpl in the theme to get it to work. What you get if you use the edit from github is the pictures appear but it pushes the icons down below the slider rather than where they usually are on the side. The github edit works in the Community theme. Deleting the homeslider.tpl in the Community Theme does not work as it distorts the images. Is there some way to preserve the theme configuration rather than having to reconfigure it every time you change themes? Yes, The best solution I have found so far is is to copy all the images to a different folder you create for the purpose in file manager, and or download all of them. If you have already done the theme or slider upgrade and lost all the images, is to copy the images from a similar store, if you have one or upload them in mass through the file manager.

If you are using the default theme you have to delete the homeslider.tpl in the theme to get it to work. What you get if you use the edit from github is the pictures appear but it pushes the icons down below the slider rather than where they usually are on the side. The github edit works in the Community theme. Deleting the homeslider.tpl in the Community Theme does not work as it distorts the images. Is there some way to preserve the theme configuration rather than having to reconfigure it every time you change themes?

Downloaded the new slider module for 1.4 stable, installed it on two stores neither works? Also down loaded and installed the new theme configuator, which delinked all the images in the theme, an hour and a half later the theme works but the slider images do not.

This is what was changed going backwards from 1.5 to stable 1.4:

This is how I fixed it: Since we have numerous shops running TB some of them were still running the Bleeding edge version of 1.3 (1.4) prior to release or the new upgrade. " New module verion is available You are using an outdated version 1.60 of core updater module" This old verision however worked when set in the bleeding edge verision. So I went to one of the stores that was running the old core updater 1.6 module and copied it to one of the stores that no longer worked. I then went to the store and was able get into modules and settings and went to the core updater which was set at the choice update which using the drop down icon switched to configure. Went in and changed it to stable rather tha bleeding edge and saved it. then I went to core updater in the preferences and ran that so i was now back to 1.4, then I switched the PHP version back to 7.4 and the store was now back online. P.S. it also works with the old 1.6 version of core updater module set to the bleeding edge mode and the core updater in preferences run with that setting.

What i f you can no longer get into modules and services to get to the core updater settings to change back to 7.4?

According to the cpanel for the account the php is set at 7.4. though the error log said we were running 7.33. What is even stranger, this is a sub-directory/shop and the main directory and two other sub-directories worked fine. All three are subs are part of a multi-store under the main directory. We were able to get the shop back by copying the vendor folder from one of the working sub-directories, and though that sub-directory was running 1.4. it reset thhe /shop directory back to 1.3. We then went in and checked the core module and it had been set to php 7.4. so we saved it again and then ran the core updater again only to get the same error message. So we had to copy the vendor directory again from a working sub-directory which again restored access to the site but again at 1.3. We just updated one of the other sub-directory stores /market to 1.4 without issue.

One of our sites we can no longer get into front of back, error message 'Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 7.4.0".' I assume someone forgot to choose the php level when switching from stable to Bleeding Edge 14 ?

We are on the bleeding edge and before moving from stable we used the excel files 95% of the time under php 7.4, If we do a search for updates tbspreadsheetsource does not show up? Do you have to download it from Github? In the mean time one of our sites we can no longer get into front or back end, error message Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 7.4.0". I assume someone forgot to choose the php level when switching from stable to BE 14. How do we fix that?

Stay logged in box cannot be checked after recaptha is installed using the most receent Chrome. Tried adding the code /* fix: chrome99+ login flying blocks */#login_form #remind-me,#login_form .show-forgot-password { position:relative;} as suggested for movement problem, but did not work. There doesn't seem to be a problem in FoxFire?

We deleted two catagories including all products without difficulties. When we deleted the third and went back to products without filter by catagory there was 0 in the catalog, however when you go to prefrenses search it shows: The "indexed" products have been analyzed by thirty bees and will appear in the results of a front office search.Indexed products 283450 / 283450. We tried rebuilding the index which said completed successfully, still 0 products in catalog. Ran TB cleaner module check and fix, still 0 products. Ran clean and optimize both of which dompleted succesfully but 0 products? Disabled Categories0 Empty Categories0 Top Category30 DAYS Silver Streak Average number of products per category 10123

When altering the php7.4 php-fpm presets for use with TB 1.3 and 1.4 are there any particular recomendations, beyond the general requirements? So far based on the logs 5 children is inadequate and had to raise that to 500 but according to the hosting company the server is using a PHP handler LSPl so changing the settings does nothing. Currently the server we are using is a dual Xeon Silver 4208 (3.2GHz) with 64 GB DDR4 ram and 2 TB SSD.

The he/she means the core folder not the module. Jointsystems.org is up and running again now in 1.3. The 1.4 installation has been running well, so far, what are the main adavantages?

You are correct, deleted cache/class_index.php and now jointsystem.org works. As far as "What does this mean?" I only deleted the core folder only and copied the core from the working 1.3. When that resulted in the TB installation not working I restored the original 1.2 core folder and the store is still down.