{"id":7372,"date":"2012-07-04T20:53:35","date_gmt":"2012-07-04T18:53:35","guid":{"rendered":"http:\/\/www.chipwreck.de\/blog\/?p=7372"},"modified":"2012-07-04T20:55:27","modified_gmt":"2012-07-04T18:55:27","slug":"coda-php-web-toolkit-3-7","status":"publish","type":"post","link":"https:\/\/www.chipwreck.de\/blog\/2012\/07\/04\/coda-php-web-toolkit-3-7\/","title":{"rendered":"Coda PHP &#038; Web Toolkit 3.7"},"content":{"rendered":"<p>A new version again, download it or use the updater in the plugin.<!--more--><\/p>\n<h4>New: PHP Validate on Save (Coda 2 only)<\/h4>\n<p>Now you can edit the list of file extensions for which the Validate on Save jumps in. The default is <q>php,phtml<\/q>, but you can enter more or different extensions if necessary. Separate them by comma, without spaces.<\/p>\n<p><a href=\"https:\/\/www.chipwreck.de\/blog\/wp-content\/uploads\/2012\/07\/php-validate-on-save-extensions.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.chipwreck.de\/blog\/wp-content\/uploads\/2012\/07\/php-validate-on-save-extensions-300x144.png\" alt=\"php validate on save: file extensions\" title=\"php validate on save extensions\" width=\"300\" height=\"144\" class=\"alignnone size-medium wp-image-7376\" srcset=\"https:\/\/www.chipwreck.de\/blog\/wp-content\/uploads\/2012\/07\/php-validate-on-save-extensions-300x144.png 300w, https:\/\/www.chipwreck.de\/blog\/wp-content\/uploads\/2012\/07\/php-validate-on-save-extensions-120x57.png 120w, https:\/\/www.chipwreck.de\/blog\/wp-content\/uploads\/2012\/07\/php-validate-on-save-extensions.png 513w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<h4>New: Minify on Publish (Coda 2 only)<\/h4>\n<p>(Still experimental) There are two new preferences: <q>Minify JS on publish<\/q> an <q>Minify CSS on publish<\/q>. When checked and you publish a CSS or Javascript file (.css\/.js) a minified version the file is uploaded. Your original (local) file is not modified.<\/p>\n<p><a href=\"https:\/\/www.chipwreck.de\/blog\/wp-content\/uploads\/2012\/06\/css-prefs.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.chipwreck.de\/blog\/wp-content\/uploads\/2012\/06\/css-prefs-101x120.png\" alt=\"CSS Preferences \/ Minify on publish\" title=\"css prefs\" width=\"101\" height=\"120\" class=\"alignnone size-thumbnail wp-image-7198\" srcset=\"https:\/\/www.chipwreck.de\/blog\/wp-content\/uploads\/2012\/06\/css-prefs-101x120.png 101w, https:\/\/www.chipwreck.de\/blog\/wp-content\/uploads\/2012\/06\/css-prefs-252x300.png 252w, https:\/\/www.chipwreck.de\/blog\/wp-content\/uploads\/2012\/06\/css-prefs.png 521w\" sizes=\"auto, (max-width: 101px) 100vw, 101px\" \/><\/a><\/p>\n<p>Please check afterwards if your uploaded files behave correctly &#8211; in case of problems uncheck the preferences and publish again (then the uncompressed file is uploaded). And of course report what&#8217;s wrong.<\/p>\n<h4>Improvements \/ Bugfixes<\/h4>\n<ul>\n<li>Check if Growl is present<\/li>\n<li>Includes Growl 1.2 and Growl 1.3 notifier, automatically and hopefully selects the right one<\/li>\n<li>Some bugfixes, typos, improved logging<\/li>\n<li>CSSTidy: New option <q>Remove last ;<\/q> &#8211; control if the last <q>;<\/q> in a block is removed or not<\/li>\n<li>CSSTidy: Workaround for wrong @import behavior<\/li>\n<li>JSHint: Doesn&#8217;t report useless strict warnings anymore<\/li>\n<li>JSHint: Removed unused &#8211;safe option<\/li>\n<li>JSHint: Added link to option documentation in the preferences<\/li>\n<li>CSSTidy\/JSMinify: CR\/LF handling improved<\/li>\n<li>PHPTidy won&#8217;t try to format php files with syntax errors<\/li>\n<li>Rewritten launching of php based tools, more robust now<\/li>\n<li>Refactoring PHP error display<\/li>\n<li>Performance\/memory improvements<\/li>\n<li>Preferences layout improved<\/li>\n<\/ul>\n<p><\/p>\n<p>Problems? Just post a comment or write an email (mario at chipwreck dot de). Since there are now more than 420 comments I&#8217;m thinking about using some kind of forum or bugtracker maybe..<\/p>\n<h4><strong><a href=\"\/blog\/software\/coda-php#download\">Click to download and\/or comment \u00bb<\/a><\/strong><\/h4>\n","protected":false},"excerpt":{"rendered":"<p>A new version again, download it or use the updater in the plugin.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[20,38],"tags":[82,33],"class_list":["post-7372","post","type-post","status-publish","format-standard","hentry","category-coda","category-updates","tag-coda","tag-update"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/paPEN-1UU","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.chipwreck.de\/blog\/wp-json\/wp\/v2\/posts\/7372","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.chipwreck.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.chipwreck.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.chipwreck.de\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.chipwreck.de\/blog\/wp-json\/wp\/v2\/comments?post=7372"}],"version-history":[{"count":0,"href":"https:\/\/www.chipwreck.de\/blog\/wp-json\/wp\/v2\/posts\/7372\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.chipwreck.de\/blog\/wp-json\/wp\/v2\/media?parent=7372"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.chipwreck.de\/blog\/wp-json\/wp\/v2\/categories?post=7372"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.chipwreck.de\/blog\/wp-json\/wp\/v2\/tags?post=7372"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}