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.

When you change those URLs you have to recreate your htaccess file if you use Pretty URLs function. It's not a bug.

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.

In your demo the backoffice is in PS1.7 and there's no such module (not enabled for demo user at least)

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.

And for further security make two backups - one from your hosting and one by FTP. Also make 2 backups of your original DB.

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.

It will be released but until then you can update to edge. It's tested almost daily.

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.

Turn debug mode on and tell us what's showing when you experience an error.

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.

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).

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.

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.

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.

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.

Check your Warehouse documentation, there's part for images in which the proper names and sizes are shown as screenshot.

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).

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!

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.

There's no difference with customization in both versions... We prefer the latest - less bugs, faster.

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'....

I would like to have the in transit email sent out when I set the tracking number in BO. But I would like to have Sent out option and the in transit status somehow merged. Now I have to manually change the status to Sent out (which sends out an email by default). Then I have to put in tracking number (this sends almost the same email, same title, etc with the only one line added - the tracking URL. I would like to have this in single action, I doubt it could be done so I have disabled the Sent out email and the customer receive only 1 email with tracking number which states that the order is shipped.

You can upload file when ordering a product as @datakick said but TB lacks good 'do-it-yourself' design module that spits out design ready for printing. Your friend should manually send design versions, etc... big pain in the .....

Glad that he/she managed to put back his/her Core folder. :)