Still no luck. When I put an absolute path, I still get the error:
Array ( [type] => phrets [code] => -1 [text] => Cookie file "/app/
webroot/xml/mris/v1.0rc1/phrets_cookies.txt" cannot be written to.
Must be an absolute path and must be writable ) GetMetadataTypes()
called but unable to find GetMetadata location. Failed login?
And I CHMOD 777 the entire directory, so it should be writable.
If I omit the SetParam line, I get the error:
Warning: tempnam() [function.tempnam]: open_basedir restriction in
effect. File() is not within the allowed path(s): (/home/admin/:/tmp:/
usr/local/lib/php/) in /home/admin/domains/
domain.com/public_html/app/
webroot/xml/RETS/phrets_v1.0rc1.php on line 1250
Array ( [type] => phrets [code] => -1 [text] => Cookie file "" cannot
be written to. Must be an absolute path and must be writable )
GetMetadataTypes() called but unable to find GetMetadata location.
Failed login?
Any advice?
Thanks
On Nov 4, 1:05 pm, Troy Davisson <
troy.davis...@gmail.com> wrote:
> This did change, sort of. You shouldn't need to declare the SetParam for
> the cookie_file now. If you do, I suggest making the file path you give
> that an absolute path. For example:
>
> $rets->SetParam("cookie_file", "/home/username/phrets/phrets_cookies.txt");
>
> By not including that SetParam line now, PHRETS will attempt to use the
> system's temporary directory and create it's own file there. If it can't do
> that, it's usually been due to PHP not knowing where the system's temporary
> folder is but I haven't run into this enough to say for sure.
>
> PHRETS will attempt to create the file it needs to manage the session cookie
> but if there are folder permission issues keeping that from happening,
> PHRETS will complain.
>