SLiCK_303

What did you upgrade to, 1.1.x Bleeding Edge, or something else?

musta been some sort of caching issue, glad you got it working one way or the other...

you need to go there, and turn on (green check) the left column on Index

blockcategories is installed by default i think, so you just have to show left blocks on the index page? Goto BO>Preferences>Themes>Advanced Settings and change were you want the left block displayed. Then using BO>Modules & Services>Postions and change the position of blockcategories in displayLeftColumn edit the .css files directly, or edit the .sass files and re-compile the theme. There is a module coming up that will let you do the things you would like, but it's not ready for primetime yet.

You need to try and create a module override, or I believe if you are using 1.1.x bleeding edge, you can change the authors name in the module, then tb will not update it.

look just like you uploaded the wrong image or something. instead of uploading the image via ftp or something. have you tried to simply edit the product, delete the bad image/s there and upload a new pic?

Thats good news, thanks for the hard work! 🤗 The rest I'm bummed about, please consider after you work on your own site for awhile, that you come back and help on the forums again, your help is most needed/wanted! 😭

@zen, please make a new topic for your thememaster module, as you've highjacked this thread, and your module deserves it's own topic. I'll have several questions for you about your module once you make your new topic

What constitutes a favorite product? a Best Seller? we have that one.... Then there's featured products and New products and Specials.. I'm pretty sure ps doesnt have a favoriteproduct block does it? If there's a block for ps 1.6 for it, there's a good chance it will work on tb.

Sounds like a caching issue to me, clear your site cache and browser cache. we are talking about so many different problems and jumping around so much it's hard to help you. On a virgin install of 1.1.0 there are 2 folders inside the /themes folder, niara, and community-theme-default, if there is a Niara folder I recommend you do a backup of it, then delete it.

they are supposed to say prestashop. I assume its for compatibility reasons.

ok....and did you do any translations on niara from the BO?

thats a new one, wonder how that happened. I can only assume it would cause problems someplace down the road. the only two folders that should be in the /themes folder is niara and community-theme-default, both lower case. Are there any files in the Niara folder?

Is there a reason you are not using the tb papal module? Glad you fixed your problem though.

I believe the fix for 1.1.x bleeding edge has been committed, so you might try now to update via the core updater again, and see if your problem goes away. Assuming they have the fix available for the updater, it will work. If it doesnt work, I would say its a server issue... I have just tried the latest updates via Core Updater, the spinning is no longer there. So try on your site, and if it still does it, assuming you have no overrides or modules affecting product editing, its a server issue of some sort.

just for fun, you might wanna try it on 1.0.8?

Dont know how up-to-date this is, but does your site meet the minimum requirements? Requirements Support for these general requirements (except recommendations) gets tested during installation, so one can simply try to proceed. A proceeding installation means all requirements are met. PHP 5.6 - PHP 7.3 with a minimum of 128 MiB RAM Apache or nginx Linux or MacOS MySQL 5.5.3+ or MariaDB 5.5+ PHP extensions: Required: bcmath gd json mbstring openssl mysql (PDO only) xml (SimpleXML, DOMDocument) zip Recommended: imap (for allowing to use an IMAP server rather than PHP's built-in mail function) curl (for better handling of background HTTPS requests) opcache (not mandatory because some hosters turn this off in favor of other caching mechanisms) apcu/redis/memcache(d) (for the (currently incomplete) full page cache)

@netamismb, are you running stock tb 1.1.0, or something newer? You can get the latest version of Niara off github, it may fix that issue. (i dont recall if that was a fix or not)

well, i'd say most people think that if you are going to run the release of 1.1.0, that you should just be on 1.1.x Bleeding Edge (meaning the very latest code on github), as it has a boat load of fixes. However in this case it broke something, and thats why some people dont use bleeding edge, cause on rare occasion something breaks. Since you are not on bleeding edge, the 'fix' I proposed above will not help you. sorry. Is this your production site that is having problems running 1.1.0, or is this a test site? I do suggest you wait a day or two, untill the correct fix is on github, and then upgrade to 1.1.x Bleeding Edge via the coreupdater. There are many fixes from 1.1.0 and fixes for Niara.

Are you guys still having issues with product edits, and the save button spinning forever? If so, are you running the latest 1.1.x bleeding edge, because issues are arrising with the new products.js file. As of this post it breaks things, so revert back to your old files, via your latest working /(admindir)/CoreUpdaterBackup-whateverdateworkedstill. Make sure to clear your cache on the site, delete /cache/class_index.php, AND clear your browser cache after words. This problem has been reported on github by @datakick already... https://github.com/thirtybees/thirtybees/issues/1079

Thats disappointing, seems like there were 2 or 3 people giving suggestions, seems like those people might wanna check it out. Beta2 is only beta by name, to my knowledge, except for some small docs editing, it's 100% working..

I guess this would be a feature request... Could you make it so that when a person is already signed in, and has an address in the db, that your module picks up that info, and fills in the top Shipping To info? For most people that would be one less thing they have to fill in / one less step. I would still leave the fields up there in case they want to change that info...

A few things to watch out for when you are setting up this module: In Settings>Orders, make sure you have your Order States setup, by default there are none. (I personally set mine to Delivered and Shipped, set yours accordingly) In Orders, make sure you have a currency setup and active. In Groups, make sure you have them prioritized, with the highest on top, and lowest on the bottom. (so probably the opposite of what its setup on install) Those are 3 tips off the top of my head, I'm sure I'll think of more.... If you have any problems or questions about the setup, I'm sure @wakabayashi or I can help ya. 😉

I saw that, nice catch...

I've always been under the impression it's a rounding issue....but whatever 😉