doclucas

@wakabayashi said in prozis.com I think is a great example: Sure it is. But I don't like the idea, that every module includes it's own technique. :) Imagine you include this one to your module. Another coder adds another editor to his newsletter module. That is in my opinion not a nice situation for the merchants. Maybe I don't understand this argument so well, but what exactly do you propose?

ok, noted, still an advanced module that does all those things can be made for TB (paid or free), the current core code is good enough to run such a module - that's my point.

lol, it was an example, bro

That's what modules are for. ;) And there are plenty of such advanced CMS modules for PS 1.6 already. Here is one example: https://addons.prestashop.com/en/page-customization/19835-advanced-cms-contenmaker-for-landing-pages.html Which brings me to my original point - these things can be done on TB. :)

It's just a static information page that can be done with a CMS module.

Are you sure such an about us page can't be done in TB? Looks like a simple html information page that can be done with a WYSIWYG editor with added js and css. Yes, I am also a developer, but currently brainstorming :)

@wakabayashi Would really love if you can write a full list of such things from this website so that we know what and where we can improve the core...

I am pretty sure making a template built on TB that does pretty much everything that this site does is doable, as long as we are just talking about js/css design elements. And as I pointed out about elasticsearch, some if not all of the features are already available in TB core, modules or possibly with prestashop 1.6 modules.

You can check out TB elasticsearch in action here: https://rackmetro.com/

Yeah, TB has elasticsearch module that (I think) does the same thing. Have you tried it? https://store.thirtybees.com/shop-modules/front-office/elastic-search-module

Thanks for the details. :) These are all theme/template related ie. design elements, not really features. One feature I did notice and like there is the countdown for today's shipping (similar to amazon's idea, but different design).

Not saying they do that, but facebook likes can be bought quite easily and many companies do. What specific features you all like in their website?

Could you please give an example of what it was before and after the fix? It can help others.

@elund said in Problem with price on product page after upgrade to 1.0,4: Where is "displayDiscountPrice" defined and set?

Please provide full step by step instructions on how we can reproduce this issue on a stock installation. Also, please let us know what TB version you have installed.

@traumflug said in Update on thirty bees: There’s another reason why offering a fairly feature complete rather than a reduced default installation is a good idea. Yes, it is not about reduced default installation, on the contrary, I totally agree that feature-rich is very important, the more features the better and the more attractive it will make TB. It is about the default theme/look setup on a stock installation. @traumflug said in Update on thirty bees: They don’t. I was referring to international giants in general, such as Amazon that was referenced in the previous post, not to that specific site.

@traumflug said in Disable in_transit email: It’s always best to use overrides when possible. Best is to get bug fixes into core. Which requires a fairly clear description of what the actual problem is, together with the changed files in an issue report. Of course, but this is not a bug as far as I understand, and as lesley pointed out above.

I think it is very important to note in such threads that modifying core code directly is not recommended and won't survive future TB/core updates (manual copying of modifications is required when upgrading). It's always best to use overrides when possible.

Thanks for the informative tutorial. Isn't it easier to simply use tool such as the free TOAD: https://mariadb.com/kb/en/library/toad-for-mysql-80/

@dosbiner my pleasure ;)

I generally agree with your post, @colorful-ant , with one exception. You have to remember those online retail giants are also working internationally and conform with international laws as well. They also spent and keep on spedning millions if not billions in marketing R&D to figure out what works in online marketing and what doesn't. Imitating them and learning from their very hard learned and highly paid lessons is wise and completely does not contradict with fighting these giants, ie. fighting them by having good sales through our TB shops. :)

Yep. I guess he meant that this is how the checkout should be looking by default, so that those BO options (of those fields) will be disabled by default on a stock installation (while can be enabled by admin of course, if and when needed). One of the best marketing advisors I ever met once told me - simplicity is the key. The more you simplify your UI/UX and make important things stand out and be more accessible, the better conversions you will have. Regardless of the one-page-checkout point , I think @ajensen27 made some valid points for improvement (and so did I :) ), and we always appreciate (constructive) feedbacks, whether we accept them as they are, modify them a bit, build on them or skip them altogether.

lol. @dynambee seems to be a lost cause. better we move along.

Not to mention the times on this thread my posts (and I think other threads) did help you and the fact that my "fix" is not already in 2.1.3! you are looking in the wrong place! Sheesh

Pull request: https://github.com/thirtybees/cronjobs/pull/7