Tomato
WordPress 6.7 theme
- THEME TYPEWordPress theme 6.7
- FILE NAMEtomato.zip
- FILE SIZE3138677 bytes
- MD52d6396a5c0d4e32aa93d8ac9d80d51da
- SHA13ab03fffd1046d1a4916da18ed9290bb89cec36b
- LICENSEGNU GPL 2
- FILES INCLUDEDCSS, PHP, XML, Bitmap images, Adobe Illustrator
- THEME URIhttp://themesquared.com/tomato
- VERSION1.4
- TAGSone-column, two-columns, right-sidebar, custom-header, custom-menu, editor-style, featured-images, microformats, post-formats, rtl-language-support, sticky-post, translation-ready
- CREATION DATE2020-01-16
- LAST FILE UPDATE2020-01-16
- LAST VALIDATION2020-01-16 17:30
This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
-
Plugins are not allowed in themes. The zip file found was
cpt.zip wp-post-formats-develop.zip.
Warning
- Possible variable $str found in translation function in class-lessc.php. Translation function calls should not contain PHP variables. Possible variable $arg found in translation function in class-lessc.php. Translation function calls should not contain PHP variables. Possible variable $items found in translation function in class-lessc.php. Translation function calls should not contain PHP variables. Possible variable $string found in translation function in class-lessc.php. Translation function calls should not contain PHP variables. Possible variable $val found in translation function in class-lessc.php. Translation function calls should not contain PHP variables. Possible variable $newUnit found in translation function in class-lessc.php. Translation function calls should not contain PHP variables. Possible variable $res found in translation function in class-lessc.php. Translation function calls should not contain PHP variables. Possible variable $key found in translation function in class-lessc.php. Translation function calls should not contain PHP variables. Possible variable $part found in translation function in class-lessc.php. Translation function calls should not contain PHP variables. Possible variable $this found in translation function in class-lessc.php. Translation function calls should not contain PHP variables.
- Screenshot dimensions are wrong! Detected: 697x523px (697:523). Ratio of width to height should be 4:3.Screenshot size is 697x523px. Screenshot size should be 1200x900, to account for HiDPI displays. Any 4:3 image size is acceptable, but 1200x900 is preferred.Bad screenshot file extension ! File screenshot.png is not an actual JPG file. Detected type was : "image/png".
Tip-off
- This theme does not contain optional file rtl.php.
- This theme does not contain optional file front-page.php.
- This theme does not contain optional file home.php.
- This theme does not contain optional file category.php.
- This theme does not contain optional file tag.php.
- This theme does not contain optional file author.php.
- This theme does not contain optional file date.php.
- This theme does not contain optional file attachment.php.
- This theme does not contain optional file image.php.
- The theme appears to use include or require : default-woocommerce-widgets.php 932: require( WC()->plugin_path() . '/includes/walkers/class-product-cat-list-wa If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : class-meta-box-ui.php 17: require( admin_path() . 'metabox/box_body.php' ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : class-options-ui.php 34: require( admin_path() . 'panel/' . $file . '.php' ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : tabs.php 62: require( $this->get_view() ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : heading.php 87: require( $this->get_view() ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : call-action.php 52: require( $this->get_view() ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : reservation.php 122: require( $this->get_view( $spyropress_template ) ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : accordion.php 64: require( $this->get_view() ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : instagram.php 57: require( $this->get_view() ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : about-us.php 145: require( $this->get_view( $spyropress_template ) ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : icon-teaser.php 122: require( $this->get_view( $spyropress_template ) ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : rich-text.php 40: require( $this->get_view( ) ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : home-section.php 146: require( $this->get_view( $spyropress_template ) ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : contact.php 147: require( $this->get_view() ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : clients.php 88: require( $this->get_view() ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : list-items.php 66: require( $this->get_view() ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : spyropress-builder-init.php 109: include_once( $spyropress_include ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : spyropress-builder-template-loader.php 32: require( $template ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : spyropress-widget-init.php 42: include_once( $widget ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : spyropress-admin-init.php 88: require( $i ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : demo-data.php 34: include_once( $option_file ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : bootstrap-nav.php 27: require_once( locate_template( $templates, false ) ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : recent-posts.php 74: require( $this->get_view( $spyropress_template ) ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.The theme appears to use include or require : contact.php 91: require( $this->get_view() ); If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead. Otherwise, use include_once or require_once instead.
