Martin Gottlieb writes:
Hi!
>>> PHP Fatal error: Call to undefined function mgd_get_host() ...
>>>
>>
>> All legacy functions are deprecated since 1.8 at least IIRC.
>>
> Thanks. I was afraid that was the case.
>
> Are there equivalent calls in the new API? If it ends up being only a
> few calls that I need, it might be
> worth writing a wrapper that maps them into the new API.
function mgd_get_host($id)
{
$host = null;
try
{
$host = new midgard_host($id);
}
catch (midgard_error_exception $e) {
}
return $host;
}
You can provide similar for page, style , etc.
> Also, without Aegir or Spider, is midcom the recommended (only) admin
> tool for managing midgard sites in 8.09 ?
Yep, MidCOM is the only one recommended.
> I attempted to get that working also but am getting 404s when trying to
> access "/midcom-login-". There is no host
> record with a prefix set to "/midcom-login-". Should there be or is
> this handled a different way ?
You can try datagard.
`datagard -c myconfig -a vhost`
Do not forget to edit/create 'myconfig' file.
http://www.midgard-project.org/documentation/unified-configuration/
> I attempted this and got loads of errors on the "make " step.
Make sure you have all devel package installed. At least: glib-devel ,
php-devel.
> This
> combined with the fact that it will not
> be supported leads me to the questions I asked above about mapping the
> old API calls into the new.
> It's either that or drop back to 1.8.9.
No one recommends going back to 1.8.
I would do things like this:
1. Build midgard-php with legacy API.
Bother us in case of any problems.
2. Keep exisiting sites.
3. Start transition to new API.
Piotras
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
