Jan Reidel

@dizzyatinnocraft I have set the MaxMind license key in the settings. Downloading works and the monthly cron task works too. Up to version 5.1.7 everything worked fine. After activation of the plugin an initial download happened and afterwards the monthly cron task.

When I activate version 5.2.0 I see in my MaxMind account in the download history that every few minutes a download happens starting at the time the plugin was activated that goes on until the daily download limit of 30 is hit.

Unfortunately the system report contains a lot of sensitive data, so I can’t post a full version of it in a public forum. But I have some interesting lines out of it regarding the GeoIP DB update.

After activation of version 5.1.7 I see the following entry:

Update GeoIP DB: Next run: 2025-02-07 14:10:46 (2 Tage 4 Stunden) ( Last started: 2025-02-05 09:54:16 (-1 Minuten 3s). Last ended: 2025-02-05 09:54:19 (-1 Minuten 0s). Interval: matomo_monthly)

That looks good to me, as the activation was around 09:54 and the next update is scheduled in a few days which should be inline with the monthly cron task.

After activation of version 5.2.0 I see the following entries:

Update GeoIP DB: Next run: 2025-02-05 09:57:22 (34 Sek.) ( Last started: 2025-02-05 09:54:16 (-2 Minuten 32s). Last ended: 2025-02-05 09:54:19 (-2 Minuten 29s). Interval: matomo_monthly)

Update GeoIP DB: Next run: 2025-02-05 09:58:29 (23 Sek.) ( Last started: 2025-02-05 09:57:49 (-17 Sek.). Last ended: 2025-02-05 09:57:51 (-15 Sek.). Interval: matomo_monthly)

Update GeoIP DB: Next run: 2025-02-05 09:59:51 (-7 Sek.) ( Last started: 2025-02-05 09:59:11 (-47 Sek.). Last ended: 2025-02-05 09:59:14 (-44 Sek.). Interval: matomo_monthly)

Update GeoIP DB: Next run: 2025-02-05 10:00:43 (-10 Sek.) ( Last started: 2025-02-05 09:59:58 (-55 Sek.). Last ended: 2025-02-05 10:00:01 (-52 Sek.). Interval: matomo_monthly)

Update GeoIP DB: Next run: 2025-02-05 10:01:33 (-6 Sek.) ( Last started: 2025-02-05 10:00:53 (-46 Sek.). Last ended: 2025-02-05 10:00:56 (-43 Sek.). Interval: matomo_monthly)

I took the system report immediately after activation before the initial download happened. What you can see from the second entry on is that approx. every minute a new download is scheduled. This goes on until the daily download limit is hit.

Hello @michael-travan ,

looks good, works as expected. Thank you.

Well, I use it in both service emails as well as newsletters.

It work in the past e.g. in the double-opt-in email where I put in the timestamp of subscription to document when the subscription attempt happened.

I also use it in a newsletter template in the copyright section to get the year.

I assume, these are the common cases for the application of this tag and that it is used by many users. But when you say that this isn’t supported anymore, I must go down another road and implement it with a shortcode myself.

These are the shortcodes I used to create a custom form which contains the same field like the standard form.

[newsletter_profile]
[newsletter_profile_field name="email"/]
[newsletter_profile_field name="first_name"/]
[/newsletter_profile]

This is the form generated by the shortcodes.

<form action="#" method="post">
	<input type="hidden" name="nk" value="0-0">
	<div class="tnp-field tnp-field-email">
		<label>E-Mail</label>
		<input class="tnp-email" type="text" name="ne" required="" value="[email protected]">
	</div>
	<div class="tnp-field tnp-field-firstname">
		<label>Vorname</label>
		<input class="tnp-firstname" type="text" name="nn" value="John">
	</div>
	<div class="tnp-field tnp-field-button">
		<input class="tnp-submit" type="submit" value="Profil speichern">
	</div>
</form>

This is the shortcode for the standard form with just email and firstname configured.

[newsletter_profile /]

This is the standard form generated by the shortcode.

<form action="https://localhost/www.mydomain.de/?na=ps" method="post">
	<input type="hidden" name="nk" value="0-0">
	<div class="tnp-field tnp-field-email">
		<label>E-Mail</label>
		<input class="tnp-email" type="text" name="ne" required="" value="[email protected]">
	</div>
	<div class="tnp-field tnp-field-firstname">
		<label>Vorname</label>
		<input class="tnp-firstname" type="text" name="nn" value="John">
	</div>
	<div class="tnp-field tnp-field-button">
		<input class="tnp-submit" type="submit" value="Profil speichern">
	</div>
</form>

Both forms look pretty much the same except the form action in row 1. The standard form has the correct URL while the custom form has just the hashtag symbol (#) as the form action.

Clicking on the profile save button results in case of the standard form in saving the field values while in case of the custom form the values are just cleared from the field and are not saved.

I’m sorry, I have no live version but I can post the generated HTML of that form if it helps?

Right, I see just the tag and it is not replaced by the actual date.