-
I'd like to see the ability to export to the ADOdb xmlschema format. This format is useful when working in an agile development environment as you can literally write any DB changes in xmlschema format and each contributer can then upgrade their own DB structure with a simple PHP importer script. The format is XML with a domain specific schema. See the docs at...
2008-02-04 00:57:54 UTC in phpMyAdmin
-
I just found out the hard way that AutoExecute isn't supported yet. Any idea when the Query module supporting this will be released?.
2007-11-26 01:58:21 UTC in ADOdb Lite
-
~~Also, a detailed report at the end would be nice, such as total number of
files processed, the number that succeeded in having templates applied and
the number that failed.~~
Strike that last part. I was only reading stderr, but the summary info was available in stdout.
2007-05-22 19:50:54 UTC in ShearerSite: Web Administration
-
How 'bout an upgrade, eh?.
2007-05-21 21:59:53 UTC in ShearerSite: Web Administration
-
When applying templates to a very large set of files, the output is often not detailed enough to find the exact files on which templating failed (because of validation errors, for example).
As an example, consider the following output:
----------
[36] => 20% done. Current file: 100043.html
[37] => The file will not be processed, because it contained 8 errors:
[38] => *...
2007-05-21 21:58:36 UTC in ShearerSite: Web Administration
-
Hey Drew, it's Chris.
It appears that the HTML parser is only validating the target file, but not the template. If a template file is not valid HTML then further attempts to apply templates fail.
Solution: validate the template file as strictly as you validate target files. If template does not pass validation, fail with relevant error message before applying any templates.
I've tested...
2007-05-21 21:52:14 UTC in ShearerSite: Web Administration
-
I think you misunderstood my note. Though I did submit another ticket (#144247) for the truncated UNTIL value, this ticket details a separate problem in that the INTERVAL value is always set to 1 no matter what the original recurrence value was. If I created an event that occurred three times, then I would expect the INTERVAL value to be 3. However, when publishing through RC it is always output...
2007-04-12 14:55:34 UTC in Remote Calendars
-
I think you misunderstood my note. Though I did submit another ticket (#144247) for the truncated UNTIL value, this ticket details a separate problem in that the INTERVAL value is always set to 1 no matter what the original recurrence value was. If I created an event that occurred three times, then I would expect the INTERVAL value to be 3. However, when publishing through RC it is always output...
2007-04-12 14:55:04 UTC in Remote Calendars
-
Thanks.
2007-04-12 14:51:32 UTC in Remote Calendars
-
Yes, by exporting I meant publishing. The last digit is truncated in the Until value.
2007-04-12 03:48:26 UTC in Remote Calendars
