wakabayashi

@Purity he is using elasticsearch and you are probably (?) using the normal search. But his reaction is not legitimate: 1. lesley offered help, but he doesn't want to give access 2. he is using elasticsearch, which needs quite a bit of knowledge to handle it. 3. he "threats" to go back to ps. after all since when does ps offer elasticsearch?

Lesley is ofc right. The hook called "displayHeader" is not really visual stuff. It's the part, which will be in html between tags.

@movieseals these are just notices. Are you sure your shop was running in debug mode, when you used 1.0.7? Maybe the difference is just, that you switched debug mode on...

@purity said in thirty bees getting better and better: release 1.0.8: Not sure why this needs said again, but if you are updating your shop, you should take a backup and/or test the update on a non-live copy of your site. There should never be a time where you update your site and then need to frantically ask for help to get your site back up. If you have problems, you should simply roll back and await a fix. You're liable to run into such problems updating even a CMS like WordPress... Completly agree. But was too tired to write, since it was said like 1000 times before...

I am not aware of this new key, but you could try to out comment: die($e->displayMessage());

@traumflug said in thirty bees getting better and better: release 1.0.8: The fix for FPC is: turn it off. TBH, I'm quite a bit surprised to see so many people making a headache about this totally optional Full Page Cache, while there are no less than 160 known bugs filed (not counting enhancement requests), some of which cause a shop to display plain wrong data to the customer. Did I hear here "Doesn't matter what a customer sees, as long as he sees this fast" ? I hope not. For me, correctness counts a lot more than a few percent performance. I don't think its about full page cache. It seems to be php 7.2 issue.

It seems that a lot of cms have such issues. I guess you are using php 7.2 right?

Are you sure debug mode is on? Do you have something in logs on your server?

I can understand! I guess it's only possible once this project is in 1.1 stage. It will be quite a big work... I have coded a similair thing in an internal module. It took me weeks to synchronize all stocks correct. But my module works a bit different, since technically we create normal products for packs.

You could write a little module.

I completly agree on your points. But there hasn't been any change in tb compared to ps.

@alwayspaws said in Welcome to all our new Team Members. We appreciate you!: Welcome, everyone! I’ve been away for a while. I’ll try to visit more often. I miss my friends. Nice to see you here again! :winking_face:

@rubben1985 problems will come up, once you switch from mailchimp to another provider...

But ok doesn't seem to be important. thx @datakick for fixing it!

@dosbiner thanks a lot. I am already at the same line of code :D but somehow I too dumb to understand the fix. Why was the variable been renamed?

@30knees have you fixed this issue somehow? It is still there in 1.0.7.

Thats a great idea!

For this I have no idea and I think you only have a chance, if you contact the developer...

I am confused about this thread. Have you done the migration trough the official migrator module?

I use the mailchimp module, but not opt-in. I have removed it from the theme... So I can't say either.

@traumflug said in Migrating from 1.0.7 to clean 1.0.7: It's an ongoing process, but thirty bees slowly learns to clean its self. For example, the upcoming 1.0.8 release will fix some back office menu entries which are typically wrong in migrated shops. It'll also learn to detect obsolete files. I love this idea of self cleaning :)

@haylau yes I completly agree.

For example the biggest clothes store here, is doing it: https://www.zalando.ch/herrenbekleidung/ You get just a better impression, if you like a product, without navigation forward an backward. When you have thoundsands of products. Nobody will watch them all on product page...

@briljander said in Products to test site?: @wakabayashi Do you mean update in database in customer table ? Yes. I just do this in case something goes wrong. I don't want my customers to get any email from my testsite ;)

I always clone my whole shop. with database. Then you have all the info. Then I change all the emails of customer, so nothing can go wrong, while testing...