Posts by Japh

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

My flights are all locked in now too! Very excited to hang out with you all :)

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

Hey AvaxTheme, as you asked me specifically on Twitter, I will post a reply here.

So, the rejection message you received as a hard-rejection effectively means that the reviewers found your theme wasn’t up to standard. So much so, that the amount of changes you would need to make, would effectively make it a new theme.

Take the advice of other authors, and hopefully you can get some good feedback to help you on your way.

Don’t give up though! When your theme gets to a stage that the reviewers believe it’s almost there, they won’t hard-reject, but will give you feedback and help work out the last issues.

Good luck!

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

Hey everyone, just letting you know I’ve been swamped with other things, but I haven’t forgotten you. This thread grows at an amazing pace!

I’ll be aiming to respond to your questions within the next week. Thanks for being so patient!

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

I think you guys misspelled “CHICAGO.”

Yeah, maybe we’ll hit the east coast next time.

It’d be awesome to catch up with you again!

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

hmm… might have to intercept him as he flies over Europe :D

I’ll be stopping in Europe for WordCamp Europe on the way, actually. Meet you there? ;)

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

I’m very much looking forward to meeting those of you who can make it! Should be loads of fun :)

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

Hey everyone, I hope the following responses help provide some clarifications.

If I missed your question, or my response is actually more confusing than clarifying, I apologise and will happily clarify further.

Again, I apologise for the long reply, and the long wait, I didn’t expect 6 pages! ;)

====================================================================


Continue to my above question: If the theme must be running without my plugin, I think the metabox and options both need to in the theme. Otherwise the user just got a twentytwelve theme after they paid $30-50.

Agreed :)


I have two question though, and i’ll take a practical example to illustrate my concerns. Let’s take my theme WowWay. I have two custom post type, but let’s say that i’ll move all the functionality inside a plugin and do the following:

...

Maybe i wasn’t too clear, but i would definitely like to hear your input on these concerns of mine.

I agree with @ChapterThemes’ reply to you on this.


Assumption is the killer of all!!!

I have in-fact owned my own web design agency for 10 years now, we have well over 50 WordPress clients a year (Not much I know but I tend to not push WordPress due to it being heavy code) and not once have I ever been asked these questions.

Please don’t think I’m against this because I am not, I think its a good thing that users will have easy to switch theming but they are not the problem.

As every author on here knows, its the bad developers, who like to steal code, this just makes it easier to do this, because all they have to do is change a few variables and style them and voila they have there self some amazing functions.

I felt for sometime that authors have been taken for a mug a lot by some authors and Envato, and it just seems that we will get more frustrated by theft than we did before.

Envato in the past just say: “You are the copyright owner and you need to fight it”.

I think if you are making things more transparent for thieves then we need more help from yourselves!

You’ve been lucky not to have been asked then! :)

Regarding thievery, can you please elaborate on how you think this creates/exacerbates a thievery problem?


Question 1: Is it allowed to let a plugin check the current theme info and let it only work if the info matches the theme it has arrived with? Question 2: Is it allowed to require the theme purchase code as a setting before any of the plugin features work?

I would need to check this with the review team. Though I imagine if this kind of behaviour was acceptable, it would be better to do it by requiring the key to access the plugin prior to install, rather than having the plugin there but disabled.


basically when a user sets the Twitter Widget ID in the admin in one place, versus having to put that Twitter Widget ID in a input field in every Twitter Widget block.

This seems to me like it could be just as easily done in the plugin.


i can see how both possibilities they can do now, but it looks like that making the slider options into a plugin, just make it easier for people to just grab your code since now its portable via a plugin

I already am using TGMPA. How would you make it available on a server with a key?

Also what the point on making slider options into a plugin, when a user can not use it on another theme, since all the files for it to work on the frontend are in the theme itself??

thanks again JAPH !!

See @QBKL’s post above yours.


What made Envato/Themeforest what is it today is using “complete-website-in-one-for-$45” as a selling point, if they were simply skins from the start there is absolutely no way it would be as big as it is today.

This is an interesting point, because in my personal experience of assisting freelance clients with ThemeForest themes, this was certainly the original selling point, but it quickly became obvious that there was a lot more work involved in actually getting the theme to play nicely.


Suppose that I have one plugin that can handle all the functionallity, however when it is activated nothing shows, because I must initiate parts of it somewhere. Now the question I want to know if this is allowed, to init these parts inside my theme or I must create another plugin for this(let’s say “Theme Functions”).
Example:
Plugin Core: contains multiple PHP classes.
class My_Metabox {...}
class My_theme_Options{...}
class My_CPT{...}

Theme: Init these classes inside my theme so when the user activate my theme and if the plugin(Plugin Core) is activated it will show the options required for this particular theme:

if(class_exists('My_Metabox ') ) {
    $meta_options = array(
        //all options for my metaboxes
    )
    new My_Metabox($meta_options);
}
//A similar call for other classes: My_theme_Options, My_CPT, etc.
...

So, is allowed to do such calls from theme?

I guess it depends what you mean by ‘init’, but assuming you are describing something like WordPress’ add_theme_support(*) functions, that sounds sensible to me.

Essentially, the plugin has certain functionality that themes can then opt to support. The plugin then should display the configuration options for the aspects of functionality that are a) generically needed by the plugin, and b) that the theme has opted into.

The theme doesn’t need to do anything more than say to the plugin “Enable X functionality please, and I will provide styling overrides etc. for it, you handle the configuration”. Make sense?


Im not just randomly saying this. The reason i said that my slider options and theme options need to go in a plugin, in Phase 2 starting in November, is because that’s the answer Enavto Support gave me TODAY when i emailed them about it. They said they will be requiring all functionality, even theme and slider options and pages ported to a plugin. Thats what they told me. So thats what im going by!

Can you please provide me with the support ticket ID on this so I can clarify?


Can you please clarify an issue we are having regarding a support email reply we have received regarding these new requirements? The actual back-and-forth conversation is too long to post here but here is a snippet

Can you please provide me with the support ticket ID on this so I can clarify? The requirements are the requirements. If we change them, they will be updated.


So if a user installs and activates your theme and plugin and everything works fine, then switches to new theme, your plugin metaboxes and CPT no longer show? Is this the general idea?

If so, doesn’t that defeat purpose of making it a plugin to begin with? Plugin idea is to allow user to access the information no matter what theme they use. I think it should always show in backend, but maybe not do anything or not look good on the frontend if the plugin is activated on a theme you didn’t create it for.

Maybe I misunderstand what you mean.

This should definitely be taken into account. On deactivation, nothing should really be deactivated to the point that a user loses access to their data, surely?

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

Your mean is that: If the user does’t install my plugin, my theme still needs to be running. Just lose some featrues from the plugin. Is it right?

In most cases I would think that would be desirable, yes.

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

Any thoughts on what would stop another developer or user from stealing code from the easy accessible plugins? And do we have to make all slider options into a plugin?

Can you explain a little further the scenario you imagine them getting access to the plugins?

I can think of two possibilities:

  1. File access to the theme or WordPress install, and taking the plugins
    If they have this level of access, nothing is stopping them doing that now.
  2. URL access to ZIP file of plugins in the theme’s subdirectory
    An option would be to utilise a different method of distribution. Have the theme install the required plugins, via TGMPA (or similar), from a repository or server that requires a key. Soon, CodeCanyon will support this (as ThemeForest does), for example.

Thanks again JAPH for answering our questions so fast!! :)

My pleasure! :D


You recommend us to add the funactions via plugins as much as possible, so I want to know, if the user only installed my theme, but not installed my plugin. I will not let the theme run. Does it allow? Other words, the user must installed my plugin, then the theme will run.

Hi Matt! Ideally, the theme would “gracefully degrade”. That is, it will still work, but the functionality provided by the plugin will be missing.

As an example, let’s say it’s a restaurant theme, and requires a plugin that enables various custom post types (such as menus etc.). In this case, with the plugin disabled, ideally it should still look roughly like the general aesthetic of the theme, but it won’t have nicely styled menus, etc.

Does that make sense?

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

It’d be kind of nice if blockquotes were expandable and collapsed by default on long posts, wouldn’t it? ;)

(Sorry!)

by
by
by
by
by
by