I am seeking some serious replies..
I am serious. If you’re adding shortcodes for use in the post content within your theme, you’re
If you need some help writing a plugin to handle these shortcodes, I’m more than willing to offer my feedback and help on that.
Here’s a thought: Don’t add shortcodes to your theme and you won’t have to worry about counting them.
Sorry, I missed your last reply until now. If you’re going to be building themes, you should really be diving into code anyway, so that’s not an issue.
Responsive Web sites
Irrelevant in terms of theme frameworks. Responsive design is something you’re going to have to do on your own anyway.
Irrelevant in terms of theme frameworks. Use it. Don’t use it. It’s up to you.
Any theme or framework should support multisite out of the box. There’s generally nothing special that needs to be done.
I’m sure all of the mentioned frameworks are internationalized. I can’t say for certain, but that should be pretty standard.
That’s all about your HTML. If you’re building a child theme based off one of the parent themes you mentioned, that should be taken care of. If you’re building a [parent] theme off of a theme framework (Hybrid, Carrington, WP Framework, etc.), this is simple to do.
As far as meta, titles, and things of that nature, plugin territory.
Again, this is really up to you as the theme developer. There might be some framework features that need additional support for those things, but it’s generally not much. I know I have a few bbPress-specific bits of code in Hybrid Core.
Framework and theme comparisons
Really, you’re trying to compare apples and oranges. To break down a few of your options:
- Hybrid Core: Essentially, this is a library of scripts meant to aid in theme development. You pick and choose the scripts that you want to “deploy” in your theme.
- Genesis: This is basically a parent theme that allows you to create child themes. The HTML and everything is done for you. You can basically just come in and write CSS (for the most part). This is probably comparable to several of the other “frameworks” (i.e., advanced parent themes) you mentioned.
- Options Tree: This is a script that makes it easy to roll out theme options (not that it’s really hard with the Settings API anyway).
I’m not really sure about the other things. I hope I didn’t misrepresent Genesis or Options Tree either.
I’m assuming you’re correctly hooking your stylesheet into
wp_enqueue_scripts. If so, you just need to set the priority higher.
I’m the creator of Hybrid Core (the framework from Theme Hybrid) and will be more than happy to answer any questions you have about what it does. Hybrid Core has been in constant development since 2008, so it’s had time to grow and mature. Several ThemeForest authors, many theme companies, and a lot of WordPress.org theme authors use it to build themes.
Other than my own themes, here’s a couple of theme companies that use it, so you can see that it doesn’t limit you in any way:
Your list of potential “frameworks” is wildly varied, some of which I would not consider frameworks at all. I can only really speak for Hybrid Core, so feel free to ask me any questions.
home.php is for the posts page. It is not to be used for any other purpose than to show the latest blog posts.
To do what you want though, you must use front-page.php. It will always overwrite what’s shown on the front page of the site regardless of reading settings. If you take this route, the user only has to go to Settings > Reading to create a blog page (i.e., the posts page) if they choose to have one.
Of course, this is usually not a good idea for public themes (it’s good for client themes though). The theme shouldn’t dictate what’s shown on the front of the site, which is the purpose of front-page.php. I’d go with a custom page template instead to give users more flexibility. Yeah, it means more steps, but I’ve never had a user complain in the past 5 years of doing it this way.
There are studies that both talk about the healthy and unhealthy aspects of coffee. You’ll find plenty of info with a Google search. I consider anything that is addicting unhealthy though.
More than anything, it’s probably not the coffee that’s the really bad thing. It’s all the crap people add into their coffee that is.
My question: Assuming coffee is healthy, does it offer any additional benefits that you cannot get from a nutritionally-sound diet? That’s the way I look at it.
I love coffee, but I typically only drink it as a fun drink once in a while. I drink water 99% of the time though. I keep my energy levels high by eating a variety of plant foods, getting adequate rest, and keeping a regular exercise routine.
This is probably a bit more than what you wanted, but here’s a breakdown of all the things you need to fix other than what’s already been mentioned.
I’m assuming you’re properly adding the meta box via
add_meta_box(). Doing so will pass the
$post object directly to your function as the first parameter, so there’s no need for the
You should use the
wp_nonce_field() function to create your nonce input instead of hardcoding the HTML for it.
You need to escape the
$date variables before adding them as an attribute for your input boxes.
I’d also prefix your name attributes instead of using
_date in the inputs. Use a unique prefix like
wpt_. I’d make sure all things going to
$_POST are prefixed so there’s less risk of conflicts with anyone else’s code.
$post_id instead of
$post->ID. No biggie, but you already have the data there in variable form.
You should check the
delete_post_meta capabilities rather than the
edit_post capability. Plus, a hardcoded
edit_post is technically wrong; you’d need to use the post type object to check the actual capability, which might be different. But, you don’t need that cap. You need the post meta caps.
$_POST data should be sanitized/validated before sending it to the database. The month should be sanitized to make sure it’s a one-/two-number value. The date should go through the same process to make sure it’s both the type of data you want and in the correct format.
There’s no need for worrying if the data is an array because a user won’t be passing you an array through a text input box. Nevertheless, with proper validation/sanitization, you wouldn’t need to worry about that anyway.
If you’re going to check if the post type is a revision, it should be done before your foreach loop.
Your if/else and if checks in your foreach loop should be if/elseif/elseif instead.