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

[Bug] When exporting to XML, if debugging is on, any debug messages also get stored in the XML file. #160

Open
redlagoon opened this issue Jun 5, 2018 · 0 comments

Comments

@redlagoon
Copy link

redlagoon commented Jun 5, 2018

I am not sure if this is related to the Importer, after all, the Exporter is quite different, but it's the other 50% of this tool.

How to replicate:

  1. Try to get a plugin to cause an error that would only get output at the head, but not break the site, for me, it was Reset-WP, it now shows:
Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; ResetWP has a deprecated constructor in C:\xampp\htdocs\wordpress\wp-content\plugins\reset-wp\reset-wp.php on line 29
  1. Go to the Export functionality.

  2. Export a file. Any options.

  3. Open the .xml file. You should now see, at the first line, the very same error and anything that got output.

This renders the exported file useless, unless you remove these lines.

My guess is that you have an ob_start somewhere that also catches it.

@redlagoon redlagoon changed the title [Not even sure] When exporting to XML, if debugging is on, any debug messages also get stored in the XML file. [Bug] When exporting to XML, if debugging is on, any debug messages also get stored in the XML file. Jun 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant