CMSB v3.54 Released - October 29, 2020

Hi Dave,

Sure, sorry about that. If you tick the "hide php errors" checkbox on and click save the security tip still shows for it. If you refresh or hit save again it goes away. Then if you uncheck the "hide php errors" checkbox and click save the security tip won't show. If you refresh or hit save again it does show.

Thanks!

Steve

Hi,

I might be missing something, but I have a list field that I have been doing the same thing in older versions that don't seem to work now.

I'm using "Get options from MYSQL query" and when I use the WHERE query, I get "There was an error sending the request! (403 error)" and cannot save.

SELECT num, name
FROM `<?php echo $TABLE_PREFIX ?>json_ld_properties`
WHERE markup_type = '<?php echo $ESCAPED_FILTER_VALUE;?>type2'

When I get rid of the WHERE, it works.

Is there any changes I should make?

Thanks in advance,

Hiroko

Hi,

I finally found out why my "Get options from MYSQL query" setting couldn't be saved.

The server had a WAF setting (Web Application Firewall) that detects access to SQL statements. I turned it off, and I was able to save.

There was also a WAF setting that detects 'kill, ftp, mail, ping, ls' commands that will case 501 error on saving record for Newsletter Builder.

Sorry if I took your time. 

In case someone has the same problem, you might want to check the server settings.

Best,

Hiroko

Hi Dave,

I posted a question/suggestion on this same thread on October 30. I do not see a reply and am hoping for an answer on that referenced error flag being thrown because CMSB may not be recognizing equality between versions of MySQL and MariaDB...if my neophyte brain understands this correctly. 

Thank you kindly.

Hi Guys, 

The MariaDB error can safely be ignored for now.  We're going to update that for the next release.  It's because the MySQL and MariaDB version numbers don't match up.

You can comment out that error for now if needed or just ignore it.  Let me know if you need a patch and I'll point you to the file and line.

Thanks Dave!

Which file and line? 

I've just updated a site from v3.53 to v3.54.  It has background tasks running, set to run every minutes.

I've noticed that each time it runs, it's changing the 'localhost' value in settings.dat.php to be '127.0.0.1' (see line 56 of database_functions.php) which breaks the connection on this site.  I'm not sure why 127.0.0.1 isn't working on the server but I've had to comment this line out to prevent it from breaking as soon as I change the setting back.

Is there a reason why it's trying to update 'localhost' to '127.0.0.1'?

Thanks, Paul.

Hi Paul, 

Yea, it was a workaround to fix an issue where some linux servers couldn't connect to mysql with ssl enabled with localhost as the hostname.  

When you ping localhost on your server what IP is it returning?