Thorsten Scherler a écrit :
El vie, 20-01-2006 a las 10:44 +0100, Cyriaque Dupoirieux escribió:
Thorsten Scherler a écrit :
El vie, 20-01-2006 a las 07:10 +0800, Gav.... escribió:
----- Original Message -----
From: "Thorsten Scherler"
| El jue, 19-01-2006 a las 22:16 +0800, Gav.... escribió:
| > I thought I would try following the new dispatcher quickstart and other
docs
| > on v3.
| >
| > I get v3 to work no problem, enable pelt.fv in forrest.properties, works
| > fine.
| >
I just tried and for me the design is weird. The searchbox on the left
hand is not staying in the div. The nav-main contract is next to the
group logo. Besides I get in the console:
01:56:56.200 EVENT Started [EMAIL PROTECTED]
[Fatal Error] :3:5: Content is not allowed in prolog.
Yes, I have the same last error, but I don't know where it comes from...
Ok, I did a quick test. If you change the theme to common then the error
is gone. Meaning that a contract in pelt.fv is causing this.
If I had time right now I would comment all contracts and uncomment them
one by one. Then I would have found the offending contract and could do
further investigation limited to this contract.
I will have a look tonight earliest, meanwhile if somebody finds this
contract, please start a new thread "Contract xyz.ft is causing [Fatal
Error] :3:5: Content is not allowed in prolog" and I can have a quick
look. ;-)
Actually the prolog part gives me the guess that some contract is
providing something like
<?xml version="1.0" encoding="UTF-8"?>
content in prolog
...
Ok, but what is the content in prolog ?
Fore the searchbox and the nav-main content next to the logo, try to
deploy the structurer to take into account the new java version
(correction of the div with the same name)
I actually did, but did not build clean forrest before.
Thanks. It is working fine now.
Cool,
Salutations,
Cyriaque,
Thx Cyriaque, btw did we finished the migration from v2 to v3?
For pelt we need to migrate the branding-theme-profiler.ft.
(But I am still thinking to drawn nearer the csszengarden xhtml style
which is much more consistent and let devs easily customise with css help.
So I don't know if we should migrate the contract now or redesign the
xhtml output - of every contracts :-[ )
(Maybe I am going to start a new theme for this with a design documentation)
For common, we still miss some contracts (I think between 5 and 10...)
Salutations,
Cyriaque,
salu2
