Posts by pixelentity

501 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.

501 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

501 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

501 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

501 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

501 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

Nonsense. TF theme authors could easily code a plugin for use with their themes in which the CSS and JS necessary to power the functionality could be overridden by including specific files in the theme directory itself. It actually makes it easier for TF theme authors this way since authors can offer a consistent operational experience across all of their themes from a single plugin codebase, and yet still offer each theme a specialized look for that functionality.
sure thing, i can tell by the number of top TF theme sellers posting in this thread, there’s a serious interest in building a common framework.

which would also be pointless since, by the look of things, only a couple of authors here know how to code themes.

BF

501 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

Im guess the better question is what dont you think could be done? the only thing I could really think of is if the plugin used A script for a slider shortcode and you wanted to use b script instead , it could be filtered(but wed still be at the same issue as the start it would break on theme change)
Which is why it will never work: complex shortcodes like gallery, slider, filterable portfolio requiring all kind of custom css/js.

btw, since this common shortcode component doesn’t exist (hardly believe it ever will), the original question still remain unanswered.

By moving theme features in custom plugins, who’s going to support the buyer when nothing works out of the box ?

BF

501 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

have you heard of filters? a properly developed plugin this wouldn’t be an issue, as long as authors use those filters(and modifying the styling) real question how many buyers actually use shortcodes?
yes and ? a bunch of filters in this collective shortcode plugin will cover every author needs so it could be used into each TF theme ?

can we assume whoever posts in this thread actually knows what he’s talking about ? because a certain wordpress evangelist tone assumed more than once in this thread starts to get really annoying.


real question how many buyers actually use shortcodes?
a lot. They even asks for more and somebody pay for custom ones also.

BF

501 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

Irrespective of whether the practice of embedding shortcode behavior in a theme is the “correct” thing to do or not, it the most practical approach when selling theme on a premium marketplace like TF. The original poster asked why do authors not account for the situation when a buyer wants to change their theme later on, while keeping their current layout which has been created using embeded shortcodes. The answer to this is because it to complicated and impractical.

Many of the complex themes here on TF use a range of different frameworks as a basis for developing a theme. All of these frameworks require layout elements to use specific markup and specific CSS . Because of this, it would be almost impossible to create a plugin which your buyer could use with your theme and then keep using with a totally different theme. At the very least, even if the framework was compatible, the whole CSS of most shortcodes would need to be changed to fit the style of the new theme. This is not something which TF buyers want to have to do after buying a premium theme, and as such is not a recipe for good sales.

Assume then that you want to be a very “correct” developer and you only make plugins for your own themes and dont care what happens when your buyer changes theme later on. Well then you are back at square one, only now you have to support your less experiences buyer while they struggle to install/ update your range of plugins. You also now have several different code bases, instead of one if the shortcodes were intrgeated into your framework. Furthermore, when your buyer does change theme and your plugins spits out the markup suitable for your theme, inside a 3rd party theme, then they will come looking for support and answers why this plugin is not working. This hence doesn’t achieve anything except giving yourself more work.

While it may be possible to produce a free plugin which would output the most generic markup and css which would have some chance at rendering in most themes, this would put a severe restriction on your shortcodes complexity as well as bring you a lot of support requests. This tradeoff is not worth it, neither for you nor for your buyer. Nothing is achieved except “correct” development, which actually doesn’t solve the original poster’s problems.

DOK

501 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

scenario: autor A releases theme + own coded plugins which break/no longer work with author B theme.
question: who’s going to support the buyer and why.

BF

by
by
by
by
by
by