On Wed, Nov 17, 2010 at 10:27 AM, Peter Lind wrote:
> Quick note, in case anyone has similar problems: make sure that the
> data you feed into DOMDocument is UTF8 encoded
>
I can attest to this as well. I just fixed a bug in our sitemap-building
code that was producing some items with empty titl
On 16 November 2010 21:30, Adam Richardson wrote:
> Hmmm...
>
> Nothing really stands out to me, but as my wife would attest, I'm often less
> than observant.
>
> I would probably try sifting through fixes/upgrades in the change logs for
> possible conflicts and/or changes in behavior. Nothing ju
Hmmm...
Nothing really stands out to me, but as my wife would attest, I'm often less
than observant.
I would probably try sifting through fixes/upgrades in the change logs for
possible conflicts and/or changes in behavior. Nothing jumped out at me
after a quick glance.
Sorry,
Adam
On Tue, Nov
I'm currently trying to parse a document with DOMDocument, and I'm
having some serious problems. I created a script that runs fine on php
5.2.9, ripping out content using DOMNode::nodeValue. The same script
fails to get any content on php 5.3.3 - even though it correctly
navigates to the proper nod
4 matches
Mail list logo