What do you mean by getting duplicates? The
_wp_page_template meta gives you the accurate file name that needs to be included. You can then do something like that:
$template = get_post_meta( $post->ID, '_wp_page_template', true ); get_template_part( $template );
EDIT: You would still probably need to do some more checks if, for example, a page doesn’t have any template assigned (the meta will return ‘default’).
Request received: [ThemeForest] Message sent via your marketplace profile from pogoking (ticket #1614)
Just sent you a message.
I don’t think there is one standard here. Everyone probably uses their own methods for creating one-page themes. How I would do it, keeping in mind that I like things simple, is I would create a bunch page templates, each corresponding to different section of the one-page (like gallery, portfolio, blog part, slider part etc.) and then just order them using the ‘Menu order’ in page attributes. Maybe even build some kind of drag-and-drop interface in theme options.
As I said, I like things simple. Other may have some more advanced systems with content composers and whatnot.
And why should people follow you on Twitter and Facebook? Shouldn’t the invite go to the person that has the best skills? It’s a shameless self-promotion.
Well well well… I know the first thing I’m buying with my Envato earnings haha
I suggest investing in a multicopter. You can attach a camera stabilisation system to it (a plane won’t handle this much of weight) and take some really great aerial videos. Or fly first person view. Or both.
I don’t really understand what you are complaining about. What’s wrong with header, footer and nav elements? Using these elements is IMO much better, cleaner, and semantically correct than slapping divs all around. And these tags are not about presentation, what I think you are implying. You can as well style the header to be at the bottom of the page.
The new HTML markup with new elements is much more readable. You open a HTML document and can tell right away which element does what. That’s not the case with old-style coding where all you see are generic divs all around. The navigation is not and should not be just another unordered list inside a generic div element. How is it different from another unordered list in another div that is actually a content of the article? Navigation is navigation, hence the nav element. I’m not sure if you know this, but you don’t have to put navigation li items inside another ul, you can just use nav as a wrapper for them. Page header is different from page content because it is repeated on every other page, the same goes for footer, that’s why they should be marked as such.
The second argument are search engines or screen readers. Or the ‘reader’ function in mobile Safari on iOS devices.
You can’t really compare the old HTML presentational attributes to HTML5 tags. You can style HTML5 tags whatever you want, but it all comes down to semantics. Aside element marks something that should be taken out of the flow of given article, but doesn’t force any styling. The article content should be perfectly understandable with the aside element taken out.
You could as well argue that ‘strong’ element is unnecessary and we should still be using ‘b’, or ‘i’ instead of ‘em’.
Shouldn’t the awards go to the best selling items that were accepted in 2012? Right now only Avada and Modernize are from 2012 (speaking about ThemeForest), the rest are from 2011 or 2010.
This just reflects the broken system of exposure on marketplaces.
Anyways, good luck to all the nominees!
So, what was wrong?
Btw, you do not want to flush rewrite rules on every page load. I suggest you remove that piece of code.