Cordillera
Free WordPress 6.7 theme
- THEME TYPEWordPress theme 6.7
- FILE NAMEcordillera.zip
- FILE SIZE2076850 bytes
- MD50e19d8686f02bc946d54a96158e367ea
- SHA14ea50624533e4891fd0b5176c4d59fd5b980f5b6
- LICENSEGNU GPL 2
- FILES INCLUDEDCSS, PHP, Bitmap images
- THEME URIhttp://www.mageewp.com/cordillera-theme.html
- VERSION1.0.7
- AUTHOR URIhttp://www.mageewp.com
- TAGSone-column, two-columns, three-columns, blue, green, responsive-layout, custom-background, custom-header, custom-menu, theme-options, right-sidebar, left-sidebar, translation-ready, editor-style, featured-images, full-width-template
- CREATION DATE2020-03-03
- LAST FILE UPDATE2020-03-03
- LAST VALIDATION2020-03-03 09:55
This theme is open source.
Warning
- The tag blue 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 responsive-layout has been deprecated, it must be removed from style.css header.
- 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 theme-functions.php. Favicons are handled by the Site Icon setting in the customizer since version 4.3.
- Possible hard-coded links were found in the file breadcrumb-trail.php.5: * Description: A smart breadcrumb menu plugin embedded with <a href='http://schema.org'>Schema.org</a> microdata that can handle variations in s
- This theme does not contain optional file rtl.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 attachment.php.
- This theme does not contain optional file image.php.
- The theme appears to use include or require : breadcrumb-trail.php 14: require_once( 'breadcrumbs.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.
