te_taipo

Thanks for the reported errors.

Try the latest update 3.3.1. Let me know how that goes.

• This reply was modified 5 months ago by te_taipo.

Try the latest update, and thanks for reporting this.

All good

I have had a look at this error and cannot see how this script could be the cause. Pareto Security does not try to define DB_CHARSET nor does it try to include the wp-config.php file or any class that would result in it being included again (that could potentially raise this error).

When did this error first appear, and was there a plugin or theme that was added about that time?

Thanks for that. Try the latest release and let me know how it goes.

The only thing I can put this down to is that there are some cron jobs being run where PHP runs via command line, and in those instances the _SERVER global array is not being propagated fully. That is the only legitimate condition where that array may be empty, so it is ok then to add in the ISSET bypass, or in the remote address, report the server address instead. Latest update is out now. Let me know how this goes, and thanks again for reporting these issues.

Got that thanks, you can delete that now if you like

On the face of it, using isset would be the easy fix, but in fact all that would be doing if basic PHP globals like SERVER_ADDR are not set, is disabling the script.

If you are able to, can you upload a simple test file to your website, example test123.php and include the following code:

<?php
print_r( $_SERVER );
?>

If you could then copy the output of that from the view source of your browser thanks. Need to take a look at what is going on. The webserver should populate the _SERVER array with all of the standard variables, but for some reason your configuration is not doing so.

• This reply was modified 1 year, 9 months ago by te_taipo.

Thanks for that, fixed in the latest update released 5 minutes ago.

That is a rather strange issue. The line numbers 2948 and 2379 do not correlate to any code in pareto_functions.php that could be causing that.

Couple of questions:
1. What webserver are you using, and what version of PHP
2. Has your webhost updated your webserver lately?

Now added.

Thanks for that, fixed now in latest update.

New update should fix this issue. Thanks again for reporting these.

Thanks for that. It’s an error that occurs when WordPress crontab is called, or for example if pareto security is used on a non-wordpress website. It will be fixed in the next update in a week or so.

Update released, let me know how this goes.