html-template-users — Discussion of HTML::Template and related modules

[htmltmpl] ANNOUNCE: Krang 1.102

[Aaron D. <aa...@da...>]

We're pleased to announce that Krang v1.102 is now available.


Notable changes in this release:

  * Added a new Krang::ElementClass method, mark_form_invalid(). This method may
    be overriden to alter how Krang marks element form fields invalid. The
    default behvior, wrapping the field in a span set to the ``invalid'' class
    remains.

  * Improved support for Mac OSX, both in compilation and documentation.

  * Can now bundle Krang::List data with your element library, and have it
    imported when the database is created (in the same fashion as
    templates.kds). The file is lists.kds.

  * Added slug as a variable available to all templates at publish-time. This
    was intended to be there all along, but somehow fell through the cracks.

  * Added bin/krang_addon_framework - a new script to create a supporting
    framework to simplify development of Krang addons.

  * Added --rebuild option to bin/krang_build allowing it to build modules even
    if there an existing Krang build there already.

  For more information about Krang, visit the Krang website:


  http://krang.sourceforge.net/


There you can download Krang, view screenshots, read documentation,
join our mailing-lists and access the CVS tree.


Detailed change-log here: http://krang.sf.net/docs/changelog.html


Krang is an Open Source web-publisher / content-management system
designed for large-scale magazine-style websites.  It is a 100% Perl
application using Apache/mod_perl and MySQL, as well as numerous CPAN
modules.


Krang provides a powerful and easy to use story and media editing
environment for magazine editors, as well as a complete template
development environment for web designers. On the back-end, Perl
programmers can customize Krang to control the data entered in the
story editor and add code to drive the templates to build
output. Krang can be enhanced with add-ons containing new skins and
other new features.  Krang easily handles large data sets and can
manage multiple websites in a single installation.



  - the Krang team



----
Aaron Dancygier

[htmltmpl] ANNOUNCE: Dada Mail 2.9 Released

[Justin S. <ju...@sk...>]

The Dada Mail Developing Team meaning... me - is please to announce the  
release of Dada Mail, version 2.9.

The Download is at:

	http://mojo.skazat.com/download/
	
As always, Dada Mail is a free download (GPL licensed)

This release of Dada Mail has focused on one idea: Write Once,  
Distribute Everywhere. Messages sent using Dada Mail are also available  
on the web, searchable, resendable, and syndicated. This allows content  
creators to focus on writing their content, while Dada Mail focuses on  
distributing it and  allows your users to choose on how they would like  
to receive it. This is the largest overhaul of Dada Mail to date.  
Here's a fancy walkthru:

	http://mojo.skazat.com/features/2_9/

Improvements are found in the following areas:

     * Syndication
     * Send an archived message to a friend feature - rewritten
     * mail.cgi - rewritten (basically)
     * Browser-based HTML Message Editor
     * List Screens
     * Archive Screens
     * Email Formatting
     * Path Infos
     * VERP support
     * Fast List Switching
     * Batch Notification Enhancements
     * Internal Templates
     * Subscriber Help Screen
     * HTML Screens - XHTML Compatible
     * Log In Security
     * Developer Stuff

An exhaustive look at all the new features can be found at:

	http://mojo.skazat.com/support/documentation/ 
new_features.pod.html#version_2_9

:: Notes:

	http://mojo.skazat.com/support/documentation/NOTES.pod.html#2_9

:: Changes:

	http://mojo.skazat.com/support/documentation/changes.pod.html#2_9_0

:: Known Issues:

	http://mojo.skazat.com/support/documentation/known_issues.pod.html

I announce this release on the HTML::Template list, since Dada Mail now  
incorporates HTML::Template to interpolate almost all of it's HTML  
Screens.

This has had some great affects:

.: The main, albeit monolithic, script has been reduced in size from  
284k to 186k -  almost all of which has been embedded HTML (in every  
possible way imaginable) which has thus been moved out of the program  
and into separate template files.

.: There are about 70 different template files in Dada Mail that are  
now editable to anyone who can pick up the HTML::Template system.

This has allowed the next affect:

.: We were able to update almost all the HTML to be xHTML Transitional!  
The HTML code in Dada Mail dates to 1999, when the program was first  
written, so this is a nice change.

.: I'm hoping that interested 3rd parties will think of translating the  
program to something other than English, now that a great majority of  
the text/layout of the program is in easy to edit template files.

:: About Dada Mail:

Dada Mail is an intuitive, web-based e-mail list management system,  
which runs on any hosting account that can execute custom CGI scripts.  
Dada Mail is also a conceptual art project.

.: More Information  -

	http://mojo.skazat.com/project/

-----------------------------------------------------------------------

Working so much with HTML::Template I've come to appreciate a few  
things about the package and of the philosophy:

.: Templates should have minimal any logic

I didn't understand why this was such a big deal - I actually saw that  
putting a little logic here and there inside the templates was actually  
a good way to shortcut some harder coding in Perl itself.

Wrong I was.

First off, having all the HTML outside of the Perl program itself,  
really gives a lot of room to actually code - everything becomes  
tighter and easier to manage. What once was spaghetti of HTML, CGI.pm  
method calls and logic? now is in easy-to-understand chunks. Many of  
the admin screens of Dada Mail look like this (actual subroutine):



1: sub view_list_options {
2:
3: 	my ($admin_list, $root_login) = check_list_security(-cgi_obj  => $q,
4: 	                                                    -Function =>  
'view_list_options');
5: 	$list = $admin_list;
6:
7: 	my @list_amount = (10,25,50,100,150,200,
8: 	                   250,300,350, 400,450,
9: 	                   500,550,600,650,700,
10: 	                   750,800,850,900,950,1000
11: 	                  );
12: 	
13: 	require DADA::MailingList::Settings;
14: 	
15: 	my $ls = DADA::MailingList::Settings->new(-List => $list);
16: 	my $li = $ls->get;
17: 	
18: 	if(!$process){
19: 	
20: 		
21: 		my $vlsn_menu = $q->popup_menu(-name     =>  
'view_list_subscriber_number',
22: 									   -values   => [ @list_amount],
23: 									   -default  => $li->{view_list_subscriber_number});
24: 											  									
25: 		print(admin_html_header(-Title      => "View List Options",
26: 		                        -List       => $list,
27: 		                        -Root_Login => $root_login,
28: 		                       ));
29: 		
30: 		require DADA::Template::Widgets;
31: 		print   DADA::Template::Widgets::screen(-screen =>  
'view_list_options_screen.tmpl',
32: 												-vars  => {
33: 															done      => $done,
34: 															vlsn_menu => $vlsn_menu
35: 														  },
36: 											   );
37: 											
38: 		print(admin_html_footer(-List => $list));
39: 	
40: 	}else{
41: 	
42: 		$ls->save({view_list_subscriber_number =>  
$q->param('view_list_subscriber_number')});
43: 		print $q->redirect(-uri => $S_PROGRAM_URL .  
'?f=view_list_options&done=1');
44: 		return;
45: 	}
46:
47: }


Before I get started - if this code looks similar to what you'd see in  
a CGI::Application program - you're right, it's what I want to move to  
- anyways:

Line 3 -

check_list_security() is Dada Mail's way to keep state and check that  
the right people are doing the right things. It uses CGI::Session at  
the core. 2 lines and we're done with that.

Line 21 -

I still used the CGI.pm methods for creating popup menus, and I just  
passed it as a variable to HTML::Template - as the docs state, it's a  
good way to do this;

Line 31 -

DADA::Template::Widgets::screen is basically a wrapper around  
HTML::Template - it checks a few things and does some janitorial work.  
One of the things you pass it is the -vars hashref - which is given  
right to HTML::Template. There's many many places that you have to  
explicitly list the vars to be filled in - but I really like having  
this list available to me, in the code. Code as Data, Data as Code and  
all that.

I'll stop there, but the subroutine itself is really simple - if  
something needs to be saved, save it, if not, give me a screen to make  
changes. It's lovely. Other people can understand what's going on and  
it's in Perl :)

Couldn't have done it without you, HTML::Template!

I was thinking of extending the above and write something on Perl  
Monks, like I did for CGI::Application:

	http://perlmonks.org/index.pl?node_id=199411

Starting with the original version of the above subroutine and stating  
how I made it a bit nicer. If I have time :)


Cheers,

Justin Simoni
-- 
// is an artist, living and working in Denver, Colorado
// URL: http://justinsimoni.com
// PHO: 720.436.7701

Re: [htmltmpl] issues using css

[Thomas N. <th...@te...>]

Solved..i did have a faulty path...the path was correct but the 
webservers root path should not be given. The correct path should 
"/test/latest.css" then it works .. and might I add is looking very 
nice


2005-05-06 kl. 09.22 skrev Philip Tellis:

> Thomas Nyman wrote:
>
>> and my template starts with
>> <head>
>>         <title>This page</title>
>>         <style type="text/css" media="screen">@import 
>> "/Library/webserver/documents/test/latest.css";</style>
>>         </head>
>
> Is http://yourhost.com/Library/webserver/documents/test/latest.css the 
> correct location of your CSS file?
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great 
> events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Html-template-users mailing list
> Htm...@li...
> https://lists.sourceforge.net/lists/listinfo/html-template-users

Re: [htmltmpl] ModPerl and HTML::Template?

[Roger B. W. <ro...@fi...>]

On Fri, May 06, 2005 at 02:50:43AM -0600, Justin Simoni wrote:

>I've used HTML::Template to create some PlainText emails, but I always 
>had to fumble with multiple if/unless tags on the same line to do what 
>I want and format acceptably.

Yup. H::T doesn't do anything to the whitespace you give it, so all the
newlines one normally uses to break up code will be propagated into the
output file.

Even with that, it's still better than many of the other options... :-)

Roger

Re: [htmltmpl] ModPerl and HTML::Template?

[Justin S. <ju...@sk...>]

> We even use HTML::Template for dynamic generation of emails to 
> customers.
> It works very well and we make use of the caching facilities.

Slightly off topic, but do you do anything special for PlainText email 
messages? I'm assuming that HTML::Template isn't the largest snob when 
it comes to afflictions of weird whitespace issues, since HTML doesn't 
either.

I've used HTML::Template to create some PlainText emails, but I always 
had to fumble with multiple if/unless tags on the same line to do what 
I want and format acceptably.

I also say this because I develop a program that centers around sending 
email, and it used HTML::Template for almost all of its HTML screens, 
and I'm not really looking forward to taking advantage of another 
system for regular text (I heart H::T)

Cheers,

Justin Simoni
-- 
// is an artist, living and working in Denver, Colorado
// URL: http://justinsimoni.com
// PHO: 720.436.7701

On May 6, 2005, at 2:16 AM, MArk Williams wrote:

> If you visit the UK DTI Government website (www.companieshouse.gov.uk) 
> and use any of thier data services, they are all built with mod_perl 
> and HTML::Template. We even use HTML::Template for dynamic generation 
> of emails to customers.
> It works very well and we make use of the caching facilities.
> MArk Williams
> Senior developer
> Orchid Telematics
>
>
>> joseph canton wrote:
>>  > Has anyone used HTML::Template with modperl or Apache::ASP?
>> I was one of the main developers of http://www.fotoserve.com/ which 
>> uses a combination of mod_perl 1 and HTML::Template. The combination 
>> works like a dream.
>> Mike
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great 
> events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Html-template-users mailing list
> Htm...@li...
> https://lists.sourceforge.net/lists/listinfo/html-template-users
>

Re: [htmltmpl] ModPerl and HTML::Template?

[MArk W. <ma...@or...>]

If you visit the UK DTI Government website (www.companieshouse.gov.uk) 
and use any of thier data services, they are all built with mod_perl 
and HTML::Template. We even use HTML::Template for dynamic generation 
of emails to customers.
It works very well and we make use of the caching facilities.
MArk Williams
Senior developer
Orchid Telematics


> joseph canton wrote:
> 
>  > Has anyone used HTML::Template with modperl or Apache::ASP?
> 
> I was one of the main developers of http://www.fotoserve.com/ which uses 
> a combination of mod_perl 1 and HTML::Template. The combination works 
> like a dream.
> 
> Mike
> 

Re: [htmltmpl] issues using css

[Philip T. <phi...@gm...>]

Thomas Nyman wrote:

> and my template starts with
> 
> <head>
>         <title>This page</title>
>         <style type="text/css" media="screen">@import 
> "/Library/webserver/documents/test/latest.css";</style>
>         </head>

Is http://yourhost.com/Library/webserver/documents/test/latest.css the 
correct location of your CSS file?

[htmltmpl] issues using css

[Thomas N. <th...@te...>]

Hi

I have a perl script that outputs to a tmpl .. so far so fine. When I 
try to manage the layout of the tmpl with css stylesheets it doesnt 
quite work.

the relevant parts of my perl script is

  my $template = HTML::Template->new(filename => 'intro_css.tmpl');
                 $template->param(DAG => $dag);
                 $template->param(DATUM => $datum);
                $template->param(TID => $tid);
                 print "Content-type: text/html\n\n";
	       print $template->output();

and my template starts with

<head>
         <title>This page</title>
         <style type="text/css" media="screen">@import 
"/Library/webserver/documents/test/latest.css";</style>
         </head>

All of this works fine on its own, but not in conjunction with 
html::template.

I guess I'm probably missing something easy. What I am trying to do is 
apply the so called "3 columns, the holy grail" to my templates, see 
http://www.glish.com/css/7.asp

Anyway..I would really appreciate som help/pointers here

Thanks

Re: [htmltmpl] ModPerl and HTML::Template?

[Mike C. <htm...@bl...>]

joseph canton wrote:

 > Has anyone used HTML::Template with modperl or Apache::ASP?

I was one of the main developers of http://www.fotoserve.com/ which uses 
a combination of mod_perl 1 and HTML::Template. The combination works 
like a dream.

Mike

Re: [htmltmpl] ModPerl and HTML::Template?

[David H. <da...@ho...>]

On 4 May 2005, at 21:25, joseph canton wrote:

> Has anyone used HTML::Template with modperl or Apache::ASP?
>
>

Apache::Template - loads the sucker right in and you can use
it PHP-style.

And yes, I'm very, very sorry.

Re: [htmltmpl] ModPerl and HTML::Template?

[Sam T. <sa...@tr...>]

On Wed, 4 May 2005, joseph canton wrote:

> Has anyone used HTML::Template with modperl or Apache::ASP?

Yes!  Krang (http://krang.sf.net) is a large-scale Apache/mod_perl app
which uses HTML::Template.

-sam

Re: [htmltmpl] ModPerl and HTML::Template?

[Timm M. <tm...@ag...>]

At 03:25 PM 5/4/2005, joseph canton wrote:
>Has anyone used HTML::Template with modperl or Apache::ASP?

Yes.  In fact, many of the caching options are only good under an 
environment like mod_perl.


Timm Murray
IT Web Asst.
ASA-CSSA-SSSA
677 S Segoe Rd.
Madison, WI 53711-1086
Phone: 608-268-4944
Fax: 608-273-2021
www.agronomy.org
www.crops.org
www.soils.org

Re: [htmltmpl] ModPerl and HTML::Template?

[Philip T. <phi...@gm...>]

joseph canton wrote:
> Has anyone used HTML::Template with modperl or Apache::ASP?

Bricolage

[htmltmpl] ModPerl and HTML::Template?

[joseph c. <jc...@re...>]

Has anyone used HTML::Template with modperl or Apache::ASP?

Re: [htmltmpl] problem in patching..

[Mathew R. <mat...@re...>]

Hi Amit,

I have just cut-n-pasted your code -> it works perfectly.
Without further information, I'm not sure we can help...

regards,
Mathew

----- Original Message -----=20
From: "Amit Marathe" <am...@gm...>
To: <htm...@li...>
Sent: Thursday, April 28, 2005 8:17 PM
Subject: [htmltmpl] problem in patching..


Hi,=20
I hv installed HTML-Template-2.7, further i tried to use it via my
program it is not working correctly.

I tried to see the e.g. program then it also wont show any o/p in the =
browser.=20
I hv checked, the prog is executable with proper headers
My perl code is as given below....

#!/usr/bin/perl -w
use HTML::Template;
use Data::Dumper;
print "Content-type: text/html \n\n";
# open the html template
my $template =3D HTML::Template->new(filename =3D> 'testTemplate.tmpl');
# fill in some parameters
$template->param(HOME =3D> 'My HOME');
$template->param(PATH =3D> 'My HOME PATH');
#print "Dumper is " . Dumper[$template];
# send the obligatory Content-Type and print the template output
#print "Content-Type: text/html\n\n",
print $template->output;
exit 0;

My template is  'testTemplate.tmpl'  & it is written as follows  :

<html>
<head><title>Test Template</title>
<body>
My Home Directory is <TMPL_VAR NAME=3DHOME>
<p>
My Path is set to <TMPL_VAR NAME=3DPATH>
</body>
</html>

############
 What might be the Error ...........
Can u give me some idea..=20

Thanks & Regards=20
AmitSM.


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Html-template-users mailing list
Htm...@li...
https://lists.sourceforge.net/lists/listinfo/html-template-users

[htmltmpl] problem in patching..

[Amit M. <am...@gm...>]

Hi,=20
I hv installed HTML-Template-2.7, further i tried to use it via my
program it is not working correctly.

I tried to see the e.g. program then it also wont show any o/p in the brows=
er.=20
I hv checked, the prog is executable with proper headers
My perl code is as given below....

#!/usr/bin/perl -w
use HTML::Template;
use Data::Dumper;
print "Content-type: text/html \n\n";
# open the html template
my $template =3D HTML::Template->new(filename =3D> 'testTemplate.tmpl');
# fill in some parameters
$template->param(HOME =3D> 'My HOME');
$template->param(PATH =3D> 'My HOME PATH');
#print "Dumper is " . Dumper[$template];
# send the obligatory Content-Type and print the template output
#print "Content-Type: text/html\n\n",
print $template->output;
exit 0;

My template is  'testTemplate.tmpl'  & it is written as follows  :

<html>
<head><title>Test Template</title>
<body>
My Home Directory is <TMPL_VAR NAME=3DHOME>
<p>
My Path is set to <TMPL_VAR NAME=3DPATH>
</body>
</html>

############
 What might be the Error ...........
Can u give me some idea..=20

Thanks & Regards=20
AmitSM.

RE: [htmltmpl] Generating dynamically named tags

[Dan H. <dan...@re...>]

 > 
> > I'm writing a template for use with 
> > CGI:Application::Plugin::ValidateRM.
> > C::A::P::VRM expects every field that requires validation 
> to have a matching
> > field  with an "err_" prefix (i.e  err_field_name).
> > 
> > My field names are dynamic, e.g.
> > 
> > <tmpl_loop name=application_parameters>
> > <input type="Text" name="<tmpl_var name=field_name>" 
> value="<tmpl_var 
> > name=field_value> </tmpl_loop>
> > 
> > but I can't figure out the best way to specify the error field. 
> > Obviously
> > 
> > <tmpl_var name=err_<tmpl_var name=parameter>>
> > 
> > doesn't work
> > 
> > Any ideas appreciated
> > 
> 
> Generate it in the Perl script instead, in an H::T var named 
> "err_field_name". In the template just place: <tmpl_var 
> name=err_field_name>
> 
> HTH,
> -- 
> Offer Kaye

Thanks for your reply. I'm not clear how it works. If I have a field called
"max_rows", then the parsed template will be

<input type="Text" name="max_rows"> value="5> err_max_rows

What should happen is that <tmpl_var err_max_rows> will be empty when the
template is displayed if there is no error, and will have the error message
if there is an error. This isn't done by me - it's done by
CGI:Application::Plugin::ValidateRM, DFV and HTML::FillInForm.

Thanks

Dan

Re: [htmltmpl] Generating dynamically named tags

[Offer K. <off...@gm...>]

On 4/20/05, Dan Horne wrote:
> Hi All
>=20
> I'm writing a template for use with CGI:Application::Plugin::ValidateRM.
> C::A::P::VRM expects every field that requires validation to have a match=
ing
> field  with an "err_" prefix (i.e  err_field_name).
>=20
> My field names are dynamic, e.g.
>=20
> <tmpl_loop name=3Dapplication_parameters>
> <input type=3D"Text" name=3D"<tmpl_var name=3Dfield_name>" value=3D"<tmpl=
_var
> name=3Dfield_value>
> </tmpl_loop>
>=20
> but I can't figure out the best way to specify the error field. Obviously
>=20
> <tmpl_var name=3Derr_<tmpl_var name=3Dparameter>>
>=20
> doesn't work
>=20
> Any ideas appreciated
>=20

Generate it in the Perl script instead, in an H::T var named
"err_field_name". In the template just place:
<tmpl_var name=3Derr_field_name>

HTH,
--=20
Offer Kaye

[htmltmpl] Generating dynamically named tags

[Dan H. <dan...@re...>]

Hi All

I'm writing a template for use with CGI:Application::Plugin::ValidateRM.
C::A::P::VRM expects every field that requires validation to have a =
matching
field  with an "err_" prefix (i.e  err_field_name).

My field names are dynamic, e.g.

<tmpl_loop name=3Dapplication_parameters>
<input type=3D"Text" name=3D"<tmpl_var name=3Dfield_name>" =
value=3D"<tmpl_var
name=3Dfield_value>
</tmpl_loop>

but I can't figure out the best way to specify the error field. =
Obviously=20

<tmpl_var name=3Derr_<tmpl_var name=3Dparameter>>=20

doesn't work

Any ideas appreciated

Thanks

Dan

Re: [htmltmpl] More flexible looping mechanism?

[Sam T. <sa...@tr...>]

On Wed, 13 Apr 2005, Jonathan Lang wrote:

> How difficult would it be to implement an alternative to the existing
> looping technique, where the values to be looped through are passed to the
> template via a bunch of lists instead of a list of hashes?  

Trivial.  Create a sub-class which uses filter to turn your syntax
into normal loops.  Create a param() which takes "a bunch of lists"
and turns them into a list of hashes.

-sam

[htmltmpl] More flexible looping mechanism?

[Jonathan L. <dat...@ya...>]

How difficult would it be to implement an alternative to the existing
looping technique, where the values to be looped through are passed to the
template via a bunch of lists instead of a list of hashes?  

Jonathan "Dataweaver" Lang


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

[htmltmpl] How to change previous and next buttons text in HTML::Pager without change the .pm

[Aliet S. S. <al...@te...>]

Hi list, I'm testing html-template with html-pager  and everything is 
ok, but the nav buttons displays the text in English and I need to set 
this to my language, I could change the Package, but if already exists a 
way, I would appreciate this, maybe a option in the new method.
Regards

[htmltmpl] ANN: Bricolage 1.8.5 Released

[David W. <da...@ki...>]

     The Bricolage development team is pleased to announce the release of
     Bricolage 1.8.5. This maintenance release addresses a number of 
issues in
     Bricolage 1.8.3 and adds a number of improvements (there was no
     announcement for the short-lived 1.8.4 release). The SOAP server in
     particular sees improvements in this release, with improved 
character set
     support; better support for related stories and media using URIs in
     addition to IDs; and as support for top-level element relations. 
Issues
     with the ordering of story elements have also been corrected, as 
well as
     errors when attempting to revert a story or media document or 
template.
     Here are the other highlights of this release:

  Improvements

       * Added Linux startup script contrib/start_scripts/linux. [David]

       * Related story and media elements managed through the SOAP server
       can now use a combination of URI and site ID to identify related
       assets in addition to the existing approach of using story and 
media
       IDs. [David]

       * A list of subelements is now less likely to mysteriously become 
out
       of order and thus lead to strange action-at-a-distance errors. And
       even if they do become out of order, the error message will be 
more
       appropriate ("Warning! State inconsistent" instead of "Can't call
       method 'get_name' on an undefined value"). Reported by Curtis Poe.
       [David]

       * The SOAP media interface now supports creating relationships
       between the media documents elements and other story and media
       documents, just like the SOAP story interface does. [David]

       * The SOAP interface now supports Related stories and media on 
story
       type and media type elements just as in the UI. This involved the
       somewhat hackish necessity for including the "related_story_id" 
and
       "related_media_id" (or "related_story_uri" and 
"related_media_uri")
       attributes in the "elements" XML element, but it does the trick.
       [David]

  Bug Fixes

       * Calls to publish documents via SOAP will no longer fail if the
       published_version attribute is not specified and the document to 
be
       published has never been published before. [David]

       * The Bricolage virtual FTP server will no longer fail to start if
       Template Toolkit is installed but its version number is less than
       2.14. Reported by Adam Rinehart. [David]

       * Stories and Media created or updated via the SOAP interface will
       now associate contributors of the appropriate type, instead of 
"All
       Contributors". [Scott & David]

       * Deleting an element that has a template no longer causes an 
error.
       Thanks to Susan for the spot! [David]

       * Eliminated encoding errors when using the SOAP interface to 
output
       stories, media, or templates with wide characters. Reported by 
Scott
       Lanning. [David]

       * Reverting (stories, media, templates) no longer gives an error.
       Reported by Simon Wilcox, Rachel Murray, and others. [David]

       * Publishing a published version of a document that has a later
       version in workflow will no longer cause that later version to be
       mysteriously removed from workflow. This could be caused by 
passing a
       document looked up using the published_version to list() to
       $burner->publish_another in a template. [David]

       * The SOAP server story and media interfaces now support elements
       that contain both related stories and media, rather than one or 
the
       other. [David]

       * Attempting to preview a story or media document currently 
checked
       out to another user no longer causes an error. Reported by Paul
       Orrock. [David]

       * Custom fields with default values now have their values included
       when they are added to stories and media. Thanks to Clare 
Parkinson
       for the spot! [David]

       * The bric_queued script now requires a username and password and
       will authenticate the user. This user will then be used for 
logging
       events. All events logged when a job is run via the UI are now 
also
       logged by bric_queued. [Mark and David]

       * Preview redirections now use the protocol setting of the preview
       output channel if it's available, and falls back on using 
"http://"
       when it's not, instead of using the hard-coded "http://". Thanks 
to
       Martin Bacovsky for the spot! [David]

       * The has_keyword() method in the Business class (from which the
       story and media classes inherit) now works. Thanks to Clare 
Parkinson
       for the spot! [David]

       * Clicking a link in the left-side navigation after the session 
has
       expired now causes the whole window to show the login form, rather
       than it showing inside the nav frame, which was useless. 
[Marshall]

       * The JavaScript that validates form contents once again works 
with
       htmlArea, provided htmlArea itself is patched. See
       
http://sourceforge.net/tracker/index.php?func=detail&aid=1155712&grou
       p_id=69750&atid=525656 for the htmlArea patch. As of this writing,
       you must run the version of htmlArea in CVS. [David & Marshall]

       * The JavaScript that handles the double list manager has been 
vastly
       optimized. It should now be able to better handle large lists, 
such
       as a list of thousands of categories. Reported by Scott. 
[Marshall]

       * Uploading a new image to a media document with a different media
       type than the previous image no longer causes an Imager error.
       [David]

     For a complete list of the changes, see the changes list at
     http://www.bricolage.cc/news/announce/changes/bricolage-1.8.5/. For 
the
     complete history of ongoing changes in Bricolage, see Bric::Changes 
at
     http://www.bricolage.cc/docs/api/current/Bric::Changes.

     Download Bricolage 1.8.5 now from the Bricolage Website at
     http://www.bricolage.cc/downloads/, from the SourceForge download 
page
     at http://sourceforge.net/project/showfiles.php?group_id=34789, and
     from the Kineticode download page at
     http://www.kineticode.com/bricolage/downloads/

ABOUT BRICOLAGE

     Bricolage is a full-featured, enterprise-class content management 
and
     publishing system. It offers a browser-based interface for ease-of 
use,
     a full-fledged templating system with complete HTML::Mason,
     HTML::Template, and Template Toolkit support for flexibility, and 
many
     other features. It operates in an Apache/mod_perl environment and 
uses
     the PostgreSQL RDBMS for its repository. A comprehensive,
     actively-developed open source CMS, Bricolage has been hailed as 
"quite
     possibly the most capable enterprise-class open-source application
     available" by eWEEK.

     Enjoy!

     --The Bricolage Team

AW: [htmltmpl] Problems with HTML::TEMPLATE

[<Seb...@3S...>]

Strict XHTML

> > I had to specifically mention CHECKED=3D"CHECKED" in the if=20
> statement to make
> > it work.
> > Simply by saying CHECKED alone (though a valid html=20
> attribute) does not seem
> > to work.


XHTML requires that you don't use empty attributes (They call
it "attribute minimization". If you don't like this you have
to use HTML 4.01 in the header of your document):
http://www.w3.org/TR/xhtml1/#h-4.5

And it requires lower-case HTML tags also ;-)
http://www.w3.org/TR/xhtml1/#h-4.2

As a funny sidenote: The W3C found it neccessary to mention in
their compatibility guildline, to state that some browsers have
problems with boolean attributes:
http://www.w3.org/TR/xhtml1/#C_10

I'd suggest checking your HTML with their free checker:
http://validator.w3.org/

Or if you want to do it the Perl-Way (e.g. in automated test
scripts):
http://search.cpan.org/~petdance/HTML-Tidy-1.04/lib/HTML/Tidy.pm

This might save you lots of trouble. On the other hand it's
always a good idea to compare how different browsers behave.

Regards,
Sebastian

Re: [htmltmpl] Problems with HTML::TEMPLATE

[Clifton R. <cli...@ti...>]

On Wed, Mar 16, 2005 at 07:15:08PM -0800, Rama Srinivas wrote:
> Hello all,
> 
> Thanks for the feed back.
> 
> I had to specifically mention CHECKED="CHECKED" in the if statement to make
> it work.
> Simply by saying CHECKED alone (though a valid html attribute) does not seem
> to work.

  That's actually not a function of HTML::Template, it's a function of
the browser.  I seem to recall I noticed something like this with IE,
whereas Mozilla worked better, but I could have it backwards.

> Basically to be more clear I tried doing this first
> <input type="radio" name="beepStatus" value="yes" <tmpl_if
> yesBeeps>cheecked</tmpl_if>  it did not work.
> 
> but by doing this it worked
> 
> <input type="radio" name="beepStatus" value="yes" <tmpl_if
> yesBeeps>cheecked="checked"</tmpl_if>  worked out well.
> 
> I am guessing the html template engine must be looking for some name-value
> pairs and just by seeing a single value with out a matching name would have
> rejected interpreting it.

  Just for future reference, H::T doesn't snoop the values that way. 
For all it cares, it could say "Pastrami!"

  -- Clifton

-- 
          Clifton Royston  --  cli...@ti... 
         Tiki Technologies Lead Programmer/Software Architect
"I'm gonna tell my son to grow up pretty as the grass is green
And whip-smart as the English Channel's wide..."
                                                   -- 'Whip-Smart', Liz Phair