wakabayashi

I just don't think its a core issue, since we dont have it and @30knees also not. I would try two things: - disable overrides - do the same tests on a clean tb installation

@30knees just refresh the page and it looks normal again...

@30knees I can confirm, that this sometimes happens. I don't know exactly when...

Do you have some overrides? Cause in general this is working for me...

I use asm, so I cant tell. What is normal: the shipping cost never adjust! I would like to have it, but its not there...

Is there any error? to me the src looks not very normal. but not sure if it's really an issue.

Oh I just tried to install this module on my testsite. It doesn't even install for me correctly... Didn't expect that :O

What do you mean with a floating social share? Can you show an example?

Happy New Year guys!

I think it could be some bots or something... @lesley knows surely better. What I can say: I have entries in Google Analytics from urls I also don't have at all...

@CoffeeGuy I was just on your site and clicked a bit around. I got no error at all. Seems to work good. Hopefully "Swiss Miss Hot Chocolate" tastes as good as it sounds :D

@Purity you are right, sorry! I haven't read the whole thread carefully. But on his site is still elasticsearch...

@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...