RafalBorowski saidthat’s exactly what that code does. You cannot strip whole “autop” feature by removing the filter or using code which has the same effect, that would break other plugins and your theme would not be accepted here.
OriginalEXE saidThanks, but that does still not solve the problem like adding p or br between (before and after) shortcodes
Check this out: https://gist.github.com/bitfade/4555047
jessengatai saidLast time i checked there was no hook to customize that area. I feel the core team wants that area to be consistent regardless the theme so there could be no way to customize its content.
- I haven’t figured out a way to add additional metafields above the content window along with all the other new metafields. Meaning, if I want to add more options for some post formats they need to go below the post content. Which is where they would normally go – but thats going to be really troublesome for people to change things to 2 places now.
ThemeBlvd saidthe question raised in the GPL thread but there was no official answer so we thought to share our direct experience.
As an author making the change to full GPL, this kind of advice (along with Chris’s advice, as well) does help to make me feel little more comfortable about such a big transition.
Historically, Envato has dealt with such issues by requesting dmca notices but not this time: they asked for evidences, conducted an investigation and enforced house rules. I think that’s very important for authors because it shows our work is valuable for Envato and worth the time and resources needed to protect it.
chrisakelley saidare we allowed to place our name in every file ? i kinda remember a forum thread where it was said we were not (i could be wrong). Anyway, it still applies in case the original copyright notices aren’t removed.
DMCA can apply to GPL. GPL is essentially a copyright license requires that all copyright notices stay intact, if any of the copyrights are removed you can file a DMCA.
yep, that’s your pic but we weren’t sure if allowed to disclose in public
We recently discovered an author using our WordPress framework to release a theme on Themeforest. According to the GPL licence this is allowed, and we would have no issue with that code being used outside of Envato’s marketplaces, but as Collis pointed out in a forum thread recently, reselling GPL code on Themeforest which was bought/obtained from themeforest, is not permitted (without permission), and rightfully so.
We contacted support and provided evidence. Despite the author renaming class/methods and/or adding/removing code, the rip was still very obvious. The theme was first soft disabled and has now been permanently removed.
WP themes code is GPL, hence a DCMA doesn’t apply to this situation, nonetheless, Envato has it’s own in house rules about these situations. So for any other authors out there who discover another author reselling their WP GPL code, don’t be afraid to report it, Envato are paying attention to these things. To any authors out there considering other author’s GPL code as a a way to cut corners or make a quick buck, DON’T!
Thanks to Jami for her help in the matter.
did that yest, forgot to post: it’s around 88M usd considering the lower badge value