|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #68454 ID already defined errors after update to anything after 1.1.26
Submitted: 2014-11-19 17:43 UTC Modified: -
Avg. Score:4.2 ± 1.0
Reproduced:4 of 4 (100.0%)
Same Version:2 (50.0%)
Same OS:1 (25.0%)
From: x9sim9 at hotmail dot com Assigned:
Status: Open Package: XSLT related
PHP Version: 5.4.35 OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
11 - 11 = ?
Subscribe to this entry?

 [2014-11-19 17:43 UTC] x9sim9 at hotmail dot com
This issue has already been well documented on stack exchange so I thought it made sense to add the link here instead:

The issue seems to have been created by fixing an existing bug and that the XHTML is now being treated as XML whereas older versions were treated as HTML.

I am hoping a compatibility flag or similar could be implemented so that codebases built on this flaw can still operate.

Test script:
XML demonstrating the issue (rare)

 <my_tag id="1234" id="4567">aaa</my_tag>

XSL demonstrating the issue (more common)

<xsl:template match="/">
  <div id="1234">aaa</div>

  <!-- further down the code -->
  <div id="1234">bbbb</div>

Expected result:
Render the HTML

Actual result:
XSLT ERROR OCCURED: XSLTProcessor::transformToXml() [xsltprocessor.transformtoxml]: ID already defined


Add a Patch

Pull Requests

Add a Pull Request

PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Sun Dec 08 13:01:23 2019 UTC