>> Hmm, I doubt so. But my hope is to find the source of the problem,
PH> ask?
That whole hosting thing has become some kinda political beyond my
recommendations. Really difficult. So I have to stick with what's
given on the server side. You won't believe how happy I was when I
heard that I was *allowed* to port the DB...
>> No your missing nothing. It's absolutely correct. Those values are
>> just filled into corresponding formfields for start and end day,
>> month, year.
PH> do you have an example?
Sure (if nobody minds):
---------- [snip] ----------
<cfscript>
request.dDatum1 = now();
request.sDatum1Tag = DateFormat(request.dDatum1, 'dd');
request.sDatum1Monat = DateFormat(request.dDatum1, 'mm');
request.sDatum1Jahr = DateFormat(request.dDatum1, 'yy');
request.dDatum2 = DateAdd('yyyy', 1, request.dDatum1);
request.sDatum2Tag = DateFormat(request.dDatum2, 'dd');
request.sDatum2Monat = DateFormat(request.dDatum2, 'mm');
request.sDatum2Jahr = DateFormat(request.dDatum2, 'yy');
</cfscript>
<cfoutput>
<div id="bereich_veranstaltungssuche">
<form id="veranstaltungssuche" method="post"
action="#request.sDirDepth##request.sCurrentWebNr##request.sCurrentWebLang#/events/suche.cfm">
<fieldset>
<legend>Veranstaltungssuche</legend>
<div class="frmZeile">
<label class="beschriftung">von</label>
<input type="text" name="sDatum1Tag" value="#request.sDatum1Tag#"
size="2" class="frmText" />
<input type="text" name="sDatum1Monat" value="#request.sDatum1Monat#"
size="2" class="frmText" />
<input type="text" name="sDatum1Jahr" value="#request.sDatum1Jahr#"
size="2" class="frmText" />
</div>
<div class="frmZeile">
<label>bis</label>
<input type="text" name="sDatum2Tag" value="#request.sDatum2Tag#"
size="2" class="frmText" />
<input type="text" name="sDatum2Monat" value="#request.sDatum2Monat#"
size="2" class="frmText" />
<input type="text" name="sDatum2Jahr" value="#request.sDatum2Jahr#"
size="2" class="frmText" />
</div>
<div class="frmZeile">
<input type="text" name="sSuchbegriff" value="Stichwort" size="10"
class="frmTextLang" />
<input type="submit" name="submit" value="suchen" class="frmButton" />
</div>
</fieldset>
</form>
</div>
</cfoutput>
---------- [snip] ----------
That little bit of code gets included in every page.
After that I cfoutput text fields from the MySQL4-datasource
(connected through the MySQL-Connector/J JDBC3-driver) almost
identically (other fieldnames) to the following:
---------- [snip] ----------
<cfquery name="qToday" datasource="#application.sDSN#">
SELECT *
FROM dates
WHERE adate >= CreateODBCDate(now())
AND sdate <= CreateODBCDate(now())
ORDER BY sdate, adate
</cfquery>
<cfoutput query="qToday">
<h2>#qToday.title#</h2>
<p>#qToday.shorttext#</p>
</cfoutput>
---------- [snip] ----------
And those title and shorttext contents get screwed as long as I use
the upper DateFormat. Setting the date vars manually (for testing)
everything works fine (or - as discovered - using LSDateFormat()
without setting a setLocale() in App.cfm).
>> I would imagine that the use of cfprocessingdirective is only useful
>> when you want to force the processing encoding on one special page. Or
>> does one have to use it always when not using utf-8?
PH> it's good practice to include it especially in your case where you're not
using
PH> the default encoding.
Well, that's something I'll look in again...
Patric
--
Patric Stumpe
mailto:[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:231570
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
