lesley

The exportation and importation of data is a pipe dream at best. It really does highlight how uninformed the people that wrote the law are on technological matters though. Every shop saves a different amount of data and has different password storage, without a set format this is something that is going to be dead and not useful. For the export itself, we will most likely add a button to the user account that will allow for this, it seems like the easiest thing to do.

Simple data collection laws should be able to be understood by the people that collect data, right?

Then it is a shitty law that is against the interests of the people. It is made to create an artificial market of people that understand the law. This quite literally makes it the legal dark ages.

We have been, but if you go through all the threads where we are offered information, you will see other people in the EU saying "No we don't need that" or "I don't read it to mean that". This makes it hard to know who to follow.

Meta tags are hit or miss to be honest. There is no SEO value what so ever in a meta description. The title is generally indexed, but Google changes them on the fly as well. They sometimes change them to align more with the term being searched to improve the click-through rate.

I think people are actually missing our point of frustration. We have several threads dealing with what changes we need to make in the EU, but no one that lives in the EU agrees can agree on what needs to be changed. This is where the problem comes in. We have no good information about what exactly we need to do. The laws themselves are very vague from my reading. I see terms like "unless the information is needed for statistical purposes". To me, that covers every piece of information collected.

Looks like I forgot to push it to the api feed. It should be there soon, I just added it.

Mail ones are hard to diagnose. There is something in some mail log telling why the mail is not sent though. It could be in the server error log or the server mail log. I would start with those.

Check the server logs, it should tell you what the error is. I am betting it is template specific.

As a note we have added a paypal donation button to the side column of the blog and the blog posts, https://thirtybees.com/blog/ So if patreon was holding anyone back, we have that option now.

Did you make sure you copied over the admin directory? You needed to rename it from admin-dev

I have come across that before also. What would you think about us detecting that warning and changing it automatically?

@datakick did you just change the cookie encryption method to fix the last error?

Are the permissions set correctly on the module?

Are they using a connector or just the web service?

Awesome, you should add the module to the thirty bees store.

It hard to see if a shop is actually being used without gathering transactional information. Its something we aren't wanting to gather really.

I do not think very accurate currently. We are toying with the idea of sending data to them directly on install though.

Since we do not collect information after the installation it is hard to tell. The downside of complying with EU laws and respecting privacy.

That is true. We are seeing between 50-100 installs a day and it is growing every month. If you support it now, there could be more features by the time you launch into production, more features are always better :-)

I would say at least 3k. The indexer is solid, but the front end language used in the template is not compatible with thirty bees, so the whole front end would need to be changed.

Delete it from your dev shop, that should fix the issue.

That module is a mess to be honest. The front end needs to be rewritten in a more stable slower smarty. It is also limited a bit in currencies and multi-shop. It would cost a few thousand to fix the module so it would be ready for wide release. We have the module forked over to our repo privately, we just want Algolia or someone else to pay for it since they will be getting all the gain for it.

Honestly I do not know. We did the elastic module through crowdfunding, but they are an opensource company. Algolia offers a paid solution, so I did approach both the cofounder and one of the other higher ups at Algolia about us making an integration. I was not answered back. I would suggest mailing them and asking them to help fund one.

I have not heard of that issue. You might ask their support.