Forum Replies Created

Viewing 15 replies - 121 through 135 (of 261 total)
  • Forum: Reviews
    In reply to: [Tweeple] Fantastic
    Plugin Author Jason

    (@themeblvd)

    Thank you. 🙂

    Plugin Author Jason

    (@themeblvd)

    Wow, I thought I was going crazy. I figured it out, but still have some other things to fix, too, before putting up v0.5.0.

    After the next update, you should have something looking similar to this:

    http://www.themeblvd.com/demo/alyeska/features/layout-builder/sample-layouts/the-webtreats-special/

    Plugin Author Jason

    (@themeblvd)

    This is more of a Theme Blvd support issue. Please post over in our support forum if you’d like more specific help with this:

    http://support.themeblvd.com

    .. And I’m getting the same issue as you now on one of my demo sites. So, I’m looking into it on my end, as well.

    Plugin Author Jason

    (@themeblvd)

    Just wanted to post an update on this. I kicked off the Theme Blvd integration with adding support for the “Tweet” element you currently have in your Theme Blvd theme. — This is as of Tweeple v0.4.0.

    Plugin Author Jason

    (@themeblvd)

    If you were to setup your own function from your own theme or plugin to display the tweets you can use Tweeple functionality something like this:

    function my_tweets() {
    
    	// The ID for the user timeline feed you setup in
    	// the admin. Maybe give it the max limit number.
    	$feed_id = 123;
    
    	$tweeple_feed = new Tweeple_Feed( $feed_id );
    	$feed = $tweeple_feed->get_feed();
    
    	foreach( $feed['tweets'] as $tweet ) {
    		if( false !== strpos( $tweet['text'], '#happyfor' ) ) {
    			//...
    		}
    	}
    
    }
    Plugin Author Jason

    (@themeblvd)

    This might help to explain why it’s difficult to pull Tweets “:from” just any Twitter account with the Search API.

    https://dev.twitter.com/docs/faq#8650

    Plugin Author Jason

    (@themeblvd)

    Hello,

    As of now, there isn’t anything for this. As we move along, I’m going to try and add more integration elements to Tweeple for Theme Blvd themes. I’m still not sure what I’m going to do with the tweet element of the Builder just yet.

    As an alternative approach, there is a [tweeple_feed] shortcode you could use in any content block — there isn’t really any CSS styling though. I know this isn’t anything like the Tweet element, but it will give you some more flexibility of where you can feed Tweet(s) potentially.

    Plugin Author Jason

    (@themeblvd)

    I honestly do not know. —

    I know when you’re fetching a user’s timeline, Twitter API does not give you any way to add in any kind of search:

    https://dev.twitter.com/docs/api/1.1/get/statuses/user_timeline

    And when doing a search, according to the docs, you’re supposed to be able to do this:

    from:you #happyfor

    https://dev.twitter.com/docs/using-search

    … but I’m playing with this and it’s very spotty. I can only get the “:from” to work with gigantic Twitter accounts like @twitterapi.

    Plugin Author Jason

    (@themeblvd)

    Thanks for taking the time to leave a rating and review!

    Plugin Author Jason

    (@themeblvd)

    Hello,

    Are you using a Theme Blvd theme and having trouble getting it to work? Or do you mean you’re using a theme from a completely different author all together?

    This plugin is made specifically for Theme Blvd themes. Theme reason is because Theme Blvd themes have an option built-in where you can configure featured images to have certain links. This plugin taps in and extends that specific option. So, you can see why the plugin simply wouldn’t do anything with any other theme.

    Plugin Author Jason

    (@themeblvd)

    Hello,

    Unfortunately, I don’t think this plugin is going to work quite right with your theme. The way your theme handles the homepage slider is clean and simple, but will unfortunately cause conflicts with other implementations of flexslider within the page (or anywhere else the class “flexslider” is used, which is sort of common when using FlexSlider).

    See here: http://btcondo.com/wp-content/themes/exclusy/script/flexslider/home-slider.js

    Your theme targets the selector “.flexslider” in general to apply all of its settings for the main slider. And then the plugin contains this class within it’s markup, as well. So, your theme is going to inevitably effect this. I think this is where the odd, unpredictable results you’re seeing come from.

    If you’re up for modifying your theme, you could try making the selector in your home-slider.js file more specific. Currently at the top you can see this:

    jQuery('.flexslider').flexslider({

    Try changing to this:

    jQuery('#main-slider .flexslider').flexslider({

    Plugin Author Jason

    (@themeblvd)

    Hello,

    There’s no shortcode for this plugin, as that would add a lot of complications with theme compatibility for the plugin in general for everyone.

    The Layout Builder does allow you to insert “floating widget areas” in the Columns element. That would be one approach you could try. I’m not sure what theme you’re using, or if you’re actually using the Layout Builder plugin, but at some point, an option to feed widget areas into a Content element was added, as well.

    Plugin Author Jason

    (@themeblvd)

    Hello,

    No, I apologize, but there is no option for this in the plugin.

    You could probably just hide the titles with CSS from your theme if you wanted to, though.

    .themeblvd-news-scroller .scroller-header { display: none; }

    Thread Starter Jason

    (@themeblvd)

    I also wanted to point out on this after doing quite a bit of digging with the structured post formats, I have found that “adding theme support” for this isn’t exactly what it seems and I think will cause confusion for many.

    When you do:

    add_theme_support('structured-post-formats', array(...));

    You’re not saying that your theme supports the structured data, you’re saying that you don’t want that data automatically filtered onto the_content(), which is what WordPress’s new posts_formats_compat is. In other words, adding support just means the fallback behavior isn’t applied to the the_content().

    For example, say you had this in your template file for displaying an image format post:

    <div class="entry-media">
    	<?php the_post_format_image(); ?>
    </div>
    <div class="entry-content">
    	<?php the_content(); ?>
    </div>

    Initially, this will show the image inputted through the post format UI twice. You’ll get it once above and once at the bottom of the content. However, if you were to add “structured-post-formats” support for the image format, now it would NOT show the image at the bottom of the_content().

    An alternate approach would be to do this:

    <div class="entry-media">
    	<?php the_post_format_image(); ?>
    </div>
    <div class="entry-content">
    	<?php the_remaining_content(); ?>
    </div>

    In this case you would NOT need to add “structured-post-formats” support because you’re not using the_content() at all. You’re using the new the_remaining_content() function.

    So in what I gather from how all this works, is that the logic of removing theme support for a structured post format and expecting the post format UI icon to be removed doesn’t quite make sense. By default, there is no theme support for any “structured-post-formats” — i.e. that has nothing to do with the UI being presented to the user; it’s all about fallbacks when outputting in the theme.

    This is all going to be confusing for many, but on the plus side there are are now so many potential options we can do in our themes, just accepting that post formats need to be part of the standard moving forward.

    Thread Starter Jason

    (@themeblvd)

    Correct me if I’m wrong, @ipstenu, but I think she was referring to the new filter added to remove the post formats UI.

    http://core.trac.ww.wp.xz.cn/ticket/23929

    add_filter( 'show_post_format_ui', '__return_false' );

    This was added after 3.6-beta1, I believe. So, still very new. It appears someone also suggested the idea of actually being able to remove specific formats in that ticket, which no one really seemed to comment to. (So maybe a chance to get your voice in! 🙂 )

    Also, from looking around, it appears all of this is definitely not set in stone. While it seems likely that post formats will essentially be on by default, there are still discussions about it. But right now, the Post Formats UI in general seems to be a real work in progress. So we kind of need to wait to see how things evolve still.

Viewing 15 replies - 121 through 135 (of 261 total)