videopro
WordPress 6.7 theme
- THEME TYPEWordPress theme 6.7
- FILE NAMEvideopro 2.zip
- FILE SIZE29772819 bytes
- MD56ee4f72d8d5ed6ce1c427cbbb85eae99
- SHA13859ef89526e6249dcdc73692291945192f52423
- LICENSECustom
- FILES INCLUDEDCSS, PHP, HTML, Bitmap images
- THEME URIhttp://videopro.cactusthemes.com
- VERSION2.3.7.9
- AUTHOR URIhttps://www.cactusthemes.com
- 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 DATE2022-12-03
- LAST FILE UPDATE2022-12-03
- LAST VALIDATION2022-12-03 19:49
- OTHER VERSIONS
This theme seems to be proprietary. Themecheck doesn't distribute commercial themes.
Critical alerts
- File class-tgm-plugin-activation.php : 741: $this->page_hook = call_user_func( 'add_submenu_page', $args['parent_slug'], $args['page_title'], $args['menu_t
-
Plugins are not allowed in themes. The zip file found was
videopro-shortcodes.zip cactus-video.zip js_composer.zip video-thumbnails-2.12.5.zip cactus-rating.zip easy-tab.zip cactus-actor.zip cactus-ads.zip advance-search-form.zip option-tree-2.7.3.2.zip videopro-unyson-backup-restore.zip cactus-badges.zip videopro-sampledata.zip.
Warning
- 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 videopro, tgmpa, membership2, colossal.
- .ds_store was found.
- Bad screenshot file extension ! File screenshot.png is not an actual JPG file. Detected type was : "image/png".
Tip-off
- Possible hard-coded links were found in the file welcome.php.200: <li><span class='new'>#Add:</span> support Google AMP for Single Post. Check <a href='http://videopro.cactusthemes.com/doc/docs/videopro-google-amp-compatibility201: <li><span class='new'>#Add:</span> support Facebook Instant Articles for Single Post. Check <a href='http://videopro.cactusthemes.com/doc/docs/videopro-2-0-features/facebook-in456: <li>Full release logs: <a href='http://videopro.cactusthemes.com/release_log.html' target='_blank'>Release Possible hard-coded links were found in the file theme-options.php.257: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,282: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,312: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,342: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,257: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,282: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,312: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,342: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,257: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,282: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,312: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,342: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,257: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,282: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,312: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,342: 'desc' => wp_kses( __( 'Enter font-family name here. Google Fonts are supported. For example, if you choose 'Source Code Pro' <a href='http://www.google.com/fonts/'>Google Font</a> with font-weight 400,500,600,
- This theme does not contain optional file rtl.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 taxonomy.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 attachment.php.
- The theme appears to use include or require : page.php 13: require 'bp_user.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.
