| Commit | Date | |
|---|---|---|
|
[r5264]
by
cwilper
minor bugfix (bug was introduced post-2.1.1): |
2006-12-01 07:15:52 | Tree |
| 2006-12-01 07:07:35 | Tree | |
| 2006-12-01 06:06:44 | Tree | |
|
[r5261]
by
cwilper
more log cleanup: |
2006-12-01 05:57:11 | Tree |
| 2006-11-30 17:46:43 | Tree | |
| 2006-11-30 17:45:01 | Tree | |
| 2006-11-30 17:32:41 | Tree | |
|
[r5257]
by
cwilper
replaceInto now uses prepared statements. |
2006-11-30 17:21:35 | Tree |
|
[r5256]
by
rlw
These userdocs are html files that were created with MSWord. Apparently the default encoding for Word is to use Windows-1252 when saving html files. When these files are placed on the webserver, the default encoding for apache is utf-8 so browsers will set the encoding as utf-8 although the underlying document encoding is actually Windows-1252. This encoding mismatch causes viewing problems based on the encoding setting of the browser. The fix was to resave these files from Word using a utf-8 encoding. Most of these docs will require revising for 2.2, so just remember if editing these particular docs with Word or FrontPage to be sure that the encoding is set to utf-8; otherwise they will revert back to Windows-1252 encoding when saved. I also updated the versions of these files on the web site so so docs for 2.1.1 should display properly now as well.... |
2006-11-30 16:20:32 | Tree |
|
[r5255]
by
wdn5e
check for object existence to avoid npe. see chris' mail "ReadOnlyContext Error on HTTP" 11/30/06 |
2006-11-30 14:27:30 | Tree |