Re: Re: Re: Re: LibXML 'Fun'

ah. now, thats a thought. i was assuming that it did indeed change the xml file loaded into $tree. I will go and play around with that, thank you for the pointer and thought :)

Also, a small note, i have the header in the XML file as is. i take it that this is 'frowned upon' ?

Comment on Re: Re: Re: Re: LibXML 'Fun'

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: LibXML 'Fun' by dws (Chancellor) on Oct 12, 2003 at 03:31 UTC
Also, a small note, i have the header in the XML file as is. i take it that this is 'frowned upon' ? Not at all. The lack of a content-type header is a likely culprit for the symptoms you reported, so I asked. Putting the content-type header (and any other necessary headers) in the template gives a more cohesive solution than putting the content-type into code and the content into a separate template. On the other hand, emitting a content-header early, from code, makes a number of problems easier to diagnose.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: Re: LibXML 'Fun'
by dws (Chancellor) on Oct 12, 2003 at 03:31 UTC

Also, a small note, i have the header in the XML file as is. i take it that this is 'frowned upon' ?

Not at all. The lack of a content-type header is a likely culprit for the symptoms you reported, so I asked. Putting the content-type header (and any other necessary headers) in the template gives a more cohesive solution than putting the content-type into code and the content into a separate template. On the other hand, emitting a content-header early, from code, makes a number of problems easier to diagnose.

[reply]