Posts by pixelentity

496 posts
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+8 more
pixelentity says

It has been requested many times in the past. I hope Envato could give someday a solution for this, as this is a very common practise lately, mostly on TF. But don’t think is something with priority on his schedule. Not sure.
yeah, we’re not holding breath.

right now the most viable solution to split earnings is to use payoneer card-to-card transfer: immediate and free (5k per month limit).

However, one author still get all the money first and then manually transfers partner share so team mates really need to trust each other before anything else.

BF

496 posts
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+8 more
pixelentity says

those assets are stored to amazon s3 cdn, meanings each user is loading them from different servers according to geo location.

most likely it’s a temporary routing issue between user isp and a particular server.

BF

496 posts
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+8 more
pixelentity says

Yep closing PHP tag is generally not used, especially on class files.
that’s not the only case, it could also happen with BOM headers: some editors just hide them so one won’t notice until buyers start chasing you armed with forks.

BF

496 posts
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+8 more
pixelentity says

We just had a very nasty issue in a recent theme: some buyers complained about “Headers already sent” warning upon theme activation which caused massive boos like getting blank pages, being unable to login or create new pages and so on.

The issue was caused by a single extra (damn) newline char placed after a closing ”?>” in one of the theme classes file but the real question for us was “how the f**k this didn’t happen with any of the multiple wp installations running on different servers/platforms where we had tested theme ?”

So today, after a bit of research, we figure out that when php outbut_buffering option is enabled, you most likely never get a “Headers already sent” warning. We had it enabled in all our php installations like any other buyer not experiencing the issue.

Our friendly advice would be to turn that option off for your testing machine, i don’t know if theme/plugin installation is part of the review process but if it’s the case, reviewers should also disable output buffering.

BF

496 posts
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+8 more
pixelentity says

Elite money is not free money. It requires 24/7 work
it looks like somebody missed last “Elites” magazine “Grow your own money tree” article ….

BF

496 posts
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+8 more
pixelentity says

payoneer: instant money, has private load and free (no fees) card-to-card transfer up to 5k per month.

496 posts
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+8 more
pixelentity says

care to share the full code. did you add it in a filter function?
yeah, same as quoted example, inside a “the_content” filter

BF

496 posts
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+8 more
pixelentity says

Wow, does this really resolve all cases? That’d be cool :)
    add_filter('the_content', 'shortcode_empty_paragraph_fix');
    function shortcode_empty_paragraph_fix($content)
    {   
        $array = array (
            '<p>[' => '[', 
            ']</p>' => ']', 
            ']<br />' => ']'
        );

        $content = strtr($content, $array);

        return $content;
    }

yes but still there’s a major issue: it gets applied to all shortcodes, including those defined in 3rd party plugins (which is bad).

just spent some time on this, and replaced the above with some regexps:

https://gist.github.com/3776987

It basically works the same way but only on your blocklevel shortcodes defined in the array (“col” in the example)

BF

496 posts
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+8 more
pixelentity says

there are 3-4 topics about that every day.
not to mention the ones posted in items comments, sent by author profile form or posted to dedicated support forums.

BF

496 posts
  • Has referred 1000+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+8 more
pixelentity says

Our intention is not having buyers to sign a life contract with us when selling them our theme and we’re defo not against a clear separation of functions/presentation in plugins/themes.

What we think it will never work here is each author shipping his own custom plugins to handle shortcodes and cpts, meaning plugin from author A not being compatible with ones from author B because of different names/parameters and so on. How the hell this is supposed to make buyers life simple is beyond me.

Now this thread kinda evolved since the original opener posted his question and the above situation is very different from all (or most) authors using the same plugins. Which do not exists yet or, at the very least, there’s not a general agreement between authors on which ones should be used.

I can see this happening on TF only if Envato release such plugins on wp.org itself, providing support and keeping them updated with authors being able to give feedback on bugs and request missing features.

Then a “Compatible with Envato $coolname” option would be added to item page, allowing users to filter the set and only show compatible themes. When buyers know they can switch between any of them with minimal (if any) pain, they will most likely pick one of those instead of a “franken-theme” and you’d slowly create a trend.

More and more authors will join the club, not because a rule forces them to but only because not doing it may cost them sales.

BF

by
by
by
by
by
by