Online code php viewer
![online code php viewer online code php viewer](https://scodeweb.com/images/codes/1241/view_full-sourcecode-responsive-web-shop-online-mo-hinh-php-mvc.jpg)
![online code php viewer online code php viewer](https://www.php-nuke.org/wp-content/uploads/2018/08/PHP-CSS-Code-Editor.png)
We've had some server maintenance going on, and unfortunately monitoring missed one service on one server, which was running This is just a quick post to apologise for the recent outages. We're hoping for a strong 2016 for us and everyone else. We have just made a few changes, including: moving to a newer faster server, fixing up some layout issues, fixing some bugs with type detection, forcing SSL (HTTPS), and other things which I've already forgotten.Īs usual, if you notice anything amiss just let us know!įirst off, happy holidays and new years to those that celebrate it. Unfortunately we've been too busy to give ToHTML much love recently, but I just fixed an issue with certain code being submitted resulting in a ERR_BLOCKED_BY_XSS_AUDITOR error in Chrome by having the source base64 encoded in-transit, and also added some cell padding to make text selection easier. Thanks to H Gleaves, K Gillen, and Odzhan for reporting these! I then added a "Copy to clipboard" button as suggested by T Miseur, and lastly, BASIC UNICODE SUPPORT! Enjoy :) I have fixed a bug that caused leading whitespace to be removed, made it replace MS Word 'smart quotes' with real quotes, and also added generation datestamps. This is a bit of a hobby project to keep alive, since I use it myself. Hopefully ERR_BLOCKED_BY_XSS_AUDITOR issue does not come back in Chrome! Removed all Base64 encoding to resolve this. Please let me know if this is not the case for you.Īlso fixed a few minor bugs with type detection inc Bash.įound an edge case where the encode-on-POST did not happen, resulting in garbage output. It was brought to my attention that ERR_BLOCKED_BY_XSS_AUDITOR is an issue again, but this appears to be only when POSTing directly instead of using the web UI. We are investigating!įixed! It turned out to be an issue in the code to do with handling non-SSL requests, which would sometimes come from our WAF.
#Online code php viewer update#
Someone has pointed out that certain code, specifically SQL UPDATE statements at least, appear to break the site causing a 520 error, when the site is actually kind of worknig.