sklerotraficon

SOLVED:

Readding the API KEY in the Mailerlite Plugin Settings fetched the account_id again correctly, now the account_id is correctly set in the URL

• This reply was modified 1 year, 1 month ago by sklerotraficon.

Seems, there was an issue with the connectivity to mailerlite, resolving this gave back access to the forms list in the plugin, but now all Forms show:

404 ERROR
Looks like you got lost…

Sorry, the page you are looking for could be not found.

Inspecting the outgoing request when the plugin tries to get the form I can see that the “share” request goes to this url, where SOMEFORMID is the id to the form

https://dashboard.mailerlite.com/forms//SOMEFORMID/share

Where the actual form in the new mailerlite should look like:

https://dashboard.mailerlite.com/forms/SOMEOTHERID/SOMEFORMID/share

It seems, that SOMEOTHERID is missing in the Mailerlite Plugin Settings

BTW: Mailerlite Plugin Version

Version: 1.7.2

API key provided: Yes

API type: MailerLite

Popups enabled: Yes

Double opt-in enabled: No

Thank you for your reply, I also noticed a mistake on my part, the Google Measurement ID (G-*** consisting of Numbers and Letters) is not to be mistaken with the StreamId (which is purely numerical)

• This reply was modified 2 years, 2 months ago by sklerotraficon.

Hi Aert,
thank you for your reply.

I removed the Facebook js snippet from Complianz -> Integration -> ScriptCenter.

I just want to make sure, that removing the script snippet still is GDPR compliant, since browser side communication to facebook must not happen, but with user consent given in the Complianz Cookie Banner.

In the Facebook Dashboard I actually see only Browser events (for events setup PixelYourSite)

Is there anything else that should be set up ?

Thanks in advance

PS: Off-Topic, what should be set in the Complianz settings to prevent Mailerlite communication before User consent in the cookie banner (couldn’t find a hint in your help section) ?

I just readded the test_event_code in the PixelYourSite Facebook settings.

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

OK, Contact form submitted with reference to this thread.

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

Do you have another channel to share the url? If not I will post it here…

Tested with the Complianz Plugin disabled:

Same result, the event shows up as Browser Event (and not as a server event) without an EventId.

I’m very grateful for your support!

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

Since I added the specific event in th PixelYourSitePlugin Settings, I’m pretty sure, that it comes from there.

The only plugin I have enabled, that has some relation to the facebook pixel is the “Complianz” plugin, where the javascript script for the facebook pixel is added in the script center for the GDPR cookie consent banner. It basically blocks sending data to facebook via the Facebook pixel, if the user does not consent.
I don’t see, that this is causing the problem, since the event is actually tracked, but just not as a server event.

Thanks a lot again for your support!

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

Thank you for your support links,

I checked the “Test Events” section with the test code for server events, and the event does not show up here, but as a browser event (showing no Eventid, which is also a bit strange, isn’t it?).

Is there anything more I can try ?

Thanks again for Info

Thanks for the hint,

Disabling “Use Ajax when conversion API is enabled. Keep this option active if you use a cache” option did the trick.

What are the downsides of disabling this options ?

Thanks for your support!!

Sklerotraficon

The wp-admin folder contains a .htaccess file with basic auth to prevent access to this folder.

Since the Plugin triggers (or at least, with the plugin activated, this call is triggered) this url, of course the Basic Auth is activated.

Is there a way to keep the plugin from calling /wp-admin/admin-ajax.php ?

Thank you

One thing I did notice:

With the plugin enabled, when reloading the website, there goes one call to /wp-admin/admin-ajax.php (it keeps pending, until I hit the Cancel Button on the Basic Auth Interface, resulting in the request returning 401) which is not occuring with the disabled plugin.

Maybe this is a clue.

• This reply was modified 3 years, 4 months ago by sklerotraficon.

Thanks for your support,

I reactivated the plugin, checked the Head & Footer section in the plugin, and there is nothing added in these fields, I also deactivated the slide switch and saved the Settings.

To no prevail, the Basic Auth is still showing.

Then I deactivated the plugin and the Basic Auth is gone promptly…

Thanks again…

Sklerotraficon

Hi,

I checked the .htacces and the part with Basic Auth is not active (commented). Apart from that, there is no Basic Auth code for the Website.

Thanks again for hints…