95
Validation results

Page Builder Framework

Free WordPress 4.9.8 theme

Page Builder Framework

Free WordPress 4.9.8 theme
95
    Error 8 : Undefined index: slug
    In /home/www/themecheck/themecheck/controllers/controller_results.php line 772
  • THEME TYPEWordPress theme 4.9.8
  • FILE NAMEpage-builder-framework.1.7.1.zip
  • FILE SIZE1705992 bytes
  • MD5175453ff7f777425c2edb350d808f27b
  • SHA1990f7fcfadcba55598b7d3175220aa3e13b916ad
  • LICENSEGNU GPL 3
  • FILES INCLUDEDCSS, PHP, Bitmap images
  • THEME URIhttps://wp-pagebuilderframework.com
  • VERSION1.7.1
  • AUTHOR URI
  • TAGSone-column, two-columns, left-sidebar, right-sidebar, custom-colors, custom-menu, featured-images, full-width-template, custom-logo, custom-background, threaded-comments, blog, e-commerce
  • CREATION DATE2018-03-27
  • LAST FILE UPDATE2018-03-27
  • LAST VALIDATION2018-03-27 20:40
  • OTHER VERSIONS

    1.8 : 96%

    1.7.5 : 95%

    1.7.4.1 : 95%

    1.7 : 95%

    1.6.10 : 96%

Error 8 : Undefined variable: cms
In /home/www/themecheck/themecheck/controllers/controller_results.php line 818
Warning
  1. theme tags : Presence of bad theme tagsFound wrong tag custom-logo in style.css header.
  2. Text domain : Incorrect use of translation functions.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 page-builder-framework, kirki.
  3. 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.
  4. Custom elements : Presence of custom headerNo reference to custom header was found in the theme.
  5. 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.
Tip-off
  1. Static links : Presence of hard-coded linksPossible hard-coded links were found in the file footer.php.
    Line 27: $footer_column_two = $footer_column_two == false ? 'Powered by <a href='https://wp-pagebuilderframework.com/'>Page Builder Framework</a>' : $footer
  2. Optional files : Presence of rtl stylesheet rtl.cssThis theme does not contain optional file rtl.php.
  3. Optional files : Presence of front page template file front-page.phpThis theme does not contain optional file front-page.php.
  4. Optional files : Presence of home template file home.phpThis theme does not contain optional file home.php.
  5. Optional files : Presence of tag template file tag.phpThis theme does not contain optional file tag.php.
  6. Optional files : Presence of term template file taxonomy.phpThis theme does not contain optional file taxonomy.php.
  7. Optional files : Presence of author template file author.phpThis theme does not contain optional file author.php.
  8. Optional files : Presence of date/time template file date.phpThis theme does not contain optional file date.php.
  9. Optional files : Presence of attachment template file attachment.phpThis theme does not contain optional file attachment.php.
  10. Optional files : Presence of image template file image.phpThis theme does not contain optional file image.php.
  11. Use of includes : Use of include or requireThe theme appears to use include or require : customizer-functions.php
    Line 18: include_once( get_template_directory() . '/inc/customizer/styles.css.php' )
    Line 49: <?php require( get_template_directory() . '/inc/customizer/styles.css.php' ); ?>
    Line 70: require( get_template_directory() . '/inc/customizer/custom-controls.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 : wpbf-kirki.php
    Line 15: include_once( ABSPATH . 'wp-admin/includes/plugin.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 : init.php
    Line 14: require_once( WPBF_THEME_DIR . '/inc/options.php' );
    Line 17: require_once( WPBF_THEME_DIR . '/assets/kirki/kirki.php' );
    Line 20: require_once( WPBF_THEME_DIR . '/inc/customizer/wpbf-kirki.php' );
    Line 23: require_once( WPBF_THEME_DIR . '/inc/body-classes.php' );
    Line 26: require_once( WPBF_THEME_DIR . '/inc/helpers.php' );
    Line 29: require_once( WPBF_THEME_DIR . '/inc/comments.php' );
    Line 32: require_once( WPBF_THEME_DIR . '/inc/misc.php' );
    Line 35: require_once( WPBF_THEME_DIR . '/inc/customizer/customizer-functions.php' )
    Line 38: require_once( WPBF_THEME_DIR . '/inc/template-parts/header.php' );
    Line 41: require_once( WPBF_THEME_DIR . '/inc/template-parts/footer.php' );
    Line 44: require_once( WPBF_THEME_DIR . '/inc/theme-mods.php' );
    Line 48: require_once( WPBF_THEME_DIR . '/inc/woocommerce.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.
Other checked themes