Title: Bug Last modified: September 1, 2016 --- # Bug * Resolved [Luiz Bills](https://wordpress.org/support/users/luizbills/) * (@luizbills) * [9 years, 9 months ago](https://wordpress.org/support/topic/bug-163/) * Everytime that a file is saved, extra whitespaces are added. * [https://wordpress.org/plugins/aceide/](https://wordpress.org/plugins/aceide/) Viewing 9 replies - 1 through 9 (of 9 total) * Plugin Author [shanept](https://wordpress.org/support/users/shanept/) * (@shanept) * [9 years, 9 months ago](https://wordpress.org/support/topic/bug-163/#post-7675860) * Hi luizbills, * Whereabouts in the file does it add extra whitespace? Do you have anything weird in the setup of your WordPress instance? * Thanks, Shane Thompson * [lotusms](https://wordpress.org/support/users/lotusms/) * (@lotusms) * [9 years, 6 months ago](https://wordpress.org/support/topic/bug-163/#post-8391280) * I agree with Luiz. It adds about 20 empty lines on the top of the editor that are also parsing to the document source. If you check out [mysite](http://www.lotusmarketingsolutions.com/) And check the source, you’ll see it on the top above the doctype declaration. * I delete it before I edit a file and it adds it again as soon as I re-open ACEide * Plugin Author [shanept](https://wordpress.org/support/users/shanept/) * (@shanept) * [9 years, 6 months ago](https://wordpress.org/support/topic/bug-163/#post-8394473) * Hi Lotus, * I can indeed see that you have a lot of whitespace added to the top of your file. I can not reproduce this issue with a clean install of WordPress, so I am wondering whether there may be a plugin conflicting with the AceIDE plugin installation. * Please note that if there is another plugin outputting extra whitespace, it will tamper with the download of the file contents into the browser. That is the issue in your case, lotusms. * If you go to the following URL, you will notice that extra whitespace is being output during an AJAX request, the request is not being handled because there is no action specified. * I would hazard a guess that this whitespace is coming from your theme’s functions. php file, as there may be some whitespace before the opening PHP tag. This will be added into files during editing, as they are downloaded with this extra whitespace. * I will have a look into some simple encoding so we may trash any output that is not file related, perhaps a simple base64 encoding of the file contents then trashing leading whitespace before decoding the file. * In the mean time, I hope this information helps you. If you would like, I can have a look at the install and see if I can spot any plugin conflicts. * Kind Regards, Shane Thompson * Plugin Author [shanept](https://wordpress.org/support/users/shanept/) * (@shanept) * [9 years, 4 months ago](https://wordpress.org/support/topic/bug-163/#post-8640912) * Hi Luizbills and Lotusms, * The latest version of AceIDE (2.5.4) now has some more checking to ensure no extra data is added to the start of the file. * Please feel free to test and get back to me with your thoughts. * Kind Regards, Shane * [Kyle Charlton](https://wordpress.org/support/users/ktc_88/) * (@ktc_88) * [9 years, 4 months ago](https://wordpress.org/support/topic/bug-163/#post-8643199) * Hi, First off thanks for all of your work on this plugin, I use it all the time. I’m not sure if this is related to this thread or not but after I updated to 2.5.4, every time I open a file I get this pre-pended to the file ===FILE_CONTENTS_START === * [gmoon](https://wordpress.org/support/users/gmoon/) * (@gmoon) * [9 years, 4 months ago](https://wordpress.org/support/topic/bug-163/#post-8643253) * great plugin, good work but * for me is the same bug like Kyle, after last update every files that open with aceide put on the begining ===FILE_CONTENTS_START=== * Plugin Author [shanept](https://wordpress.org/support/users/shanept/) * (@shanept) * [9 years, 4 months ago](https://wordpress.org/support/topic/bug-163/#post-8644585) * Hi Kyle and gmoon, * Thanks for your responses. This marker is, in fact, to do with fixing the above bug. * This bug introduces a change to the javascript file sent to the browser, without which you would definitely see this marker. * Can you please clear your cache and try again, I’m sure this will solve your problem. * Kind Regards, Shane * [Kyle Charlton](https://wordpress.org/support/users/ktc_88/) * (@ktc_88) * [9 years, 4 months ago](https://wordpress.org/support/topic/bug-163/#post-8647090) * Thanks clearing cache worked! * Plugin Author [shanept](https://wordpress.org/support/users/shanept/) * (@shanept) * [9 years, 4 months ago](https://wordpress.org/support/topic/bug-163/#post-8649349) * Great! * I shall mark this as resolved. Thanks for your contribution! * Kind Regards, Shane Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘Bug’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/aceide_f0f0f0.svg) * [AceIDE](https://wordpress.org/plugins/aceide/) * [Frequently Asked Questions](https://wordpress.org/plugins/aceide/#faq) * [Support Threads](https://wordpress.org/support/plugin/aceide/) * [Active Topics](https://wordpress.org/support/plugin/aceide/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/aceide/unresolved/) * [Reviews](https://wordpress.org/support/plugin/aceide/reviews/) * 9 replies * 5 participants * Last reply from: [shanept](https://wordpress.org/support/users/shanept/) * Last activity: [9 years, 4 months ago](https://wordpress.org/support/topic/bug-163/#post-8649349) * Status: resolved