We asked support about this recently. In our case it was concerning a HTML template which was old but popular. When building a WP version of it recently, we completely rebuilt the original HTML template, adding responsiveness, bootstrap framework etc, and were wondering if there was a possibility of releasing the rebuilt version as a new template.
Basically support told us the answer was no, unless the new one did not look like the old one (totally new design), or that it had some significant additional features, which would enhance the template’s fundamental use ( e-commerce support ). There was a 3rd condition, which I can’t remember now, might have been something like if it’s made using a different technology (Drupal, WP, Magento etc.)
So in the end we did nothing with the old template.
Smuliii saidyou’re right, doesn’t require the extra “[raw]” but the principle is the same: it only gets applied where it should and leaves native/plugin defined shortcodes untouched.
I really can’t say what’s the difference between mine and your code (since they both modify ‘the_content‘) but if this is accepted, I’ll start using it then.
We use in all our themes, only thing is we always include a note in “reviewer info” box to explain how it works just to be safe.
Needed to add a custom image filter, again no docs on the subject, most likely broken the swearing world record, here’s an example:
Here’s an alternate method which relies on events to restore the original function after the image has been added or the uploader closed by clicking “close” button or using “ESC” key:https://gist.github.com/4452118
Hey, Sorry to hear about this.
If you are having this amount of trouble getting the first dollar out of that author, then I would advise you to jump out of that deal at light speed! If its like this now, what will it be like in months to come? The trust has been broken and cannot be repaired.
I would advise any author not to collaborate without protecting themselves. Like this situation and many others I have heard from friends working here on TF, it is not as easy as you think to find a skilled WP developer with the required amount of professionalism. Think before you agree with random authors, you could be depending on them to send you monthly earnings for 1-2 years, if the file has a good selling lifespan. This is a serious business deal.
This is why we sign a declaration with each author with whom we collaborate. They are agreeing to licence their work to us to convert it into a WP Theme provided we pay them their agreed share of the monthly earnings as licence fee. Payments dates and methods are all written down and agreed. If payment doesn’t happen then we no longer have a licence to use/sell the author’s work, its a simple as that. This paper makes it all clear for both parties and for Envato, in such case as they require some proof of the collaboration.
So next time you should work with us instead