wakabayashi

I know this concept from big companies. A lot of others have tried to establish some kind of marketplace, but most of them fail. If I had something like that in mind, I would hire 50 devs / 10 marketers and start all over again. Maybe your idea is very small. Then there might be a module for it. I have seen such stuff before. Maybe from webkul.

I click this buttons since years 😅 The thing I noticed: the dashboard has issues with the first day of the month. But maybe that was fixed. I am not on bleeding edge right now...

Haven't worked too much with payment modules. But this is surely about the module and not a core thing. Which one is used?

Haha right. My own theme has also been postopened to 2023... 🙃

Css seems to be missing. Delete cache. If this doesnt help try some setting changes under performances.

TB is not the problem: Btw my last PR was merged in 10 minutes 😂 This project never won't be shopify. But at the moment it's really making progress.

There is no issue in asking questions. That's what the forum is for. But I can feel @the.rampage.rado. Sometimes when you help, your solution proposal is not even been taking into account. This can be really frustrating. Also I have to add, that his message was a bit provocative. Probably he shouldn't have post it. BUT you were the one, that started to INSULT.

Guys please relax. Soon its weekend 😏

Well that could take a multiple failed orders till it works again. I just wanted to add the important php graphic, to illustrate that this issue has not so much todo with TB: So very soon php7 won't be supported anymore. It means the same trouble for all prestashop 1.6 shops. If you are lucky, some module devs still fix their modules. If not, you should either look for an alternative module or let it fix. I have no experience in this, but I would expect that most modules can be fixed in 1-2 hours. Ofc I might be wrong.

All good 🙂 I just tried to explain in clear words. The questions about a new theme comes up a lot lately. "more attractive and intuitive" sounds good. But every merchants has a different view on it. Personally I try to simplify everything for my customer. Taking away all element that arent needed. And my main goal is to make it almost as mobile friendly as an app. But it's easier said than done.

Thats a very important part. Nowdays I try to code as clean as possible, but from time to time I say myself "fuck off". Example: why should I invest a week for having customization in the theme, if I don't use this at all 🙂

I don't understand, what this devBlinders do!? If it's just about fixing and improving a little, they could submit PRs to prestashop. Optically it looks the same as classical theme. The last commit was 9 months ago... The hummingbird project is more interesting to me, but I am also sceptical: So it breaks everything, but is no rewrite either. What is it then? Some guys would say: a typical prestashop project. To reply your intital question, why there is no collaboration... It's a huge workload. Jollyfrog is not even active here and I haven't seen any real value from him. @zen has done his cisero theme. @datakick has other stuff to do. @toplakd and I are merchants. So we might be working on things, that is not intented to be public. The theme I am working on since months is just for me. I would only reconsider with a clear approach from community, what a new theme needs and if it's financed in some ways.

@datakick Do you use any expires values? I followed some examples from google, but can't make it work. Google PageSpeed Insights always says, there aren't set. How would this done be correctly? location ~* \.(woff)$ { expires 300d; add_header Pragma "public"; add_header Cache-Control "public"; } I tried this one. I am using nginx and cloudflare. Not sure if cloudflare has any impact on that 🤔

Thats not the whole error message... Maybe it's simpler for you to post a screenshot.

@zen You offer webp support with your theme. Did this take any special settings or is it just about setting the config.xml file?

I don't know. I haven't used this module before. But IMO my code is 100% compatible with TB core. I guess only you can tell, if the new core can replace this module. I would be a little surprised, if you still need it as the new core will be quite powerful with features...

Just my thoughts on this: I can see the point for this feature and it can be useful for other merchants. But it's not a feature that was asked that often in the past. In addition it's not easy to implement at all... I know not a single "new" feature, that already exists. I guess you are talking about my "Multiple Features PR". As you see in my thread: multiple persons like it a lot. I think you still haven't understood, that I am not even part of the tb team. My PR is basically a "gift" that took me probably more than hundred hours. Why you are supporting this project? Ofc that's up to you, but all guys now using TB or PS 1.6 are fucked up in a few months, if development doesn't continue. I have asked it many times: which open source ecommerce software is better? Haven't got any names. Please also check github and the recent forum posts from @datakick. This is why you support it. He works so hard to hold this project on and make it even better. From github I would say that this software is much more alive than a year ago. 🙂

Yeah I was in some exchange with @zen , but we are following a different approach. He was basically updating an existing theme to modern standards. I start from stratch and implement a new system with components (basically I implement my own framework). I use Tailwindcss, which is no classical css framework. As it looks now, I won't need any JS Framework at all. I don't like to have a lot of dependencies. Today I have just coded my own blockcart functionality. It's not even a third of coding lines of the original blockcart. JavaScript advanced a lot since this modules/themes were created. If you want you can go to genzo.ch and see some progress. But only homepage and category pages are done to some extend.

I am basically doing that right now. The workload is sick, but I believe it's worth it (for me). My demo site feels so much better than my current shop 😏

After some further tests, you are right. jv80.se is faster (once you have loded the page fully). But the for the first call both are very slow. I would guess it is some caching setting. But you could turn on profiling in BO and check if it tells any interesting difference. Edit: even the homepage has double size 66.0 kB to 30.4kB. I don't know what this exactly means, but it clearly says this two pages are not as similair as you think... Check also console. There is a cookie issue on jv74.se that isnt on jv80.se.

Both feel slow to me. They arent the same. One loads ajaxSetPrice.php, which seems to be not super fast. But as I understand, that is the shop, that you define as fast (jv80.se).

I can understand this need. 😏 I need it myself somehow. It's on my "planned" list. But I won't integrate it soon. I first want to see the "basic" version be integrated. When this happened and works fine, I will improve it further 🙂

You should use the right technique. Design changes need to happen in themes and functional changes in core should happen with overrides. TBH I am no more sure, if overrding in modules is easily possible. Maybe this one works: https://build.prestashop.com/howtos/module/how-to-override-modules/ Another way is to take part in official development. If your PR are merged, you won't have the upgrade issue at all 🙂 But ofc not all things can be merged... Not upgrading can be very risky for security (see other topics these days).

Ofc not. But it might be helpful to know. Maybe the chain doesn't exist 1 to 1 in tb. Where does this information come from? I would guess, that this can only be true, if you are already infected...

Is there even one TB shop with an issue right now? 🤔