[Crimp-users] BUGS - crimp-2006-02-02

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Well its not even been launched more than 24 hours and already I have
noticed a few minor bugs.

The main area of bugs lie within the way CRIMP works with CSS, currently 2
modules have been fixed:

ContentDirectory and BreadCrumbs.

When pages are reassembled either with or without the use of a template, th=
e
pages must follow the following rules:

<body>
<div id=3D'usersChoice'>
 ________________________________
|  ____<!--PAGE_CONTENT-->_____
| |                            |
| |   id=3DcrimpModuleName2      |  This is the 3rd Module called
| | eg crimpMenuContent        |
| |____________________________|
|  ____________________________
| |                            |
| |   id=3DcrimpModuleName1      |  This is the 2nd Module called
 | | eg crimpBreadCrumbs        |
| |____________________________|
|  ____________________________
| |                            |
| |   id=3DcrimpPageContent      |  This is the 1st Module called
| | from any first run module  |
| |____________________________|
|________________________________
</div>
</body>

This means that before ContentDirectory finishes, the div tags NEED to be
inserted
BEFORE any other tags take advantage of the pages body tags.

Main Content Modules are now required to do this.
MenuContent Modules are ok as the div tags are automatic
other modules that add to existing content 'should' already supply their ow=
n
tags,
eg crimpBreadCrumbs and crimpRandomContent.

The above changes allow EVERY section of the document to be moved however
the user
chooses instead of the current method of the entire page being within
<div id=3D'usersChoice'><!--PAGE_CONTENT--></div>

the 2nd error is with VirtualRedirect, when a page is grabbed, only the
title of
the page and everything inside the body tags should be used and put into
$crimp->{DisplayHtml} using the format of $crimp->{DefaultHtml}.

This will fix sites that cause errors due to <body foo=3D'bar'> and as abov=
e,
the div
tag of crimpPageContent should be used for the retrieved content.
(view crimp-2006-02-02 current [/google] source for the problem)

Roll on our 2nd release :)

Deadpan110