Zikula Community

• MACscr
  
  

  • Rank: Expert
  • Registered: Dec 31, 1969
  • Last visit: Oct 21, 2009
  • Posts: 1437

  Posted: May 24, 2005 - 04:12 AM

  Is there anyway to get NW to validate? All im looking for is HTML 4.01 Transitional.

  • 
  •  
• **unknown user**
  
  

  • Rank: Helper
  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 676

  Posted: May 26, 2005 - 02:32 AM

  NW just wraps your supplied pages in PostNuke. PostNuke itself currently doesn't validate, that is being worked on by the PN developers. It's up to users to make their wrapped pages valid.
  However, on one point it wouldn't validate; NW doesn't strip the HEAD of the included page, since it may contain Javascript or CSS links, or JS and CSS code. Making a generic solution where it injects the entire content of the included page's Head into PN's Head would probably break things in unpredicted ways, so I haven't done it, and since browsers handle it fine, haven't thought it a problem. But it could be done. Currently with the supplied modified header.php file for 'old' themes, or modified Templates for Xanthia, it strips the Metadata of the included page and puts it in PostNuke. If there's a demand, I could look into it when I have time.
  
  PN 0.76 will produce much better code (at least for templated core modules, older modules probably won't), moving towards PN 0.8.

  • 
  •  
• MACscr
  
  

  • Rank: Expert
  • Registered: Dec 31, 1969
  • Last visit: Oct 21, 2009
  • Posts: 1437

  Posted: May 26, 2005 - 02:46 AM

  The validation was was with the frame code itself. So it was specific to the nukewrapper module. I forget what the warnings were as im not using it now. But i know one of the things had something to do with a ilayer or something like that.

  • 
  •  
• **unknown user**
  
  

  • Rank: Helper
  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 676

  Posted: May 26, 2005 - 02:59 AM

  Oh right, I left the iLayer in there. Completely redundant now. It was Netscape's proposal for Layers, it wasn't accepted by the W3C, and IE's iFrames became the defacto standard. Netscape6/Mozilla dropped it. It serves no useful purpose anymore, it was an old cross-browser convention to include both. Easily removed.
  Also I left out the src attribute deliberately. I could change it slightly, which hopefully will fix that.
  Actually I'mnot sure what their position is in iFrames, I understand the W3C don't like them much, don't think they're in the XHTML spec, but they're too damn useful to get rid of. One of the issues is that content in Frames isn't Accessible to screenreaders for the blind.
  One of the reason I wrote NukeWrapper was to get away from iframes used in all other implementations like PostWrap. But I put them in later as people still wanted to access external sites, for which a frame is necessary.

  • 
  •  
• MACscr
  
  

  • Rank: Expert
  • Registered: Dec 31, 1969
  • Last visit: Oct 21, 2009
  • Posts: 1437

  Posted: May 26, 2005 - 03:09 AM

  Ok, i will look into that. Thanks.
  
  Also, quick question about targeting the frame. Lets say i have a regular menu on my PN site. Whats the best way to reference the frame without reloading the page? I have a client that for some reason wants frames for a particular module. Its the UpDownload moduel to be exact. Anyway, i made a block that lists all the download categories and would like to be able to reference the nukewrapper frame without it actually reloading. Also, is there a better way to do it besides page.php?URL=http://domain.com/index.php?module=UpDownload, etc? I tried setting a URL key to shorten that up a little to page.php?DocManager??module=UpDownload, but then the permissions for the module are messed up.
  
  Sry to mix posts, just thought i woudl ask real quick.

  • 
  •  
• **unknown user**
  
  

  • Rank: Helper
  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 676

  Posted: May 26, 2005 - 03:11 AM

  If you seaarch for ilayer or iframe in the script, you can try replacing the code yourself if you're up for it:
  

  Code

  <noscript><div align="center"><strong>Please enable Javascript to see the page.</strong></div></noscript>
    <iframe id="ContentFrame" name="ContentFrame" scrolling="auto" frameborder="no"
          <?php echo ((!empty($Request['url2']) or !$AutoResize or !$ExternalUrl) ? "src=\"$URLwrap\" " : 'src="" ')  ?>
      onLoad="window.setTimeout('iFrameHeight(this)',50);"
      style="width: 100%; height: <?PHP echo $FrameHeight ?>px;" marginwidth="0" marginheight="0">
    </iframe>

  
  One of the things the validator might also complain about is the use of < b > and < i >instead of the new < strong > and tags. Personally I like B and I, they're pretty straightforward and intuitive.

  • 
  •  
•  
•  

Users on-line

• slam

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