@Rahul Tilloo Well other well-known ones do that too... the point in this article that we are making is that it still causes inconvenience to users if they want to switch away from Headway or Genesis ... and they used the Headway SEO options... because now they have to use the SEO Data Transporter to transfer the data to a plugin or a new theme....
@newwpthemesnet Yes, I think the themes should have the proper semantics (which include H1, H2 etc. Breadcrumbs can be provided by a theme if needed. But the theme should account for popular plugins such as BreadCrumb NavXT or Yoast... both are fairly powerful and bring a lot to the table.
@hollywood_cat No particular form attracts SPAM. It is your site that does. If you put proper SPAM protection (such as captcha, or honeypot) then it will be fine. Gravity Forms have both options.
@WPFortress Just to be clear, I'm not pointing fingers at you. Everyone is entitled to an opinion, and I respect the choices that you guys have made.I understand that a lot of companies have "Import Content" feature for their themes along with documentation and FAQs. My point is that people should NOT have to read a 90+ page web & PDF documentation to USE a THEME. I haven't seen the codes for your theme nor have used any of your themes. So I don't know how they are working. All I'm saying is if you are copying hard codes of plugins in your themes and giving them credit, then that is not the way to do it (specially not for big features). It is much better to use theme/plugin dependency so the user have the ability to upgrade that plugin when the plugin author updates.
Totally agreed with you. Plugin and Themes are separate. It is definitely a "marketing gimmick". How do you stand out? By bloating it with more features when you shouldn't. I think that theme authors are doing it to keep up with competition. If they seriously think from a "user stand point", then they would realize the inconvenience. As for the theme/plugin dependencies @otto42 has written a very cool article about it. http://wpbeg.in/JtxqCh
@WPFortress You can't possibly put everything into a theme. There is a reason why plugins are available. It is this vary mindset that is causing this huge issue. Everyone wants to bloat the theme with tons of widgets, hundreds of options... It makes it that much harder for a new user to understand WordPress. They like the theme how it looks (it should be simple install and activate) to make the theme look like the demo. Except it doesn't. They have to go through a bunch of settings to just get close to what the demo of the theme look like. Options are a great thing to have, but within reasons. Changing themes should not be as big of a hassle that it is now becoming (with all these options). If you think there is an important feature that you want to provide (i.e tabbers, slideshow, etc), perhaps going on a similar route as WooDojo makes more sense. Where you create a mega plugin with widgets that the user can activate. So it can actually work with other themes should the user decide to switch. The whole point is to "keep the very important features" such as SEO data be the same through out theme changes. I think this comes down to the fact that companies do not want to promote other companies or other developers. But we should. Specialize in what you do best (and be damn sure that you are the best in that). Collaborate with complimentary products, and see how you two can partner up. This will save you a lot of time which you can use to do what you do best "produce more great looking, well-coded themes".
@mrwindowsx Oh didn't know that. Thanks for pointing it out.
@yoast @jonbish Yes we understand that this is probably a compatibility issue. Yoast sitemaps work fine on our sites. We had to do this on a client's site.
@Daniele Zamboni These are CSS classes that you can add for styling purposes.
@makkuus @wpbeginner None that we are aware of.
@mrahmadawais Because we keep the most updated version running.
@shumail @thewebmasterblogs It won't work with Gravity Forms because they do not have that add-on.
In the usage section, replace "wpbeginner" with your twitter name.
Agreed. Just updated the code.
It still works :)
@MarkStanwyck Its a security update, so not major but recommended for everyone.
@MarkStanwyck The newest version of HTTPs is extremely unstable. We recommend using 2.0.4 << that is the last stable version that we found is working. As you can notice, that the current version is being reported by so many.