wakabayashi

Maybe the leightweight word is very confusing. I meant it in a technical way... It's of course possible to build a theme, which looks nice. But what is nice? To make my point more clear. For theme develeopers it's not easy to start. Should you just use the community theme and change it? But which class can you remove, which not? Very hard to understand. Is the community theme a good starting point? Some might even doubt that... From my opinion a skeleton theme is needed and clear standards.

Well I am 99% sure, that the blog is wrong then... But you can test it out... What the blog writes, would be the logical way, but it isn't like that. Thats why this issues come up every month.

You need to make everything red... Only the things which should be loaded dynamically should be green... @lesley please finally write this into the core. It always confuses merchants.

@mockob said in Plans and priorities for the community theme: If there is someone to design clear and light template with all basic thirty bees features This was actually the goal of the community theme. I guess for tb/1.6 ps it's almost impossible to make something like clear and light template. This is software is so big and the documentation is not really there. I am not a big fan of 1.7 ps of course. But I like their idea of having a plain theme...

I understood it like this: A new merchant wont spent 2000€, if 90% is working for free. He wants to buy some cheaper module and spend 200-300€. He said this in answer to the customization post from you. As you said: you haven't spend yet a big amount for modules. What would you be ready to pay for customization and support? Keep in mind that this things are a way more expensive than modules, which can be sold multiple times.

@nickon That is basically, what he is saying, isn't it?

At least Traumflug is still alive :) good to see you back here @Traumflug

@vincentdenkspel yeah unfortunately thats the sad reality. Right now I can't imagine a user based way, which leads to any serious cash flow.

Actually I dont have any time to produce something like that. And to be honest, it wouldn't be worth the time. My free module was downloaded maybe from 5 people and this after I spent like 6 weeks to code it. The TB plattform is just a way too small to take any money out if it.

Cool stuff! Maybe it's something for the core. But maybe the customer Service should be redesigned in a bigger way!? At least for me the customer service right now, is a big mess :)

There is also a book from Fabien Serny, which helped me a lot...

Well I just checked with 1.0.8. There wan't this issue for me. So I guess there is a new bug somewhere or a totally new concept with bootstrap!? (I dont use bootstrap in my theme - dont ask my why :D) Edit: it works now

@datakick does this module now require bootstrap or something? In my teststore it doesn't display anymore correctly :( For me the colors are no more working... And as you can see the stars arent floating...

New 1.0.1 version was just released! It includes some bug fixes and some minor improvements. They come mainly from @SLiCK_303!

@SLiCK_303 thx for the feedback. I for myself arent live at the moment. Didn't have to time to set it up :) But of course soon I will go live too ;)

Today I released v.1.0.0. You can find the module in official store: https://store.thirtybees.com/shop-modules/front-office/genzo-krona @SLiCK_303 thx for your doozens of hours testing the module with me!

@30knees in the new release you can use the coupon 'KronaTemplate: Orders' as a template... So all functionalities are available. For any kind of features which are based on email sending, I will definitely wait for datakicks planned mailstream module. So don't expect this feature to be soon in the module.

@yaniv14 oh cool. I just saw it. That's really advanced stuff! Didn't even know that there is such a method ^^

@yaniv14 nice! Don't you wanna make a pull request for it?

@zimmer-media In the upcoming release the hookDisplayProductButtons will be availble. But you have to hook it manually and unhook DisplayRightColumnProduct.

@30knees thx for your feedback! No idea, tbh. But all module files can be overriden in your theme folder, so everbody can design it like it fits best for him. It's not possible to find a perfect design for all themes ;) Yes you can import them. This feature haven't been tested a lot, since I don't use loyalty module myself. You are right. It makes not much sense, to use native module and mine on the same time. I would decide for one or the other. I haven't thought seriously about it. Right now it's not planned, since it's not so easy to implement. I have my module would become popular and the feature is asked multiple times, I will think about it. Well with my module you can use all coupon features, which are available in TB. You just need to setup a "template". Just now I notice, that you are maybe talking about the loyalty points which are converted by the customer. I will improve this way, so you can use a template Coupon as well. Yes. In future you can set it up, like you prefer. Will be fixed in the next release.

I have just released a new beta 0.8: https://github.com/eschiendorfer/genzo_krona/releases It's a huge rewrite with some database changes. That's why you should reset your module. Soon the module is going to be released with 1.0 version. The 0.8 doesn't include many new features, but the backoffice is now using controllers, which will make it easier in the feature to add features. I also tried to restructure the module, so it's a bit less messy :) ;) Thx to @datakick for implementing krona in his awesome review module: https://github.com/getdatakick/revws

well, acutally I dont care which one we use. I just think one is enough...

@lesley maybe gitter is no more needed. It's not that active and slack does the job well. So it gets a bit more lucidly.

@nssimpson you should tell, why PS is not the solution for you. Then we can say, if this points are handled differently here.