Fork me on GitHub

pnRender module-centric stylesheets?  Bottom

Go to page [-1] 1 - 2:

  • Are you using the Header_Footer module?

    --
    itbegins.co.uk - Zikula Consulting

    birtwistle.me.uk - Personal Blog


    Please read the Support Guide
  • No... but then again, I don't want EU's to have to be using it either... I want just a single module install to be fully working...
  • The Header_Footer module is a core module, and it's a very good idea to use it if you have a classic theme. Not that I've used it with an AutoTheme...

    --
    itbegins.co.uk - Zikula Consulting

    birtwistle.me.uk - Personal Blog


    Please read the Support Guide
  • OIC...must be for .760 then? My .750 doesn't have it... I don't use the classic themes, only custom jobbies written for AT.
  • Might just be .760. I honestly can't remember as I upgraded all of my sites to .760 months ago...

    --
    itbegins.co.uk - Zikula Consulting

    birtwistle.me.uk - Personal Blog


    Please read the Support Guide
  • Quote

    Line 3 makes no sense to me...


    It would only make sense if you you were using a legacy theme, as far as I know. The present version of AutoTheme uses it's own headers, I think. You are using AutoTheme?

    I still think your stuck with doing it the way you described above.
  • It's a feature of the upcoming PN 0.76, the Header_Footer module doesn't exist in PN 0.75. The point is to have templated Header/Footer output for legacy themes.
    What you can do for styling in general is use the additional_header array in the module code, eg

    Code

    global $additional_header, $bgcolor1, $bgcolor2;
    $additional_header[] = '<style type="text/css">
    .AlarStyle { color: '
    .$bgcolor2.'; }
    </style>
    '
    ;

    It puts the style in the Head section.
    For the Option list, build it in the module code as an Array, and use Section or Foreach to cycle over it in the template.
    Prebuilt functions like html_options have limitations.
  • @msandersen - Ok... that seems logical enough. I wonder if I could just fread the CSS file into a $var and then use $additional_header[] = $var; ... I'd like to avoid putting the sheet info into the mod-code directly if possible since people are inherently going to look in pnstyle/style.css for the sheet.

    @denisrf - Yes, an AutoTheme.

    Since pnRender is all about templating and giving the end-user more options and control over the layout, one would think that this issue would have been addressed across the board.

    seems a bit proprietary...:|
  • alarconcepts

    @msandersen - Ok... that seems logical enough. I wonder if I could just fread the CSS file into a $var and then use $additional_header[] = $var; ... I'd like to avoid putting the sheet info into the mod-code directly if possible since people are inherently going to look in pnstyle/style.css for the sheet.


    Of course, there's a bit of a caveat that way too... (eg) won't correctly parse when placed in a CSS file... so I see what you mean about putting it into the mod-code. Perhaps reading the file in and doing a str_replace could solve it...
  • I'd just use the pnRender include file plugin / thing (I know what I'm talking about, even if you don't), to include the stylesheets I want - though apparently that didnt work for you?

    Quote

    Ok, so a regular pnRender file include doesn't do the trick


    --
    itbegins.co.uk - Zikula Consulting

    birtwistle.me.uk - Personal Blog


    Please read the Support Guide
  • I used this:

    ...this does include the CSS file...however, it's included as plain-text and the contents are displayed onscreen...
  • Yes, that does hide it from displaying... only one problem... it's not put into the .. it's put into the ...
  • I tried the $additional_header method to no avail as well.

    I appreciate the help everyone...

    ...was hoping for an "approved" method, but it seems that's not going to be the case. I want to avoid doing anything hacky so I think I'll have to live with the inline styles...
  • The Header_Footer module is only included in PostNuke .760 not in PostNuke .750.
    This is a change in the .760 release : all NON XANTHIA (legacy) themes use the footer_page.htm template !!!
    So you can use this template to include what you want. For instance you can remove the tag in this template and replace it with or or to use another editor (of course the corresponding module should be installed and activated) with non xanthia themes.
    And yes there was a typo in my post because it is modules/Header_Footer/pntemplates/header_footer_page.htm (slashes not backslashes, windows fault !!)

    --
    Visit my live reef aquarium.

    My Amazon wish list.

Go to page [-1] 1 - 2:

This list is based on users active over the last 60 minutes.