Forum Replies Created

Viewing 15 replies - 76 through 90 (of 134 total)
  • Plugin Author Arunas Liuiza

    (@ideag)

    Hi and thanks for suggestion.

    Autosave was actually introduced in the latest version of Gust. It utilizes the same process WP Editor does.

    Plugin Author Arunas Liuiza

    (@ideag)

    Hello again,

    You have to enable OpenGraph support on Yoast. Follow instructions from Yoast knowledge base: http://kb.yoast.com/article/219-getting-open-graph-for-your-articles

    Once og:image meta tag shows up on your pages source code, Content Cards should pick it up. You should also note, that Content Cards caches the data it extracts from the link, so if you tried embedding the link before it had proper meta data, it will take Content Cards a while to refresh the cache. There is a setting i Content Cards Settings screen, that controls the caching interval.

    If you want to force Content Cards to recrawl the link, you can add a meaningless query string to the end of the link, that way Content Cards will treat it as a new link. For example you can change http://domain.com/article to http://domain.com/article?sddffsd. That link will still point to the same article, but Content Cards will recrawl it and get the updated data.

    Plugin Author Arunas Liuiza

    (@ideag)

    Hello and thanks for trying Content Cards out.

    Content Cards rely on OpenGraph data to generate the rich snippet. The link you are trying to embed (http://dragosteadinfarfurie.ro/blatul-de-pizza-preferat/) does not provide og:image meta tag, so Content Cards does not get the information about the image.

    As you are trying to embed from your own site, the solution would be to provide said meta data. You can enable that by using one of a handful of plugins – Jetpack, Yoast SEO and many more. The plugins I mentioned above do much more than insert the required metadata, but there also are small plugins, that do just that, like [OpenGraph](https://wordpress.org/plugins/opengraph/) and others. Any of them will do the job.

    Good luck, Arūnas

    Plugin Author Arunas Liuiza

    (@ideag)

    Hi,

    You can overwrite the template by putting content-cards.php file in your theme’s directory. We have some details about that in our FAQ, under Skins section.

    We have plans to include more skins in future releases, having picture on the side of text is one of our most requested features, so we’ll probably add that in near future. If you would like to help, you can always fork our repository, create a new skin and submit a pull request on GitHub. We’d happily add it to the plugin.

    Regarding chose-able image – we don’t have that feature at the moment. I am putting it to our suggested features list, but that would be a bit involved technically, so this feature will not happen very quickly.

    Forum: Plugins
    In reply to: [Content Cards] Fatal Error
    Plugin Author Arunas Liuiza

    (@ideag)

    Well, the idea was to blend in to the ‘natural’ look and feel of WP admin, so I guess we did a bit too good a job on the icon 🙂

    Forum: Plugins
    In reply to: [Content Cards] Fatal Error
    Plugin Author Arunas Liuiza

    (@ideag)

    In 0.9.1 we replaced “CC” with an icon. You should see a button like in this screenshot: http://i.imgur.com/emaSWMC.png. We’ll have to update the readme.txt, thanks for noting that.

    Forum: Plugins
    In reply to: [Content Cards] Fatal Error
    Plugin Author Arunas Liuiza

    (@ideag)

    Issue should be fixed in 0.9.3 that was just released. Please let us know if any more issues arise.

    Forum: Plugins
    In reply to: [Content Cards] Fatal Error
    Plugin Author Arunas Liuiza

    (@ideag)

    Hello! Thanks for trying this out and reporting. We’ll have a fix released shortly!

    Plugin Author Arunas Liuiza

    (@ideag)

    Hi,

    This is a second request for that, so, I will look into it and will try to get this working in the next release.

    Arūnas

    Plugin Author Arunas Liuiza

    (@ideag)

    Hello,

    I do intend to develop this further, but I have limited time available. I try to deliver bugfix’es asap, but feature development timeline is a bit unpredictable. And slow, I have to admit.

    Plugin Author Arunas Liuiza

    (@ideag)

    Hi again,

    As the example of filter usage, the script will always set callback urls to the current link.

    add_filter( 'tinycoffee_options', 'arunas_filter_callbacks' ) ;
    function arunas_filter_callbacks( $options ) {
      // get the current url
      global $wp;
      $current_url = home_url(add_query_arg(array(),$wp->request));
      // modify tinycoffee options array
      $options['callback_success'] = $current_url;
      $options['callback_cancel'] = $current_url;
      // return modified options array
      return $options;
    }

    As for Your scenario, I think you should use JavaScript to trigger the modal, and you could modify the form fields at the same time, again, using JavaScript:

    jQuery( function($){
      $('.more-link').click(function(e){
        // modify form fields
        var url = $(this).attr('href');
        $('#modal-container input[name=return]').val(url);
        $('#modal-container input[name=cancel_return]').val(url);
        // open tinyCoffee modal
        openCoffee();
      });
    });

    Note – the above code snippets are concept only, I haven’t actually tried them. There might be typos, etc. but they illustrate the general idea.

    Plugin Author Arunas Liuiza

    (@ideag)

    Hi,

    Since 0.2.0 (latest) version, I introduced a tinycoffee_options filter. It is not yet documented, but it allows to modify pretty much every possible option, callbacks included. Also, all the options can be overwritten in shortcode mode, via arguments.

    Arūnas.

    Plugin Author Arunas Liuiza

    (@ideag)

    Hi,

    Thanks for your remarks and Kind words. I’ll look into the icon issue.

    About the images – they work the same way as in Ghost. Just type ![]() or use a shortcut (Ctrl+Shif+I) to insert it and in the preview screen an upload pane will show up.

    Thanks again!

    Plugin Author Arunas Liuiza

    (@ideag)

    Hi,

    Not at the moment and it will not be, unless you can convince me storing Markdown directly into post_content would not be a very bad idea 🙂

    My current reasoning is as follows: The main idea of Gust is to get best of both worlds – a very nice editing experience from Ghost and a robust and powerful theme/plugin ecosystem from WordPress. To achieve this, Gust has to be as compatible with other plugins and themes as much as possible. Most of WordPress plugins that deal with post content expect post_content to be stripped down HTML + some shortcodes (shortcodes output HTML too, so more of HTML, really). Having Markdown there directly could (and will) result in breaking functionality of those plugins. Themes are also written in a way to expect HTML in post_content, so the same reasoning applies.
    I can achieve compatibility in two ways – I could convert Markdown very early on post_content read calls by filtering the_content et al, or on write calls (when saving). I think doing it on read calls is a bad idea, because:
    1. There are a lot more read calls than write calls. Markdown generation isn’t the most expensive call to run, but I would still prefer to do that a lot less times, if I can.
    2. Even if i hook in very early into the read calls, another plugin could still hook-in earlier, for very different reasons. And things could still break, so doing it on write calls is safer compatibility-wise.

    If you have reasons which you think outweigh mine, I’d be happy to hear them and reconsider.

    Plugin Author Arunas Liuiza

    (@ideag)

    Hi, Gust lives together with WP admin – you can access and use both of them, as you see fit via Admin Bar, or directly via /gust and /wp-admin respectively. Gust is just editor, it is not meant to handle widgets, menus, settings, etc.

Viewing 15 replies - 76 through 90 (of 134 total)