Basel
WordPress 6.7 theme
- THEME TYPEWordPress theme 6.7
- FILE NAMEbasel.zip
- FILE SIZE4296819 bytes
- MD5045c4553c3cb18cdfa02cbf49270c6af
- SHA14d7539575776c0aeda9a50f1fb4229e2ec327203
- LICENSEGNU GPL 3
- FILES INCLUDEDCSS, PHP, HTML, XML, Bitmap images, Adobe Illustrator
- DEMO PAGEhttp://demo.xtemos.com/basel/
- VERSION4.7.0
- TAGSblack, white, light, one-column, two-columns, right-sidebar, responsive-layout, custom-header, custom-menu, editor-style, featured-images, microformats, post-formats, sticky-post, translation-ready
- CREATION DATE2021-01-21
- LAST FILE UPDATE2021-01-21
- LAST VALIDATION2021-01-21 12:07
- OTHER VERSIONS
This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
- File dashboard.php : 56: add_submenu_page(64: add_submenu_page(75: add_submenu_page(85: add_submenu_page(File dashboard.php : 56: add_submenu_page(64: add_submenu_page(75: add_submenu_page(85: add_submenu_page(File dashboard.php : 56: add_submenu_page(64: add_submenu_page(75: add_submenu_page(85: add_submenu_page(File dashboard.php : 56: add_submenu_page(64: add_submenu_page(75: add_submenu_page(85: add_submenu_page(
Warning
- The tag black 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 light 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.
- Found a translation function that is missing a text-domain. Function esc_html_e, with the arguments in file template-tags.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 basel, woocommerce, yith-woocommerce-wishlist, woodmart, tgmpa.
- Could not find the comment-reply script enqueued, however a reference to 'comment-reply' was found. Make sure that the comment-reply js script is being enqueued properly on singular pages.
- No reference to custom header was found in the theme.
- No reference to custom background was found in the theme.
- Possible variable $text found in translation function in template-tags.php. Translation function calls should not contain PHP variables.
- Possible variable $text found in translation function in template-tags.php. Translation function calls should not contain PHP variables.
- Screenshot size is 880x660px. 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
- Possible Favicon found in template-tags.php. Favicons are handled by the Site Icon setting in the customizer since version 4.3.
- 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 category.php.
- This theme does not contain optional file tag.php.
- This theme does not contain optional file taxonomy.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 archive.php.
- This theme does not contain optional file search.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 : variable.php 21: require_once('variable-swatches.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 : Importversion.php 465: require_once($class_wp_importer); 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 : dashboard.php 136: include_once 'views/' . $name . '.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 : woocommerce.php 1641: include_once( WC()->plugin_path() . '/includes/walkers/class-product-cat-li1712: //include_once( WC()->plugin_path() . '/includes/walkers/class-product-cat-li 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 : widgets.php 12: include_once( 'widgets/class-widget-price-filter.php');13: include_once( 'widgets/class-widget-layered-nav.php');15: include_once( 'widgets/class-wp-nav-menu-widget.php');16: include_once( 'widgets/class-widget-search.php');17: include_once( 'widgets/class-widget-sorting.php');18: include_once( 'widgets/class-user-panel-widget.php');19: include_once( 'widgets/class-author-area-widget.php');20: include_once( 'widgets/class-banner-widget.php');21: include_once( 'widgets/class-instagram-widget.php');22: include_once( 'widgets/class-static-block-widget.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.
