scott001

Maybe the solution is for me to turn on strict mode on my current mariadb 10.1 using what I learned here: https://www.liquidweb.com/kb/how-to-disable-mysql-strict-mode/ and see if everything goes ok? My concern is that bad things could start happening to the db without me noticing right away. I was really hoping that the developers on this software could help with this more...who else should know this besides them? MariaDB is now the standard, and mysql support will end soon.

Any idea if strict mode in mysql is ok for Revive?

Is Revive Adserver compatible with MariaDB 10.2 ? I am currently running MariaDB 10.1, and see this warning when I go to upgrade: MariaDB enables "strict mode" by default as of version 10.2. Strict mode controls how MariaDB and MySQL handle invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MariaDB are compatible before upgrading. More information about strict mode is available here

Also, I discovered more files that contain my site's login info, which should probably also have at least 644 permissions. So we know about the config file which should probably be 444: var/www.mysite.com.conf.php But also in /var/cache are the following which contain your site's login info/passwords, which probably should be at least 644, if not 444: var/cache/localhost_admin_container.php var/cache/www.mysite.com_admin_container.php.meta var/cache/localhost_admin_container.php.meta Don't forget this one mentioned earlier: var/cache/www.mysite.com_admin_container.php

It's your software, why not just give the exact permissions we need to set with a publicly facing site??? I don't write your software, but as a user I need to know this. Your software is throwing errors--based on what? The site you send me to to fix those errors doesn't have the required information for me to fix those errors, yet you keep sending people there. PS - I would not set this file /var/cache/www.mydomin.com_admin_container.php to anything other than 644 or higher, perhaps even 444 if that would work. So why not just give your users the most conservative setting that will prevent the software from throwing the errors? That is all I am saying here. Why leave us to guess from dozens of possible permissions?

Here is what you currently say: The web server requires the ability to write to the following Revive Adserver directories and all files/directories under these locations: var var/cache var/plugins var/templates_compiled plugins www/admin/plugins www/images And here is what I believe it should say (note that I removed the var and plugins listings, because I don't think you mean those. I think you mean only the ones listed under those): The web server requires the ability to write to the following Revive Adserver directories and MOST files/directories under these locations (FOR APACHE THIS IS 777): var/cache (EXCEPT THE PHP FILES IN THERE, WHICH SHOULD BE 644) var/plugins var/templates_compiled www/admin/plugins www/images

For example in /var/cache I seethis file which contains my site login/password: www.mydomin.com_admin_container.php Your instructions are telling me to chmod this 777, right?

I know I seem like I am being a pain about this, but there are issues with what you say here: https://documentation.revive-adserver.com/display/DOCS/Directory+Permissions#DirectoryPermissions-WritePermissions For example, within my var/cache I see a cached version of my conf file, complete with passwords. If I 777 all files under /var 777, then it will be open to the world. I only ask that you be precise, so that my server, and perhaps others, don't get hacked. Due to this situation, I am still unclear which files need 777.

Ok, so no reply...again, are you saying that I need to chmod my configuration file to 777? Would this not open it up, including my passwords, to the world?

I certainly hope you can be more clear, as I keep seeing this error and can't believe that you'd have me 777 files like conf.

It doesn't seem safe to put 777 permissions on .htaccess and php files...but I will check. This can't be right, you would have me put 777 on my conf file??? It is in /var...

I correctly applied those permissions yesterday, 777 so those directories and their sub-directories, yet when I logged in today I got this error again: Error: File permission errors detected.These may impact the accurate delivery of your ads,See the debug.log file for the list of unwritable files I double checked, and the permissions are correct. Also, I checked the debug.log, which I emptied yesterday, and nothing is there. Any ideas?

Right now I have those directories all set to 644, but am getting this error: Error: File permission errors detected. These may impact the accurate delivery of your ads, See the debug.log file for the list of unwritable files Can you tell me the exact permissions they need? I thought 644 does allow the server to read and write, but apparently not. Do I need to allow the world to read and write with 777? Thank you in advance.

Here is what I found. My cronjob, which worked fine for years like this: 0 * * * * php -f /home/site/public_html/revivieadserver/maintenance/maintenance.php >/dev/null 2>&1 suddenly, at least to me anyway, needed to be like this: 0 * * * * php -f /home/site/public_html/revivieadserver/maintenance/maintenance.php localhost >/dev/null 2>&1 The mysql restarts may have been just a coincidence, and my server auto-updated and installed a new version of cpanel or something else, but something changes and now I must include "localhost" in the cronjob. I hope this helps someone else!

Last night I did some work on my server and had to restart mysql several times. I don't believe that any changes I made would break the maintenance cronjob--I checked and it is running on schedule, but no stats are being recorded. I suspect that the cache is somehow corrupted because I may have restarted mysql during a maintenance run. Is there a way for me to flush the cache in case this is the cause? Any ideas about how to get this fixed? Thank you in advance! Just in case the performance changes I made last night to my.cnf could somehow affect this, here is what I did: changed thread_cache_size from 128 to 256 Since I upgraded to MariaDB a couple of months ago I read that these are important for speed, so I added them to the my.cnf: host_cache_size=256 (default is 128) aria_pagecache_buffer_size=256M (default is 128)

I think I know what is going on @fede_2110. In your Google Adsense account go to My Ads > Content > Auto Ads. Then on the right click the pen (change your global settings), and turn off the "Text and Display Ads" setting. This setting allows google to put its ads where it wants to if you have this code in your page. Keep in mind that this may lower your earning, but you will be able to control where the ads go.

I've been unable to get any 3rd party ads to display, including Google Adsense ads. I've used this software since it was PHPAdsNew, so am well-versed in how to use it. I've gone through your guide in detail, but no matter what I do it serves blank white space instead of ads. Interestingly Google Adwords campaigns that I made years ago are working fine, just not any new campaigns that I create. I noticed that the old working Google Adsense banner fields look different, for example: and the new one is missing the Banner link area fields: Any help would be highly appreciated! PS - The ads do display fine when embedded directly into a web page, just not when serving with Revive Adserver.

I did some searching and probably missed this somewhere, but... 1) Can you use the same asynch banner tag on the same page? Will it properly count the impressions served by each, and will it count clicks? 2) I don't care to register at github to report this as a bug, but I may have found a bug. I noticed that if I use the asynch tag to call a zone that has only one single advertiser, so that advertiser has 100% probability, it will not serve the ad. However, if I use any of the others, like iframe, java, etc., it will serve the ad. Not sure why, or if it is a but, but I suspect it is a bug. Thank you for any help!

FYI: I just switched back to IFrame calls, after all, my advertisers want clicks! I'll report any changes in CTR. I agree that a side by side would be interesting, but not sure I have time to do it. Although not on topic, one issue I also have is that some of my advertisers have complained that the clicks I am recording are not showing up at all in google analytics data for their sites. After doing some research I've discovered that the referrer is not sent by certain browsers when a link goes from an https secure site like mine, to an http non-secure site like most of my advertisers. Does this sound right to you? One big job I am always facing is growing skepticism on the views and clicks (especially the clicks) that Revive is showing, but some of my advertisers claim isn't happening. Is there any help you can offer me to overcome those objections and explain discrepancies in click data that is recorded?

I am running a cpanel apache mysql configuration. Under the latest cpanel you can run PHP per site, so you could set this in your control panel and run PHP 7 on your site. In my case, I wanted it to run within a directory, so I added this to the root .htaccess file for my Revivie Adserver site: <IfModule mime_module>AddType application/x-httpd-ea-php70 .php .php7 .phtml</IfModule> I then edited the main configuration file from: [database] type=mysql To: [database] type=mysqli

That did the trick, thank you. So I could not find a way to edit the DB settings withing the admin area, but did change it directly in the config file from "mysql" to "mysqli". l can now get into admin, and it looks like the stats are updating. Thank you!

I will try this again soon and post what I find. Since I am running PHP 7 on a per directory basis, I will try restarting the server when I switch it, because I did not do that last time.

Unfortunately it does not work. The admin area doesn't seem to function...the admin login page does not load. Additionally, the statistics stop being collected, so the hourly cron job does not seem to work. The ads do show, but the app is not PHP 7 compatible.

Does anyone know why PHP 7.0 isn't working with Revive Adserver v4.0.1?

Currently my server is running PHP 5.6.30 as the default, but PHP 7 is also installed. I am trying to force Rvive Adserver to run under PHP 7, and I've tried adding this code to a new .htaccess file in the root ad server's directory, in my case it is /adserv : <IfModule mime_module>AddType application/x-httpd-ea-php70 .php .php7 .phtml</IfModule> This configuration works fine for a forum which I have in a different directory on the same domain, but is not working for Revive Adserver--the ads stop running. Am I putting this file in the correct location, the root for Ad Server, or should it go somewhere else, for example /var ? It is possible that I don't have some required extension installed for PHP 7 that is needed for Revive, is there a list somewhere of those? Any help would be appreciated.