31
Validation results

Enigma-Pro

Enigma-Pro

WordPress 4.6+ theme
31
  • THEME TYPEWordPress theme 4.6+
  • FILE NAMEenigma.zip
  • FILE SIZE6817273 bytes
  • MD519f6028639875bdf49b1c7c048ebd269
  • SHA1fec417861a17f91a210be0518cd3c623a2603d31
  • LICENSEGNU GPL 3
  • FILES INCLUDEDCSS, PHP, Bitmap images
  • VERSION1.2
  • TAGSblack, green, gray, red, dark, light, silver, white, two-columns, custom-menu, right-sidebar, fixed-layout, fluid-layout, custom-background, featured-image-header, sticky-post, theme-options, threaded-comments, featured-images, flexible-header, responsive-
  • CREATION DATE2020-07-31
  • LAST FILE UPDATE2020-07-31
  • LAST VALIDATION2020-07-31 19:07
This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
  1. Title : Title No reference to add_theme_support( "title-tag" ) was found in the theme.The theme needs to have <title> tags, ideally in the header.php file.The theme needs to have a call to wp_title(), ideally in the header.php file.The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output.
  2. Presence of iframes : iframes are sometimes used to load unwanted adverts and malicious code on another site Found <iframe width="100%" scrolling="no" height="500" frameborder="0" src="<?php echo $google_maps; ?> in file contact-us.php. 117: <iframe width='100%' scrolling='no' height='500' frameborder='0' src='<?php
  3. Deprecated functions : get_currentuserinfo get_currentuserinfo found in file option-panel.php. Deprecated since version 4.5. Use wp_get_current_user instead.108: get_currentuserinfo();
Warning
  1. theme tags : Presence of bad theme tagsThe tag black has been deprecated, it must be removed from style.css header.The tag green has been deprecated, it must be removed from style.css header.The tag gray has been deprecated, it must be removed from style.css header.The tag red has been deprecated, it must be removed from style.css header.The tag dark has been deprecated, it must be removed from style.css header.The tag light has been deprecated, it must be removed from style.css header.The tag silver has been deprecated, it must be removed from style.css header.The tag white has been deprecated, it must be removed from style.css header.The tag fixed-layout has been deprecated, it must be removed from style.css header.The tag fluid-layout has been deprecated, it must be removed from style.css header.The tag responsive-layout has been deprecated, it must be removed from style.css header.
  2. Text domain : Incorrect use of translation functions.Wrong installation directory for the theme name. The directory name must match the slug of the theme. This theme's correct slug and text-domain is enigma-pro.
  3. Text domain : Incorrect use of translation functions.Found a translation function that is missing a text-domain. Function _e, with the arguments 'Home Layout Manager' in file option-settings.php.More than one text-domain is being used in this theme. This means the theme will not be compatible with WordPress.org language packs. The domains found are weblizar, .
  4. Cdn : Use of CDNFound the URL of a CDN in the code: maxcdn.bootstrapcdn.com/font-awesome. CSS or Javascript resources should not be loaded from a CDN. These resources should be bundled with the theme.
  5. Plugin territory : Plugin territory functionalitiesThe theme uses the register_post_type() function, which is plugin-territory functionality.The theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
  6. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  7. Editor style : Presence of editor styleNo reference to add_editor_style() was found in the theme. It is recommended that the theme implements editor styling, so as to make the editor content match the resulting post output in the theme, for a better user experience.
  8. CSS files : Presence of .screen-reader-text class.screen-reader-text css class is needed in your theme css. See : the Codex for an example implementation.
  9. Screenshot : Screenshot fileScreenshot is wrong size! Detected: 1903x5022px. Maximum allowed size is 1200x900px.Screenshot dimensions are wrong! Detected: 1903x5022px (1903:5022). Ratio of width to height should be 4:3.Bad screenshot file extension ! File screenshot.png is not an actual JPG file. Detected type was : "image/png".
Tip-off
  1. Optional files : Presence of rtl stylesheet rtl.cssThis theme does not contain optional file rtl.php.
  2. Optional files : Presence of home template file home.phpThis theme does not contain optional file home.php.
  3. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  4. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  5. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  6. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  7. Use of includes : Use of include or requireThe theme appears to use include or require : shortcodes.php 3: if(defined('WP_ADMIN') && WP_ADMIN ) { require_once('shortcode_popup.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 : home-portfolio.php 4: //require_once('js/slidecustomjs.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 : option-panel.php 62: <?php require_once('option-data.php'); ?> 64: <?php require_once('option-settings.php'); ?> 99: include($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.
Other checked themes