Great stuff as always Sam, also, nice one Iman
If you can’t built a WordPress theme from scratch, you shouldn’t be selling WordPress themes, seriously, what happens when you need to debug it?
Spend some time learning to develop WordPress themes properly, carefully choose your frameworks, and develop a product that is your own.
Grabbing a starter theme, slapping a page builder in and updating the CSS would work for a site you’re making just for yourself, but it’s likely to be very problematic if you start selling it.
@natman, could you please remove all of my themes from the affected list, any that were potentially affected have been updated, and you’ve listed plenty of my themes that were released well past the 4.2 security update that fixed this flaw.
I know you’ve scraped that theme list for speed, but I can count at least 5 of my themes in that list that should be nowhere near it.
EDIT: Sorry, that list is useless I’ll admit one of my themes was affected by this, and it’s not even in that list, then you’ve added multiple of my themes that are not affected, and they are in this list?! Can’t wait for all the support tickets from my confused buyers…
Fact of the matter is that the theme met the marketplace standards, and yet was rejected three times by a reviewer who clearly was not capable of making the right call…
100% wrong, as the interview stated it took the review team manager to look at the theme and “see it’s potential” before it was accepted.
As has been shown 1000’s of times before, the first thing viewed when reviewing a theme is the design quality, if this doesn’t meet standards then the theme is rejected.
BTW, the reviewers do a great job, it would be a good idea to be a little more respectful to people who are seemingly massively overworked and doing the best job humanly possible.
I don’t agree that this story proves a problem in our review system but it surely proves that super heavy marketing works!Cheers,
Agreed, it seems buyers are happy with X, but the design quality is pretty weak IMO, seeing that the first thing that is reviewed by the TF team is design quality, I’m not surprised it was rejected, if you consider this is the third iteration of X, I imagine the original design was of even lower quality.
@themeCo – no disrespect, you clearly have a great selling product, I’m just saying there’s many stronger designs on here.
well i guess as long as the spinner loads before the content does, then i guess its ok,
Yeah, it’s super basic I know, but does the trick, it’s the first bit of HTML after the body tag so it’s pretty seamless, mainly there just to stop content flashing around as it loads
Be as nosey as you want
In what way would it be AJAX though? It’s just a little HTML that’s used to cover any ugliness as the side loads, and then when window.load() fires it’s simply removed.
if so, can you document the code, so others besides me can learn from, i ask you because your ballin on sales, lol.
Turned this into a blog post for you:http://www.madeinebor.com/premium-theme-development-using-get_template_part-switching-blog-layouts/
Sorry, I’m not the best writer in the world, but hopefully that will help
EDIT: Dat URL
Masonry blog vs blog with sidebar etc probably has quite big markup changes, in which case it’s best to use 2 separate loop files and then use this in your page:
get_template_part( 'loop', get_option('blog_layout', 'masonry') );