Stephanie

Answering to myself : replacing localhost by 127.0.0.1 in the database config section did the trick and it works

Installed 5.3.0, everything went fine. Server is under 7.4.22 / Apache 2.4.46 / MySQL 5.7 Everything works fine under PHP 7, switching to PHP8 leads to an error stating that it's impossible to connect to the database.

You need to modify the delivery file you use (asyncspc.php or afr.php) Search for : $imageTag = "$clickTag<img src='".htmlspecialchars($imageUrl, ENT_QUOTES)."' width='$width' height='$height' alt='$alt' title='$alt' border='0'$imgStatus />$clickTagEnd"; change it to : $imageTag = "$clickTag<img src='".htmlspecialchars($imageUrl, ENT_QUOTES)."' width='$width' height='$height' loading='lazy' alt='$alt' title='$alt' border='0'$imgStatus />$clickTagEnd";

Hi, I duplicated the database before the upgrade. Everything went fine, but by simply copying the database, it's getting bigger every time. As an example, our database was 640 MB before copy, the copy version with exactly the same data is now 1.55 GB. 2 tables seems to be mainly affected, see below : Before : rv_data_summary_ad_hourly - 814 639 entries - 128.3 MB rv_data_summary_ad_zone_assoc - 1 604 550 entries - 342.6 MB After : rv_data_summary_ad_hourly - 2 307 907 entries - 366.5 MB rv_data_summary_ad_zone_assoc - 3 568 792 entries - 804 MB It occurs during every update, over time it will go to disaster any idea why this happens and how to clean those two tables ?

"the system wanted me to specify the path the previous installation", you should have paid attention to this step As a result, you did not properly update your plugins because the path (absolute path is needed) you provided was wrong and the XML files for plugins could not be located properly. Which led to the problem you mention in some other topic.

Plugins are inside of the zip archive you downloaded to update, you can update manually but you should have updated plugins during the global adserver update.

You use old version of the plugin, it has since been updated to insert your licence key. Update your plugin to 1.1.0.

Just use custom in the menu and then use * character for width / height

We use this way : We create delivery rules sets in our preferences folder, where we determine which countries are targeted by groups. Then we apply those rules to each banner. You need to check if the database is there, in the var/plugins/rvMaxMindGeoIP2 folder Get your free licence from Maxmind, input the licence data into the dedicated field of plugin management interface

I think Revive can only automatically download one type of database (City one), hence the .lock file during the download of an updated version. I don't think that you can and need to use another tape of geo database in the folder. To use thi geo function, I create Geo delivery rules sets in my preferences interface and then apply them to banners. I don't use the Geo rules directly from the banner distribution options.

Did you enter your Maxmind license key in the plugin settings ?

Did you check your stats ? do they show impressions on geolocated ads ? did you apply rules correctly to the campaign / ad ? We use 5.0.4 and geotargeting, no issue, it works. I don't think you need any kind of "plugins_repo" folder.

This new version is about the Samesite Cookie issue, as per changelog : Added support for the SameSite cookie directive which will soon be required by browsers in order to allow 3rd party cookies. I upgraded but I still get 4 warnings in the Chrome console when checking the websites were we display ads from our server : A cookie associated with a cross-site resource at our-adserver/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032. Is it still supposed to happen ?

You look in the wrong place, not the /plugins folder the /etc/plugins folder, it's there.

We do, what's your issue ?