To insert code use <code>...</code>.
CLOSED - Some issues, Some requests
  • This is not issue with the latest (3.0.5) release, those existed in previous versions as well.

    First, if I add tag for excerpt, it works fine in Blog page, i.e. it cuts the text at the place I specify. But I added blog posts via short-code generator on my home page and it ignores this tag and cuts the text after the default number of chars as if there was no tag at all.

    Secondly, RSS2 feed should NOT show class="image_shadow", in the feed it display two images (main and shadow), side by side..

    In addition, I have two request. One is related to the first issue above. I like that text is automatically trimmed if "Show full" is not selected, however could you add a check if exists and if it does cut it on that place, not on the default place. Sometimes I need some more text to be displayed in excerpt and this automatic trimming does not allow me to display it..

    And the main feature which would be really useful if you could add ability to add custom code for feature header section. Currently it is just custom title and description or a slider, but I would like to add some other things before the main content.. short-codes should also be supported.

    Overall, you are doing really excellent job, very well done!
    Thanks!

    RSS FEED.png
    464 x 319 - 71K
    Screen shot 2011-06-12 at 21.30.02.png
    421 x 173 - 21K
    Screen shot 2011-06-12 at 21.30.19.png
    418 x 192 - 22K
  • 9 Comments sorted by
  • Hi nesako

    Good points. For your main feature, if you want something like that immediately, it would be easy to do using the function.php and some Wordpress filters. Could be conditional based upon a category or page.

    If you want some code for that email me through the forum or runner2009 (AT) gmail (DOT) com
  • Hi nesako,
    These will fixed in the new release of striking. Just look forward to it.

    For custom code for feature header section, why not set 'Feature Header Type' to 'custom text', then use the shortcode in 'Feature Header Custom Text'?

    Regards,
    KaptinLin
  • Thanks for advice!

    I am sure I tried using shortcode in Feature header custom text before in previous version of Striking and it did not work, but just tried again and all is good, so I am 100% happy with this feature :)
  • Just before closing this tread, what should I modify so the Portfolio title would link to the portfolio item as currently you can only navigate by pressing the featured image.. It would be a nice addition in the next release to set if portfolio title should link to full portfolio page or not and then this would be possible: you have portfolio with type image, by clicking the image it zooms in and if you want to read the actual portfolio you just click the title and it goes inside it..

    Thanks
  • Hi,

    You can unzip the attached file to striking\framework\shortcodes folder.

    Then add

    titleLinkable="true" to portfolio shortcode.


    Regards,
    KaptinLin
    portfolios.zip
    4K
  • KaptinLin,

    I've integrated the code above ^^, thank you. It works however if the portfolio is sorted the links no longer exist.

    example:
    http://woskalawfirm.com/areas-of-practice/pharmaceuticals-and-medical-devices/
  • Hi,
    You can unzip the attached file to striking/js folder to fix it.

    Regards,
    KaptinLin
    custom.zip
    4K
  • I was having a somewhat different problem with the portfolio that I was hoping the fixes above would address, but they did not. I have two Cufon fonts active and have specified one of them to control the .portfolio_title class under Cufon code. When the portfolio page is first loaded, the correct Cufon font is applied, but if the portfolio is sorted, all portfolio titles revert to the other Cufon font. I had a similar issue with the top menu navigation (second font would appear after hover) until I removed [cufon.replace $ > a] from jqueryslidemenu. Any thoughts?

    Example: http://hudsonriveragent.com/wp/developments
  • When the portfolio page is first loaded, the correct Cufon font is applied, but if the portfolio is sorted, all portfolio titles revert to the other Cufon font.



    I resolved the issue - in custom.js, under the section controlling the custom portfolio sorting, there is an if statement (checking if cufon is defined), in the 'else' section, I manually added the cufon font name - '.portfolio_title', {fontFamily : "ColaborateLight"}

    Fixed! (But this should probably be addressed permanently in an update. Thank you