Correct me if I am wrong (didn’t read the whole thread) but I think the point of using “shortcode plugins” is to prevent the “lock in” effect you get if you use a theme and then want to switch and none of your shortcodes work any longer. Therefore it should be sufficient to provide a small self written plugin for your customers so they can switch theme whenever they want and keep their shortcodes working. Thats what I plan to do.
I’m still confused… It’s about working shortcodes when the user change the theme with another theme of the same authors?... or different authors, different framework etc?...
So, let’s see, if we have some theme-specific features like cool services section or filterable portfolio, how are we supposed to integrate it? Through shortcodes, obviously, but creating plugins for each theme individually is just stupid. Now we don’t have to maintenance 10 themes, but 10 themes + 30 plugins maybe? Really? And how about the grid? Why aren’t we allowed to create column shortcodes? One may use skelton, one bootstrap, one their own grid, how do we integrate it within the theme without shortcodes?
+1… All the pages from my templates are using column shortcodes.
Also in 2 weeks I’ll finish a new template. Could be accepted if it doesn’t meet the new standards?
I hope they will change their minds and will let us to include shortcodes as columns, maps, tabs etc as we used to do till now. What is so wrong with this?... At least columns…
I’ve worked a lot to build a framework with a lot of features of this kind and now suddenly these aren’t accepted any more?... How come that?... And now I should loose a lot of time also to find a alternative way… Guys, who are those “experienced authors” who agreed with this?... I bet that there is not even one from the top authors.
Actually it’s not, you can. It has been clarified a few months ago:
Thanks… I didn’t know about that.
What about having a button (On/Off) Timthumb (with the default value on Off), and if Off, to use another script as aqua resizer, filosofo… This is a rejecting reason any more? I would like to know because currently I’m working to a new theme and I don’t want to loose time and finally the item will be rejected.
I hope it’s a start some real theme authors develop their own stuff
Funny because in your latest theme you are using prettyphoto, flexslider, vegas, why didn’t you code these yourself? Are you not a real author?It’s the same for everyone, we buy/use ready code because it’s convenient, saves time, and there is no point reinventing the wheel
+1 … The main difference between what he uses (prettyphoto, flexslider etc) and CC plugins, is that they are for free (unless you “buy their authors a beer”) and the CC plugins are not.
OK so we’re also confused: We – as an author – CANNOT give permission to our customers about including our products in their themes (if they purchased an extended license of course)?
Probably if you give us your permission. I was about to buy an extended licence of your Layer Slider but I’m waiting for something clear. Otherwise I think we, as TF authors won’t buy extended licences but regular licences just for presentation…
Again, I’m agree to pay the regular licence every time I use a plugin in my themes just for presentation. If any one of the buyers likes the plugin, they should buy the licence for that plugin. It’s fair…
But these new licences should be respected by all authors and all items, not just the new items. So the old items with integrated plugins should not offer them anymore even they paid for extended licences.
We already understood that. But how remains with this difference between the old and new items which have the plugins integrated. The old ones will have more more sales and the new ones don’t. This is my point of view… There should be no difference between the old and new items. The buyers of these kind of items should buy themselves the licence. Not only the buyers of the new items. That’s not fair… Thanks