Does anybody knows if Visual Composer addons plugins should be integrated with TGMPA (as VC) or just like part of themes? Thanks
I have next custom theme widgets: Advertisment, Contact Form, Contact Information, Custom Links, Most Read Posts, Popular Portfolio Posts, Popular Posts, Recent Portfolio Posts, Recent Posts, Related Posts, Social Icons, Social Icons Alternative, Side Navigation, Twitter and Flickr.
Which one of the above widgets are theme-dependent and which aren’t except Twitter?
The ones for portfolio should be activated when the plugin for portfolio CPT is activated I suppose…
If there are another widget from the above which are not theme-dependent, then there should be a plugin for them I think. Which are the ones that should make part from this plugin and could this plugin to include Twitter widget also or not?
Thanks… This will be my last question today. At least I think…
Ok, thanks for clarifying the above things. Sleep tight!
What about custom theme widgets and metaboxes. I have 15 theme widgets in my framework including the widget for Twitter. All this widgets should be put in a plugin and the twitter widget in a separate plugin?
I also have metaboxes for every page / post below the editor with General Options for Page alignment, custom sidebars, header types etc. The same, another metabox for Backgrounds with options for every page / post header bg and color, content bg and color, footer bg and color and so on. All of these should be part of another separate plugin? There will be errors in pages because nothing from the above won’t be recognized because that plugin is not activated. How can we handle this thing?
Great Japh ! I’ve spent few days to solve the issue with new twitter API a month ago, updated all the themes since I have the option even with a shortcode and separate widget also… And now the things are changing again?... A separate plugin only for twitter which should not use cURL? Thanks guys… seems that all my work and another author’s here was for nothing…
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.