Support Spidean |
Do you like our FREE downloads? How about the FREE support for the FREE downloads? Please help us out and donate any amount! It's fast and easy through PayPal.
|
Board Index > NukeWrap > Push the Envelope in the Next Version
keyrocks
Newbie   Posts: 1 Registered: 3/14/2006 Status: Offline
|
 posted on 3/15/2006 at 04:03 PM |
I've been nuking about a year now and quite comfortable with php, etc. so
not really a newbie. Downloaded NukeWrap a couple days ago and found the
installation/use instructions very difficult to follow. However, after an
hour of browsing this forum, and a little experimentation, I figured out
how to make links work in the iframe. After a couple of hours - I must say
I was impressed with this module's functionality. But - a day and a half
later - my project seems like a deep well with no bottom.
My site is php-nuke v7.7 cross-bred with a few inclusions from 7.9. I'm
running about 50+ modules, most of which are scratch-built for specific
uses. I'm running two themes at present, one lightly modified stock Nuke
theme and and the other (my default) using css to the max with no tables
anywhere.
My objective - with NukeWrap - was to have all modules displayed in the
iframe. My default css-based theme is heavy on the graphics and has slowed
page loading time for users, especially those still stuck on dial-up
connections. I thought NukeWrap would speed page loading up again, by only
having to load the theme template once in a session. I managed to create a
set of links to work with the nav systems in both themes after getting all
modules (and a few external sites) listed in NukeWrap.
Problem One - the old "Nuke-in-Nuke" effect, when the theme template -
header, blocks and footer are replicated within the iframe. Of course this
happens because the include header and include footer lines are active in
every module function as well as in NukeWrap. A little surgery... disabling
themeheader(); in header.php's head function, and inserting it in
NukeWrap's index.php just under the include("header.php"); string solved
that nicely for me.
Problem Two - When I used my old nav-bar links to log-out or log-in, I
found the auto-refresh links in the Your_Account module (I'm using the
rather large Approve_Membership 6.0 mod) refreshed to pages with no iframe
panel and no header/blocks/footer. But If I use the links for these from
the NukeWrap block - they work fine. So I set about exploring the use of
$variables to replace all the function links in the Approve_Membership
module, the idea being to make it easier to change all the links at the top
of the file and have them apply globally throughout each file. This works
OK but... when I realised I have to do this with all 50-some modules - way
too much work.
NukeWrap is a great little script as it is, for a module or two. My
recommendation for the next version is to concentrate on integrating it
into the core operation of Nuke so that the whole theme template (header,
blocks and footer) are loaded once during a session and ALL portal content
goes into the content iframe by default, perhaps by integrating the iframe
within a theme's theme.php file. Again... right in the theme.php file...
right in between the themeheader and themefooter functions. I wish I had
the time to explore this more myself, but no time.
Again - great script - looking for quick, clean, total php-Nuke integration
with the theme template loading only once. Will keep an eye on this Forum
for good news.
[Edited on 15/3/2006 by keyrocks]
|
| |
| |
|
|
|
|
