mateusneves
Member
Posted 1 year ago #
My theme is now licensed under GPL
For download access: MN Chameleon Theme
* Licensed under GPL
* Clean and full customizable design
* Localization ready ( English and Portuguese included )
* Menu manager ready
* Dropdown menu ready
* Widget ready ( Sidebar and Footer )
* Theme options ( Total customization )
o Magazine mode and Blog mode
o Theme color ( color picker )
o Custom logo
o Optionals logos
o Three font type options
o Posts slider effect
o Featured post
o Social Network options
o And more…
* Custom header if you want
* Post thumbnails for magazine mode, slider and featured post
* Option model page without sidebar
* It’s totality free!
looks like it could be a nice theme, but I had to rename the folder for wordpress to even find it, and even then it doesnt seem to load the css correctly.
It also causes a few errors when checked with the Theme Check plugin.
mateusneves
Member
Posted 1 year ago #
Tanks, i will check it, but i instaling this theme in my server and its works fine.
A few notes:
1) You should remove the __MACOSX hidden files.
2) You should add your Theme options to the database as a single DB entry, in the form of an options array
3) All Theme options need to be validated on input, and properly escaped on output, both on front-end output, and on output in the Theme Settings form (e.g. esc_attr() for text inputs and esc_html() (or esc_textarea() in WP 3.1) for textareas).
4) In the Theme Settings form, use the WordPress checked() and selected() functions for outputting "checked=checked" and "selected=selected".
5) Your call to add_theme_page() should use the "edit_theme_options" capability, rather than the "administrator" role.
6) Theme should explicitly provide Settings-page nonce checking, if not using the Settings API
7) Your backwards-compatibility is inconsistent. In some places, you wrap function_exists() conditionals around add_theme_support(), which was added in WP 2.9, but not around set_post_thumbnail_size(), which was also added in WP 2.9. I would recommend not worrying about backward compatibility for anything before one version prior to the current major release. In other words: now that WP 3.1 is released, I would limit backwards-compatibility to WP 3.1 or WP 3.0 functions.
mateusneves
Member
Posted 1 year ago #
mateusneves
Member
Posted 1 year ago #
Chipe Bennet, you have a example of the item 2 in you few notes list?
mateusneves
Member
Posted 1 year ago #
@mateusneves, the SpeckyGeek tutorial looks sound (although it might be a bit overkill unless you are implementing several dozen Theme options).
Here's my tutorial on the same topic:
http://www.chipbennett.net/2011/02/17/incorporating-the-settings-api-in-wordpress-themes/
(I'm going to write a simplified version, also.)
poena
