cienislaw

IMO Niara is just a 'skin' for Community Theme. there are no major differences between those two in terms of functionality. so as Community Theme was outdated, Niara still is too, but looks a bit fresher.

from my perspective it's simple: 1. point out where current themes suck and address those issues mobile experience shopping process ux cart... code duplication to achieve the same thing in different places 2. give it modern look with minimal set of features 3. reduce quantity of modules used to achieve that anything else should be in merchant hands or someone hired by him.

in such case this initiative will fail. don't get me wrong, but 'community' will launch an endless loop of wishes.

yup, it's time to move on. current state is unacceptable in a long run. theme architecture is archaic, with a lot of teeny-tiny modules for very specific outcome. as many of you said before - you really don't need a bunch of modules, a successful shop can be build with just a few of them. for sure, building a new theme in community style will not be easy, but IMO it's the only way. TB user base is too small to invest a lot to build new modern theme and frankly, I really don't like commercial themes as those are bloated with too much stuff. if someone starts such a project, I will try to help.

check user groups and their access to this category.

read again what @rubben1985 wrote. for those who don't have account on prestashop marketplace (is it possible?;-), message is below.

no changes in repo for almost 3 weeks so...

no, this bug is still unresolved on github.

I would suggest a quick rename of admin folder which you just posted publicly above.

are there more such traps in themes? theme really shouldn't calculate anything, just take data from core and display it.

fill in meta title

you have active Live Configurator mode.

so discount is calculated once for default variant or most expensive one - this need a fix asap.

he is helping, but on his terms. code is public, so if TB core team finds something interesting in ME, they can use it.

Well said. IMO Commercial themes pack too much stuff and tempt users to use it all as on examples, which are there not to show you how to achieve good and simple look (not basic!), but present all theme features. This is a snake eating own tail situation, when with too much stuff and freedom you bloat the site with fancy stuff, which doesn't help sales at all and frustrates users.

just one question about using Tailwind CSS - what about compatibility with the rest of the Prestashop 1.6 world as it is Bootstrap v3 based?

We need a modern look, ux design and shopping process/experience. Community Theme Default is several years old. It has flaws, it isn't mobile friendly at all. Don't get me wrong guys, but another face lifting will get just a bit better theme, not a new perspective this project needs. I'm not saying that existing code can't be reused in some way, but for sure shouldn't be used as a base for a new template. Also there is a need to change a way of expanding theme features. I know that no one is forcing you to use a lot of modules, but currently there is a module for every little thing, with a lot of duplicated data and so on. This, beside removal of useless modules from a theme, can be addressed in favor of using HTML Block, so module bloat will be minimalized. I don't think that there is a need for mobile and desktop version - more space doesn't mean that you should bloat it with something and a good RWD designed theme will look good on both platforms. Feature voting - I'm against it. Most of us merchants on this forum are not graphic or ux designers, and you can see it clearly by visiting our shops. Of course users can suggest something, but the final look and feel of theme should be decided by professionals. There is also need of translations proofreading. Even the best theme shopping experience will be ruined with bad translation, and if the rest of them is as bad as Polish one... I understand how works community translation and I know that it's hard to get quality with multiple people translating something they don't even use. Proofreading will take time, but it will be worth it. That's my five cents which should explain my point of view on this matter.

I hope that new owners have a new default theme for 30b on the roadmap. By new I mean done from scratch, because any other way will be only face lifting without heavy lifting. By a new default theme I don't have in mind anything close to Panda or other commercial themes, not at all. But we need a new theme, based on 2021 design rules, with heavy focus on mobile version and so on.

just checked my provider and php 5.6 is still available, but default is set to 7.3. 5.6 is 6 and a half years old, if someone still uses it, better have good reason to do that.

there is a lot of code waiting months to be merged. I hoped that after take over github will be flooded with commits, but last one was 4 months ago.

Clean up repos (core and modules) from bug reports and pull requests.

yeah, it can log out or block you from logging in. it's pain in ass on mobile connections, as IP changes there quite frequently. after disabling this check, problem solved.

well said - 1.1.0 has a few 'imperfections' which can make you a bit frustrated.

edit coresponding php files and add a hidden-print class to elements you dont want to have on printed page. <div class="hidden-print">content for non print</div> <div class="visible-print">content for print only</div>

let me copy & paste it for you: https://nodejs.org/en/ Download and install node.js + npm, LTS version will do. With npm up and running you can finally compile SASS to CSS. To do that, make sure you first set up build environment. Steps to do that you can find below. Be aware, that you have to do this on your local machine and use Niara theme from GitHub repo, not release from your store. https://github.com/thirtybees/niara Building This theme works as-is on thirty bees, all built files are committed to the repository. CSS files shouldn't get edited directly, but their Sass counterpart in sass/ instead. After doing so, CSS gets compiled from that. For contributions, please create commits including both, source file changes together with their build results. Setting up the build environment npm install Building CSS from Sass npm run compile-css Linting JavaScript npm run lint-js