Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getXML() usage and enhancement #35

Closed
GoogleCodeExporter opened this issue Aug 8, 2015 · 3 comments
Closed

getXML() usage and enhancement #35

GoogleCodeExporter opened this issue Aug 8, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

Wanted to get this function clarified. getXML() seems to be a simple
wrapper for reading a XML file.

1. Should this be used more? Even functions like menu_data() the exact code
that is contained by getXML(). Should these be changed to getXML()?

2. Should it be enhanced to support addCData()? Currently the XML DOM load
by getXML() can not be manipulated with the help of addCData(). The fix
would be swapping:

   simplexml_load_string($xml, NULL, LIBXML_NOCDATA)

with:

   simplexml_load_string($xml, 'SimpleXMLExtended', LIBXML_NOCDATA)

Wanted to put this up for debate. As I have no good idea of how much we
actually use this function in the core.

Original issue reported on code.google.com by martijn.personal@gmail.com on 23 Feb 2010 at 10:07

@GoogleCodeExporter
Copy link
Author

This function is used in the core quite extensively. Can you make that change 
and see
if it breaks anything? Since all the init xml files are read by that function 
it will
be pretty clear if this works or not.

Thanks Martijn

Original comment by ccagle8 on 23 Feb 2010 at 2:03

@GoogleCodeExporter
Copy link
Author

So it was just menu_data() being behind on the rest of the core once more?

What a little bugger that function tends to be ;-) I will be on my PC with SVN 
set-up
in about an hour or so, will update the function and see whether menu_data() 
wants to
play along with it.

/Switching this ticket to me./

Original comment by martijn.personal@gmail.com on 23 Feb 2010 at 2:14

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

This should now be fixed. Might need some more testing but the code shouldn’t 
give to
much problems.

Original comment by martijn.personal@gmail.com on 23 Feb 2010 at 7:29

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant