[eluser]broofa[/eluser]
Thanks for the quick reply, Phil.
[quote author="OverZealous" date="1277451111"]
Well, I don't have any control over what stensi does with his domain. I don't understand why you would assume that... And DataMapper isn't deprecated. It's just not upgraded any more.[/quote]
'Wasn't assuming you had control over stensi.com. Rather, it's pretty clear you're carrying the baton on this codebase now. So sending an email to stensi.com asking that he point people to the DMZ site would seem an obvious thing to do (especially since you don't show up in the first page of google results for "php datamapper" and stensi.com does). I'm happy to do that if you'd like, but it would make more sense if that came from you.
Quote:As for your configuration problems, I'm sorry but the very first item in the upgrade process tells you to update your datamapper config. And the config page explicitly lists the items that are new to DMZ.
By documenting "default" values for these parameters you set up the expectation that they aren't required. (That's what "default" means). So either the code should change to provide default values when none are found in the config file, or docs should describe these as required properties with "suggested" values.
Quote:As for your other errors, you probably need to spend some time reading the manual. Setting db_params to FALSE is not recommended, and just not necessary since 1.7.
While it's entirely possible my problems are specific to my application, this isn't a problem of me not having read the manual. 'Read it several times. And I'm now at the point where I'm stepping through DMZ and CI code trying to understand what I might be doing wrong. Unfortunately with the default config settings, I'm seeing errors. That's the *only* reason I'm using the FALSE value for db_params, and also the only reason I have lang_file_format=''. If you have better suggestions for how to avoid (or understand what might be causing) these errors, I would love to hear them. (e.g. is it possible there's something different in CI 1.7.2 that might be causing these?)
