Core Modules & Blocks  :: 
News/Sections not rendering HTML if no quotes are around attribute values
 Top

  • Hi, the news and sections does not seem to render HTML where the attribute values are not surrounded by quotes...
    i.e.

    Code

    <span class=blah>Some text</span>

    Renders as source code where...

    Code

    <span class="blah">Some text</span>

    Will render correctly... Yes, I know without quotes is not correct but that's the way the WYSIWYG is rendering it and it's what I need to work with...



    Does anyone have a fix or is there some options I am missing?

    --
    Get PhotoGallery, PayPalCart, Dynamenu, Enhanced Blocks & other mods

    Cape Cod Travel Info...
  • Nate,

    Two options....

    1) get a better editor.... icon_wink we're getting rid of typetool very soon.
    2) Swith the parser back to the old non XHTML parser

    In pnAPI uncomment line 634 and comment out line 632.

    -Mark
  • Thanks for the reply Mark - I had an inkling it could be reverted in pnAPI - works like a charm...

    As far as a better editor - that would definately be my first preference, beleive me - A project I have "on the boards" is to put together my "dream editor", likely starting with TinyMCE and some lesser known "plug-ins"... I think I have a thread somewhere describing what that would be...

    --
    Get PhotoGallery, PayPalCart, Dynamenu, Enhanced Blocks & other mods

    Cape Cod Travel Info...
  • Nate,

    I've got a project at noc.postnuke.com for tinymce. My intention was to work primarily on keeping a base tincymce install up to date. If you want to help add further plugins to this that would be great - let me know if your interested and i'll add you to the developers/admins list for the project.

    -Mark
  • I am having this exact same issue, only it is a fresh install of PostNuke .764

    You mentioned in your post to modify lines 632 & 634 in the script called pnAPI.php; however These line numbers don't seem to line up with the lines in this script. Please explain which lines of code need to be commented out to resolve this issue. It's very annoying that none of the HTML code is working properly. I would like to resolve this issue before I go live with my website.

    Any assistance would be appreciated.

    Regards,
    Jerry Grogan

    markwest

    Nate,

    Two options....

    1) get a better editor.... icon_wink we're getting rid of typetool very soon.
    2) Swith the parser back to the old non XHTML parser

    In pnAPI uncomment line 634 and comment out line 632.

    -Mark

  • Try Scribrite, instead.

    --
    David Pahl
    Zikula Support Team
  • markwest

    Nate,

    Two options....

    1) get a better editor.... icon_wink we're getting rid of typetool very soon.
    2) Swith the parser back to the old non XHTML parser

    In pnAPI uncomment line 634 and comment out line 632.

    -Mark

    I show the following code for those lines (surrounding code included). Which lines are to be commented and uncommented? It's not clear to me. Forgive me, but I don't see any existing comments in this code segment.

    static $allowedtags = NULL;

    if (!isset($allowedtags)) {
    $allowedhtml = array();
    foreach(pnConfigGetVar('AllowableHTML') as $k=>$v) {
    if ($k == '!--') {
    if ($v <> 0) {
    $allowedhtml[] = "$k.*?--";
    }
    } else {
    switch($v) {
    case 0:
    break;
    case 1:
    $allowedhtml[] = "/?$k\s*/?";
    break;
    case 2:
    // intelligent regex to deal with > in parameters, bug #1782
    // credits to jln
    $allowedhtml[] = "/?\s*$k" . "(\s+[\w:]+\s*=\s*(\"[^\"]*\"|'[^']*'))*" . '\s*/?';
    // original version
    // $allowedhtml[] = "/?$k(\s+[^>]*)?/?";
    break;



    edited by: geraldgrogan, Jun 02, 2007 - 06:36 AM
This list is based on the users active over the last 60 minutes.