+1-888-365-2779
Try Now
More in this section

Forums / Project Feather / Feather sf-html-field custom layout options

Feather sf-html-field custom layout options

4 posts, 1 answered
  1. Frank Osako
    Frank Osako avatar
    4 posts
    Registered:
    27 Dec 2006
    05 Jul
    Link to this post

    We are working on a feather implementation, and are having issues adding custom layout options to the individual package. 

    At this time, we have followed the direction of the following url:

    http://www.sitefinity.com/developer-network/forums/project-feather/custom-designer-for-custom-widget-isn't-registering

    and

    https://github.com/Sitefinity/feather-samples/tree/master/CustomStylesContentBlock.

    Both items have been implemented, however I am not seeing any of my custom classes.  What would be my next steps.

    Any help would be greatly appreciated.

  2. Mariush
    Mariush avatar
    43 posts
    Registered:
    08 Aug 2014
    06 Jul
    Link to this post

    Hi Frank,

    Which page template you based your page on? If you are using a page template from a ResourcePackage, you may need to modify the html-field of that resource package. 

    For example, if you are using Bootstrap, you need to add the extra styles in: \ResourcePackages\Bootstrap\client-components\fields\html-field

    Please give it a try and let me know if it helps.

    Mariush

  3. Frank Osako
    Frank Osako avatar
    4 posts
    Registered:
    27 Dec 2006
    06 Jul in reply to Mariush
    Link to this post

    Thanks Mariush,

    I'll try that again.  The ResourcePackage I am using is based off Bootstrap. I basically copied all the contents of Bootstrap, renamed to SitePackage and modified the contents to meet my needs . 

     

    Would you see any issues with a custom made ResourcePackage, or is there any hidden gotchas that I may be running into?

     

    Thanks

  4. Frank Osako
    Frank Osako avatar
    4 posts
    Registered:
    27 Dec 2006
    06 Jul
    Link to this post

    Mariush,

     

    In my instance, I followed directions and examples correctly.  The issue actually lied within the output cache within the administration.  Once I had viewed in a new browser my changes were being made.

     

    Therefore, in my instance I disabled output cache for development, and cleaned out my browsers history and all was good to go.

    Answered
4 posts, 1 answered