Plugin Author
Eli
(@scheeeli)
Check the Error Console or Element Inspector in your browser to see if there are any JavaScript Errors on the page. You could also try another browser or you could look int he error_log files to see if there are any errors triggered when you run the Complete Scan.
Are the Quick Scans are working fine on those sites?
Using element inspection -> console -> I got these errors ‘SyntaxError: expected expression, got ‘<‘ ‘
I wonder if that help.. .:)
When I pressed quick scan, it tries to load a new page (loading within top tab) and goes into error with varnish cache server error.
Plugin Author
Eli
(@scheeeli)
The heart of the Complete Scan is driven by dynamic ajax calls in JavaScript. It sounds like those scripts are outputting HTML that is likely injected by the malware that is affecting those sites.
Is would be best if you could disable all caching, then maybe the Quick Scan would work and once you have removed the threat that is causing the JavaScript error you could run the Complete Scan again.
In the element inspector you could examine the JavaScript output that is causing that Syntax Error ad look for the ‘<‘ (which is probably an HTML tag) and that might gibe us some more clues about how to fix this.
So i turned off varnish
did quick scan on all three = core, plugins, themes = all came out clean
Then click ‘complete scan’
Same result where it stays at 0…. 🙁
any thoughts?
Plugin Author
Eli
(@scheeeli)
It sounds like the dynamic ajax scripts are outputting HTML that is affecting the scan. Use the element inspector in your browser to examine the JavaScript output that is causing that Syntax Error and look for the ‘<‘ (which is probably an HTML tag). That might give us some more clues about how to fix this.
Below is two error I got and when I clicked on admin-ajax.php -> I got below result. It’s not all of it but it seemed repetitive.
Let me know if this help?
———
SyntaxError: expected expression, got ‘<‘ admin-ajax.php:1:0
Use of captureEvents() is deprecated. To upgrade your code, use the DOM 2 addEventListener() method. For more help http://developer.mozilla.org/en/docs/DOM:element.addEventListener admin.php:467:9
SyntaxError: expected expression, got ‘<‘
———–
<b>Warning</b>: ini_set() has been disabled for security reasons in <b>/home/dirtyworking/public_html/tempsite/wp-includes/load.php</b> on line <b>305</b>
update_status(‘Scanning …/tempsite’, 5, -1);
//flushed(46)
/*–>*/
document.getElementById(‘status_text’).innerHTML=’Checking /home/dirtyworking/public_html/tempsite/.htaccess (26224 bytes)’;
scanned++;
—————–
<b>Warning</b>: ini_set() has been disabled for security reasons in <b>/home/dirtyworking/public_html/tempsite/wp-includes/load.php</b> on line <b>305</b>
<b>Warning</b>: Cannot modify header information – headers already sent by (output started at /home/dirtyworking/public_html/tempsite/wp-includes/load.php:305) in <b>/home/dirtyworking/public_html/tempsite/wp-content/plugins/jetpack/modules/after-the-deadline.php</b> on line <b>175</b>
AtD.rpc = “http:\/\/dirtyworklandscape.com\/wp-admin\/admin-ajax.php?action=proxy_atd&_wpnonce=5b15818ee9&url=”;
AtD.api_key = “WPORG-b378e65d2911381e424d9ed87e40c9ac”;
AtD.setIgnoreStrings(“”);
AtD.showTypes(“”);
AtD.rpc_ignore = “http:\/\/dirtyworklandscape.com\/wp-admin\/admin-ajax.php?action=atd_ignore&_wpnonce=95858cdabe&phrase=”;
Plugin Author
Eli
(@scheeeli)
Yes, That does provide some answers for us:
First, it looks like your server has disabled the ini_set() function, see if you can re-enable that function to fix this issue.
Also, you may have enabled WP_DEBUG, check your wp-config.php and if you find a line that says define(‘WP_DEBUG’, true); then change it to say define(‘WP_DEBUG’, false);
You might also want to check the log_level setting in your php.ini file on the server. If it is set to warning, notice, or debug, then you might want to change it to error. You may want to turn display_errors off too.
Let me know if you need any more help with any of these or if you still have this issue after you make these changes.
Aloha, Eli
1. ini.set() if this was disabled, all site within server wouldn’t be able to do full scan, no? Because some sites works and some don’t.
2. doubt this becaue they are all live sites. If it’s on debug, I’d noticed because it’ll have message on each page
Either way, I’ll check all of them and get back with you,.
Plugin Author
Eli
(@scheeeli)
Actually, it is only the combination of these settings that would lead to warnings being output and only when circumstances create a situation where a warning is triggered. It is very likely that changing just one of these settings would solve you problem.
As you can see by the output you posted here, this is not a problem with my plugin but rather a configuration on your site/server that creates HTML output inside my dynamic javascript thus breaking my code and sending these errors to your browser console.
There are likely to be other situation that generate warnings which could cause other issues that you have not noticed yet. That is why I recommended turning off error reporting for warnings at all levels.
Feel free to let me know if you try my suggestions and it does not work, though I would be surprised at that 😉
Eli, I know you’re right because my other sites on the server is working.
Debug is off for sure & confirmed.
I’m not sure if server itself has ini_set issues but I did find this line within wp-includes/load.php
if ( defined( ‘XMLRPC_REQUEST’ ) || defined( ‘REST_REQUEST’ ) || ( defined( ‘DOING_AJAX’ ) && DOING_AJAX ) ) {
ini_set( ‘display_errors’, 0 );
}
would doing inidividual change on this file result anything different? Would any changes here effect anything else in terms of security?
Nvm… I found out that ini_set() was disabled within WHM.
I just never thought that would be it since some sites were working… weird…… Thanks for working with me, it’s all working now!!!
Fixed by WHM-> PHP configuration editor -> advanced -> disable_functions
