<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I'm suffering from this same problem. V2.2.8, NPL templates.<br>
<br>
Rob Weir wrote:
<blockquote cite="mid46338007.9000205@alum.drexel.edu" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
I tried the suggested patch and still have the same problem. In V2.2.8,
when adding a new member, if I leave the joining and expiry date fields
blank, I don't get any dates.<br>
<br>
If I swap date.pm back to the 2.2.7 version that uses DateManip, I get
the expected behavior of today's date for the dateenrolled field and a
auto-calculated date a year later for the expiry field.<br>
<br>
Will I break anything else if I just run with the 2.2.7 date.pm for
now? Or can anyone suggest a fix for the new version? I tried to find
the block of code that is processing these two dates, and could not. I
have v5.4 of Date-Calc and v5.44 of DateManip installed.<br>
</blockquote>
Can anyone out there suggest whether it is OK to use the old version of
date.pm?<br>
<br>
Kevin<br>
<pre class="moz-signature" cols="72">--
Kevin O'Rourke
ICT Coordinator, National Teachers' Institute, Kaduna, Nigeria
062 316972</pre>
</body>
</html>