Theme Check Information

Last Update: February 13, 2023

Theme Check is a plugin that tests your theme with the latest theme review standards using automated testing tools. However, the results should be taken with care. Many items it will return may seem to be errors, but are not. Please see below for a description of things you will see in the results. Errors you may see in the test results do not mean that the theme is broken or will not work. Themecheck is a general guideline, and is not anywhere close to being fool proof.

These Results From Theme Check Can Be Fully Ignored

text domain warnings
base_64_encode
file operations like fread, fwrite, fsockopen, fopen, fclose
file_get_contents

Explanations For Why They Can Be Ignored

1) text domain warnings: Theme Check plugin is listing these as false positives. The listed items are correct.

2) base64_encode: that is a normal php function. WordPress theme repo prohibits it for no reason in our opinion. You can do harmful things with any php code. It is officially allowed by ThemeForest!

3) file operations like fread, fwrite, fsockopen, fopen, fclose: all used only for importer. WordPress prefers using the WP_filesystem, but there is no problem with using the php functions.

4) file_get_contents: the main problem is that wp_filesystem offers very limited functions. So for example for revslider imports we use php ZipArchive class right now which allows you to read a file inside a zip without extracting the zip. The wp_filesystem function get_contents doesn’t allow to do this. So we would need to extract all the zips to the upload directory, then get the contents and then delete them again when finished. that causes a lot of overhead and is completely unnecessary.

Copy to Clipboard

WARNING: Found base64_encode in the file tweets-widget.php. base64_encode() is not allowed.
Line 52: $toSend = base64_encode($credentials);
 
WARNING: Found base64_encode in the file recaptchalib.php. base64_encode() is not allowed.
Line 226: return strtr(base64_encode ($x), '+/', '-_');
 
WARNING: Found base64_encode in the file class.options_machine.php. base64_encode() is not allowed.
Line 582: $output .= '<textarea id='export_data' rows='8'>'.base64_encode(serialize($smof_data)) /* 100% safe - ignore theme check nag 
 
WARNING: Found base64_decode in the file importer.php. base64_decode() is not allowed.
Line 103: $smof_data = unserialize( base64_decode( $theme_options_txt['body'])  );
 
WARNING: Found base64_decode in the file functions.interface.php. base64_decode() is not allowed.
Line 247: $smof_data = unserialize(base64_decode($imported_data)); //100% safe - ignore theme check nag
 
WARNING: fwrite was found in the file recaptchalib.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 84: fwrite($fs, $http_request);
 
WARNING: fsockopen was found in the file recaptchalib.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 80: if( false == ( $fs = @fsockopen($host, $port, $errno, $errstr, 10) ) ) {
 
WARNING: fread was found in the file importer.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 264: while (!feof($slider_export)) $content .= fread($slider_export, 1024);
Line 265: if($custom_animations){ while (!feof($custom_animations)) $animations .= fread($custom_animations, 1024); }
Line 266: if($dynamic_captions){ while (!feof($dynamic_captions)) $dynamic .= fread($dynamic_captions, 1024); }
Line 267: if($static_captions){ while (!feof($static_captions)) $static .= fread($static_captions, 1024); }
 
WARNING: fopen was found in the file parsers.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 415: $fp = $this->fopen( $file, 'r' );
Line 641: function fopen( $filename, $mode = 'r' ) {
Line 644: return fopen( $filename, $mode );
 
WARNING: file_get_contents was found in the file parsers.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 66: $success = $dom->loadXML( file_get_contents( $file ) );
Line 269: if ( ! xml_parse( $xml, file_get_contents( $file ), true ) ) {
 
WARNING: file_get_contents was found in the file importer.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 278: $content = @file_get_contents($filepath);
 
WARNING: fclose was found in the file recaptchalib.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 88: fclose($fs);
 
WARNING: fclose was found in the file parsers.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 464: $this->fclose($fp);
Line 659: function fclose( $fp ) {
Line 662: return fclose( $fp );
 
WARNING: fclose was found in the file importer.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 269: fclose($slider_export);
Line 270: if($custom_animations){ fclose($custom_animations); }
Line 271: if($dynamic_captions){ fclose($dynamic_captions); }
Line 272: if($static_captions){ fclose($static_captions); }

These Results From Theme Check Can Be Fully Ignored
Explanations For Why They Can Be Ignored

Theme Check Information

These Results From Theme Check Can Be Fully Ignored

Explanations For Why They Can Be Ignored

In this article