lesley

Do this, look in your server logs, it is organized by time / date and ip addresses, search the times and ip addresses to see what pages they are landing on. Then post some of those back here.

I did not put blame on anyone. I offered to help. I took time, did a fresh installation to try to reproduce the problem. I could not reproduce the problem. So I asked for access so I could help you solve the problem. Then you acted all weird like you have super secret customer data. I am sorry, but you don't. I manage close to 1000 ecommerce sites, you don't have anything I haven't seen before or any information I am not insured against if there is a breach because of me. Just imagine things from my shoes. If I bought a product from you (which you haven't bought anything from us) and said there was a problem with it, wouldn't you want me to give you access to the problem so you could verify? Then you could handle the problem. But what if I refused to give you access to the product? How would you solve it?

Great, good luck over there, I will close your accounts here. Honestly 99% of people in our community make working with thirty bees a pleasure. People like you really gut punch us and need to be weeded out from our community. Sure there are bugs, there are bugs in any software package with over 1 million lines of code. We don't actively try to make bugs, we actively try to fix them. The actual developers are here, in the forums, trying to help fix them. Other packages developers do not even go to the forums and if you want a fix by them they charge you. Pick your road.

It works in a vanilla 1.0.8 installation that has been upgraded from 1.0.7. I tried to check your installation, but you would not give access. I don't know what to tell you at this point.

@violinparts The best I can tell you is good luck. I offered to help. As a fyi, I installed a 1.0.7 shop, ran the upgrade to 1.0.8, added a few products, killed the search index and re-indexed, and turned instant search on. It works for me with an out of the box installation, http://thirtybees-200675-702960.cloudwaysapps.com/ My best guess would be to try to disable overrides on the performance page and see if that helps.

I have moved these posts to this topic as a fyi.

I would suggest hiring a developer that you trust to look into the issue then. No one will likely be able to guess the problem without access.

Can you PM me back office access, I want to check it out. I have not seen this issue on other shops.

Uninstall it and delete it, then also make sure that the search is indexed in thirty bees.

Can we make separate topics for these issues? It would be best for organizing things. Does the search work when elastic is uninstalled? Have you made sure to index the search in thirty bees?

No problem. I don't know if you are aware, but there are modules like this for most major platforms. What they expect is that you enter things in your shop, then they can push the products to the platforms. That way you do not have to enter things 2 or more times, you can just have one site to manage all of your listings.

There are ebay modules like this one, https://store.thirtybees.com/shop-modules/administration/thirtybees-ebay-intergration-prestabay?search_query=ebay&results=3 that should sync the inventory.

This is actually an error code that can present from mysql being throttled too. Instead of just saying mysql has gone away, or the connection limit has been reached, this error can show as well.

@datakick this does raise a good point though. I do tend to fall on the side of not breaking shops, but you are very right in that we lose the ability to track and trace errors too. What about a data collection method? What if we just started logging all fatal errors that are catchable in a phone home type server? Just about every executable software company does that these days.

This seems like another law that only big companies will follow, or companies in other EU states. I cannot see US/CA/MX based companies that have no EU presence even be remotely concerned with this.

Hmm, Do you know if your host supports utf for mysql? You might open a ticket with them and ask.

That issue is because of things on paypals side. I had it the other day as well.

The normal error reporting should still be working, nothing was changed about that.

Ok, I have debugged this without being able to see the error message. The fix I have is not elegant, so I want to talk to @Traumflug and @datakick about it before I make a patch to the tbupdater module.

I think that solution will work, I have it on several live sites, I am planning on adding it to the module with a bit more testing.

Can you try replacing your /modules/paypal/classes/paypalrestapi.php with the contents of this gist and test, https://gist.github.com/Dh42/09eb812b0c5d7f8d7cfdc1a8e3c28c98

If you want to pm me your logins I can take a look at it and see what is going wrong.

Can you create a php info file in your web space and see what is returned as the php version. 5.6 should be fine.

What error are you getting? thirty bees is compatible with 5.6 -> 7.2

Can you try replacing your /modules/paypal/classes/paypalrestapi.php with the contents of this gist and test, https://gist.github.com/Dh42/09eb812b0c5d7f8d7cfdc1a8e3c28c98