fishheadcode

Sorry, forgot to answer.

The thing is: When there are rounding errors because of different currencies, please test this. Not every store has dollars. This then is a plugin bug and shall not be the users problem, but yours which needs to be fixed. I mean i was using free. Imagine someone buys it, is this the same answer then? That would be awful.

Anyway i now use a different, own, solution for that. But you shall anyway test this on a site with euros as example.

Its then not this “$ 1.23” but “1,23 €”. I think its the formating (comma and where the currency is placed) which causes it then. Also there are settings for this directly in wordpress and functions in wordpress and also functions to get the raw unformatted value, which you anyway shall use. So this should not be a problem at all

How shall i give more details than i already wrote? We use the free plugin, thats why i am writing here.

We want to give: 5% commission
Setup in backend: 95% stays on admin side
Product price brutto: 55€
Product price net: 46.50€
Awaited commission: 2.33€
Commission actually calculated by your script: -0.01

Why is it -0.01 and not 2.33€?

My only question is: HOW does your script calculates with the end result of -0.01 so i can set it up correctly.
From my perspective your calculation is horribly wrong in this case.
I know we “misuse” it because we are not a marketplace but want to use it for commissions of our artists, but anyway it shall work with 95:5 percent.

Same here. In the docs there is text at point 5: “Complete the?[Problem Internal Link]?(install all the required plugins if any).”

What was the link exactly? There seems to be missing someone. And YES its correctly setup @Fluxbuilder. I have a shop which is running years and it shows attributes and variants. I know how them work. The problem is NOT the attributes. Please check docs and tell us whats wrong.

@hammat24 i also opened a ticket for that, when i got feedback i will write here.

OK thats what i kind of thought already. But is it planned? It would be very helpful.

One more thing, i must correct myself. Or maybe not, not 100% sure, because GDPR…

Brevo now said, that DOI is NOT required in the EU.
Also the GDPR site says this (somehow, and somehow also not)

ChatGPT(4) says, its not enough and you need a DOI to be 100% safe.

Also a my customer – who studied law – is not sure what is right (i sent him the official GDPR site)

So, no one knows whats correct, like always with GDPR.

We leave it now as it is.
But i still think its some kind of worthy to research this and maybe also built this into your plugin.

The documentation does not seem to be that big, it seems like one just need to create a new customer via new \SendinBlue\Client\Model\CreateDoiContact().

I have not took a look into your plugin, but i think you will make it similar to this.
So maybe the solution is not as difficult as it seems now, maybe the config around takes more time.

I am out for now, if you still have ideas or questions, tell me.
Otherwise close it ??

Hi!

I got feedback now and in the end its something on your plugin, but let me explain ??

This is the last message i got from the support
“this placeholder works only for our own plugins/forms or third party integration which are using our dedicated DOI process. Contact Form 7 does not support our DOI Process. Therefore, the links do not work.
Feel free to forward this to Contact Form 7.
?
You would need to use our own sign-up forms or find an integration which is supporting our DOI process.”

So what you support is the consent itself, i now understand the difference. But NOT the DOI (double opt-in) process.

But this is very important for the EU because of the GDPR.
Can you have a look at this and tell me if there maybe is a an estimate date.
I myself would rate this as critical, if this was mine ticket, but of course it isnt ??

If possible, please just tell me if that would make sense to you, if you could adopt this as ticket and how the plans are – if you can.

Meanwhile i will search for a solution, maybe via hooks or something, idk.

Can you maybe tell me where the integration for sendinblue is? Especially sending to sendinblue? if there are some api params, i would add them myself.

Now where we are in the discussion i realize that it maybe makes no sense. Do you have ANY possibility of “transfering” a parameter like “doubleoptin”?

If not it might be a brevo topic.
I think i just have the wrong guy in the emails then.
I just wrote them and wait for feedback from their site also.

I will keep you updated then.
Maybe indeed it has to be something todo with your plugin, but now i think it has not.
But maybe you can check it anyway if you see something when sending the consent to brevo? ??

the newsletter confirmation newsletter which is sent when users first must approve again in an email that they want to join the newsletter. just go on the site of the customer, go to the footer and test it (with both checkboxes). you will receive a confirmation email in which you can NOT click the link.

Since the template is defined correctly on brevo (nothing changed), it cant be brevos fault. there is a link with a placeholder

<a href="{{ doubleoptin }}" target="_blank" style="color:#ffffff;font-size:14px;text-decoration:none;line-height:24px;width:100%;">Yes, subscribe me to this list</a>

Your integration with Brevo / Sendinblue.
This here: https://contactform7.com/sendinblue-integration/

Just try it yourself on a clean install. Build a formular with a consent (see “Privacy considerations” in your docs) and you will see that there is no link in the mail from brevo.

Brevo says everything is fine from their side, the plugin is not sending the correct data. I think maybe some param is not sent to brevo, i am not sure. But Brevo seems pretty sure that this is more of a CF7 problem.

Its Avada, using child theme. Version 7.8.2

Hi! That was fast ??

You can see here, i made a screen
https://pasteboard.co/6jJcRwikbV71.png

Hi Katherine,

yeah, it definitely can be set up.
Also like i already said there is a default woocommerce field for this.
The problem is that your plugin does not fills this field.

I will write the support and refer to this thread ??

@listerine28 the solution at last was to install an old version of the theme which was compatible.

head over to https://de.www.ads-software.com/themes/neve/ (this is the german version)

you can download it then via https://downloads.www.ads-software.com/theme/neve.2.10.0.zip for v2.10.0.

Simply change the version and try out which version fits your wordpress installation. try it until it works.

@fareedkhan12 you simply cant answer the same in every ticket. This is NOT the solution… i think a developer knows howto install a plugin and activate it. So, no, this wont help…

I Also got the same problem.
Downloaded neve, installed the plugin (and yes, activated it) and nothing works. Tested it on Windows and Linux, XAMPP and LAMPP environment, both times php xml installed and activated.

So now i cant use the theme. Also in the backend all options are json encoded in a textfield instead of a dropdown or multiple dropdowns.

This happens on an existing site and a fresh install.

Also got the same problem.
Downloaded neve, installed the plugin (and yes, activated it) and nothing works. Tested it on Windows and Linux, XAMPP and LAMPP environment, both times php xml installed and activated.

So now i cant use the theme. Also in the backend all options are json encoded in a textfield instead of a dropdown or multiple dropdowns.

This happens on an existing site and a fresh install.

• This reply was modified 3 years, 11 months ago by fishheadcode.