Posts by mordauk

731 posts
  • Has referred 500+ members
  • Has sold $125,000+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+7 more
mordauk says




I always built auto-updaters into my plugins that I sold on Code Canyon and was never told I can’t. If TF does not allow it, then that should definitely change. You are also more than welcome to place your plugins in WordPress.org, which will automatically have an update system.

...so then everyone else in the world is free to use our plugins in their own themes (or whatever they like as it’s GPL) and profit off my hard work?

Good one.
Just saying it’s an option. If you do not want to share your plugin (which is fine), then include your own custom updater like @Astoundify mentioned. As far as I know TF does not prevent this, but if they do, it SHOULD be allowed.
I would say it’s likely allowed, the point I’m trying to make is that it shouldn’t be on authors’ shoulders to facilitate this kind of functionality.

Hey, I’m all for TF providing an easier updater solution.

731 posts
  • Has referred 500+ members
  • Has sold $125,000+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+7 more
mordauk says


I always built auto-updaters into my plugins that I sold on Code Canyon and was never told I can’t. If TF does not allow it, then that should definitely change. You are also more than welcome to place your plugins in WordPress.org, which will automatically have an update system.

...so then everyone else in the world is free to use our plugins in their own themes (or whatever they like as it’s GPL) and profit off my hard work?

Good one.
Just saying it’s an option. If you do not want to share your plugin (which is fine), then include your own custom updater like @Astoundify mentioned. As far as I know TF does not prevent this, but if they do, it SHOULD be allowed.
731 posts
  • Has referred 500+ members
  • Has sold $125,000+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+7 more
mordauk says


One major advantage is that you, the theme developer, can now use the same, shared functionality in multiple themes.
Common framework included in theme repo as git submodule does it already and without requiring me to rape existing codebase for the sake of it.

But you still have to update each theme independently when you make changes to the framework.

731 posts
  • Has referred 500+ members
  • Has sold $125,000+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+7 more
mordauk says

I always built auto-updaters into my plugins that I sold on Code Canyon and was never told I can’t. If TF does not allow it, then that should definitely change.

You are also more than welcome to place your plugins in WordPress.org, which will automatically have an update system.

731 posts
  • Has referred 500+ members
  • Has sold $125,000+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+7 more
mordauk says

So, let’s see, our theme is built using shortcodes or a layout builder, the whole homepage for example. If the user doesn’t install any of the theme-related plugins, he gets a blog theme, nothing else, right? And my another little problem would be the fact that, each theme being unique, having one plugin for shortcodes isn’t enough, each theme has individual features, individual shortcodes, basically demanding a new plugin for each theme. And this only for the shortcodes, if you have a portfolio too, you need another plugin. If you have something else, another plugin, we end up selling more plugins than the whole theme itself, let’s not forget that we’re on ThemeForest and not CodeCanyon.

There are always exceptions, but when it comes down to basic short codes (columns, buttons, drop caps, etc) they are all nearly identical, and those that aren’t identical are simply because they were built by different people. There’s no reason a theme needs to build it’s own set of short codes for columns or buttons when the markup for those will end up being the same as all the others. The same goes for things like alert boxes.

If you have a truly unique short code, fine, put it in the theme, but don’t convolute things by re-including all of the basics time and time again.

731 posts
  • Has referred 500+ members
  • Has sold $125,000+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+7 more
mordauk says

@Net-Labs I’m confused by this:

“Your “quick lines of css” is also no easy feat for mr restaurant owner who wants to cook pasta and now have to work through “css for dummies”.”

Where does the restaurant owner come into play with the CSS? That’s handled by the theme developer. With ~50 of CSS you can easily style all of the most common contact forms, so it doesn’t matter which one is used.

In regards to your table booking feature, why not just turn that into your own plugin that you use throughout your themes? I suspect you already have a framework for the features that you include in your themes, so move it into a plugin and it will behave exactly the same, but with a major advantage: you update it once and all of your themes have the new features and bug fixes.

731 posts
  • Has referred 500+ members
  • Has sold $125,000+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+7 more
mordauk says


For example, if your theme is based around major portfolio features (filtering, categorization, grids, galleries, etc), build a portfolio plugin that is built specifically with the features you want, then style / implement the features provided by the plugin in your theme.
and what would be the advantage for the end user ? Once theme is replaced and js/css are gone, it would be useless.

One major advantage is that you, the theme developer, can now use the same, shared functionality in multiple themes.

731 posts
  • Has referred 500+ members
  • Has sold $125,000+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+7 more
mordauk says

One key element of using plugins for features that I think a lot of people are missing is that no theme (without exception) should completely rely on a plugin. A theme should still be fully functional without the plugins, it will just be less. It will be a “standard” theme that does what the core concept behind themes is: style the default WordPress functionality.

If the additional plugins, be it WooCommerce, a page builder, a portfolio, etc, are present, the theme provides complete support for them.

As plugin developers, we follow the same concept often by providing “conditional” support for additional features available in other plugins that automatically becomes available if the plugin(s) is active.

731 posts
  • Has referred 500+ members
  • Has sold $125,000+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+7 more
mordauk says



Also “The text domain parameter must be a string and not a variable or constant.” this is semi silly, there some cases where classes use a constant(filtered) to define the parameter so it can be reused. also there are a few theme frameworks that use a constant.
No, actually is must be a string. Setting it to a constant makes it not actually work.
hmm its working fine for me

I’ll let Otto explain it: http://ottopress.com/2012/internationalization-youre-probably-doing-it-wrong/

731 posts
  • Has referred 500+ members
  • Has sold $125,000+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+7 more
mordauk says

Also “The text domain parameter must be a string and not a variable or constant.” this is semi silly, there some cases where classes use a constant(filtered) to define the parameter so it can be reused. also there are a few theme frameworks that use a constant.

No, actually is must be a string. Setting it to a constant makes it not actually work.

by
by
by
by
by
by