4.2
JSHint 2.3.0 included
Removed some legacy options from JSHint configuration
Use any JSHint option, there’s a text field in which you can enter JSHint config options. (separated by comma).
A list of valid options can be found here: jshint.com/docs/options/
Rewritten JSHint-Wrapper (because JSHint works a bit differently now)
Removed some legacy JSHint options
4.1
Bugfix for a very improbable exception
Code update (mostly internal stuff)
Dialog layout improved when resized
4.0
CSSTidy updated to the current development release. This should now correctly format CSS inside @media-tags.
Integrated HTML 5 compatible tidy for validation and reformatting
3.9
New: Validate JS on save (Coda 2 only)
New: Separate CSS minification included
Fix PHP validation on save with selection
Laxcomma setting for JSHINT
JSMinify updated
3.8
Lots of bugfixes
Compatibility with other plugins improved
JSMinify updated
3.7
New: Minify on Publish (Coda 2 only)
New: Modify file extension list for PHP validate on save
Check if Growl is present, includes Growl 1.2 and Growl 1.3 notifier
CSSTidy: New option Remove last ; – control if the last ; in a block is removed or not
CSSTidy: Workaround for wrong @import behavior
JSHint: Doesn’t report useless strict warnings anymore
JSHint: Removed unused –safe option
JSHint: Added link to option documentation in the preferences
CSSTidy/JSMinify: CR/LF handling improved
PHPTidy won’t try to format php files with syntax errors
Rewritten launching of php based tools, more robust now
Refactoring PHP error display
Performance/memory improvements
Preferences layout improved, added Google+ link
3.6
“Unified” version for Coda 1 and Coda 2
Checks automatically if accidentally more than one plugin is installed
New function: PHP validate on save (Coda 2 only)
Javascript JSHint: Updated to a new version
Javascript Tidy (JSBeautify): Update to latest version, no file size limit anymore, CR/LF handling correctly now
CSS Tidy: Update to latest version, CR/LF handling correctly now
Performance improvements (loading time, js functions)
New version notification now shows the new version number…
Plugin path is now correct for Coda 1 and Coda 2
3.5 beta
Coda 2 compatible version
New preference setting for JSHint: Use smart tabs
“Go to line” (for PHP errors) now uses the API function in Coda 2, so it scrolls to the error location
Automatic update should now work correctly with Coda 1 and Coda 2
3.4
Remove proCSSor because the API service has been cancelled
3.3
Small bugfix for Prefs window layout
Internal structure improvement
Fix (improbable) memory leak
3.2
Validate PHP syntax before performing PHPtidy
Minify CSS
Updated CSSTidy
Preferences window improved (links to twitter/fb/donate)
JS Hint: Many more options
JS Hint: Respect line endings, whitespace warnings now correct
JS Tidy: Respect line endings
3.1
JS Tidy now also configurable
proCSSor bugfix
Respect Tabs/Spaces where available
Automatic Update (finally..!!)
Improved validation results
JS Hint updated
PHPTidy improvements
JS Hint: Remove (quite useless) “unsafe character” warning
Result window looks cooler now
Modularized the code
Modularized the code
Prefs window improved
3.0
Use selection
Growl (and growl-like) notifications
Results as floating window
More preferences for PHPTidy
HTML online validation: Included three validator settings
Drop curl, use cocoa instead
Use JSC call instead of shell script
JShint preferences
Improved preferences layout
Bugfixes, lots of
Nearly complete code rewrite
2.7
Show an short message after updating (only once)
Updated CSSTidy to 1.3.1
HTML Validate output improved
HTML5 support
aka workaround for tidy
JSLint replace by JSHint (upgrade, kind of)
Preference for PHPTidy: Fix statement brackets
2.6
Preferences for PHPTidy: New lines, Whitespaces, Comma spacing
Bugfix for umlaut conversion with JSTidy
2.5
Set CSS Level for validation (2, 2.1, 3)
Configure PHPTidy braces placement
2.4
Warning message (incompatible plugin) improved
Before accessing proCSSor, check if incompatible plugin present
2.3
TidyCSS update (current SVN)
W3C online response much more readable
Check for incompatible SBJsonParser
Error messages improved
Updatecheck circumvents cache now
2.2
New: Beep only for PHP validation
Preferences window now remembers the open tab
Preferences window revamped (again..)
Shortcuts also shown in the preferences
HTML Tidy version in about window now modified if “use internal” is changed
Improved some tooltips in the preferences
2.1
New: procssor.com configurable
New: JSBeautifier included
About window now part of the preferences
Preferences window revamped
Code clean-up
Shortcut for JS Beautifier
2.0
New: Encoding automatically selected
New: Custom HTML tidy configuration
New: Included a more recent HTML tidy binary
New: procssor.com online service included (experimental)
Goto line now works correctly with different line endings
Line endings now respected in HTML tidy, CSS tidy and PHP tidy
HTML tidy version shown in the about page
Preferences window new layout
JS lint now correctly handles backslashes
Error messages improved
Message sheet layout improved
1.9
New: JS Minify
HTML Validation report window now can be close without the annoying “Save Changes”-question
“Reveal in Finder” bugfix at preferences page
Donation button in the about window (Hint: click it :)
1.81
CSS tidy now handles CSS3 values starting with a dash (-)
Keyboard shortcuts for CSS tidy and Preferences
Some code clean-up
1.8
Javascript Lint (JSLint) now included
Update check now daily instead of each time Coda starts
New CSS tidy configuration: Sort attributes
1.7
HTML tidy now configurable (in the Preferences) !
Preferences are automatically saved
Bugfix when saving Coda Prefs
1.62
Automatic update check now in the background (asynchronous)
CSS tidy now configurable (in the Preferences) !
Less intrusive error-messages on connection failures
1.6
User Preferences
Automatic check for updates
CSS tidy integrated
Structured Menu (aka Submenus)
Using the HTML-tidy version delivered with OSX (PowerPC compatible)
Redesigned the error- and “validation okay”-sheets XCode-like
More encodings: ASCII, UTF-16, Windows CP-1252
All functions use the current buffer contents now
Error messages not explicitely state their origin
Updated phptidy to current version 2.10
1.4
W3C-Validation online for HTML-files
W3C-Validation online for CSS-files
Help button (on the about sheet) now opens this page
1.31
W3C-Validation service, 1st try
1.3
Improved Sheet display
Bugfixes
1.13
Validate HTML (via tidy)
Jump to error line – if PHP validation finds an error
Check for Updates (in the about-box)
File encoding can be chosen
Nice sheets, no more of those ugly alert-boxes
Menu items are only available if they should be
Lots of code cleanup
More useful “About”-dialogue, link to the plugin homepage
0.96
“About..”-dialog
Improved exception handling
Bugfixes
0.9
New features: HTML tidy, Strip PHP, PHP tidy
Included HTML Tidy
Included phptidy
Bugfixes
0.85
Bugfixes, dialogs updated
0.8
Initial release
Love this tool. Any chance of a tidy and validate for SASS? Would it be difficult to extend myself?
I don’t have the time to continue development, but the source-code is available. In order to extend the tool you’d need to know Objective-C and how to use Xcode on OSX.
Hi
While using font icons:
I am getting
“Warning: trimming empty ”
When I have
“”
This should not be an error.
Thanks!
Sorry, I forgot to state…
When using ‘Tidy HTML’ it removes these tags which is not the desired effect.
Thank you!
PHP 7.1
To get support for PHP 7.1 you will need to update your OS PHP version located in /usr/bin/php
Update it by running this command:
curl -s http://php-osx.liip.ch/install.sh | bash -s 7.1
Hi,
Can the PHP validator be updated to support/understand PHP 7? For instance it reports error with spaceship operators () although those are perfectly legitimate. :)
Run this command in your terminal to update the PHP version on your OS and restart your Coda if you have it open.
curl -s http://php-osx.liip.ch/install.sh | bash -s 7.1
The plugin use the PHP library built into OS X
Hi,
this plugins breaks ES6 variables like $(`#${htmlId}`).html()
Hi again :-)
Also support for minifying CSS variables would be deeply appreciated.
Example:
:root {
–headerheight: 52px;
–footerheight: 50px;
–textblue: rgb(8, 145, 197);
}
Thanks. :) Also, this plugin just really made my day. It’s just what I’ve been looking for. :)
PHP brace style “Always on new line” won’t work.
I prefer this style:
command
{
code …
}
but it still writes this:
comand {
code …
}
Is there a way to have the CSS minify output a .min.css file instead of minifying the file itself?
Is there a way (or better practice) for the html prettifier to leave something like this in peace? I meandered through the MAN of tidy but couldn’t find some way to exclude these.
<input type="text" name="myname[]” value=”stuff” />
or
<a href="javascript:myfunky('’)”>great link
thanks
best
manu
Hi everybody,
I’ve recognized that the css minifier doesn’t handle – @keyframes – right. It sets the keyframe name into double quotes. Is there a way to fix that?
By the way thanks for the plugin, nice work!
Hi –
unfortunately there’s not a real solution, only a hotfix which involves search and replace in the compressed file – see here: http://www.chipwreck.de/blog/software/coda-php/comment-page-7/#comment-357481 (also look at the comment below!)
Mario
Hi Mario,
I am getting penalized by Google’s PageSpped test for my CSS/JS files not being compressed enough even after using your mins plug-in on Coda.
Any thoughts?
Thanks!
Richard
@getzpro
https://developers.google.com/speed/pagespeed/insights/?url=www.getz.pro
Hi –
just had a look and according to google pagespeed there are no problems with minification… The CSS and JS files are loaded too early according to pagespeed.
Thanks for the reply.
The CSS is in the head; is Google really suggesting inlining my styles?
What am I not understanding?
Thanks!
Okay I see – Google only complains about CSS files. I thought it was also about JS files, for these it would be reasonable to put them to the bottom.
When it comes to CSS, I wouldn’t put them inline (except you use an asset framework which does this automatically). But in your case you could merge the CSS files into one file (if possible), this reduces the network requests per page.
IMHO it’s important to balance page speed and maintainability, so I wouldn’t put too much effort in optimizing each PageSpeed complaint if this makes your page much harder to maintain.
Thanks again Mario,
Yeah, I was not moving my CSS regardless of how much Google yelled LOL
I was wondering if there were any settings that could better suite this plugging for email development and if not if I could request this for a future release.
I develop a lot of emails at work. With my workflow, I generally code a HTML file, and a CSS file then use inliner.cm to convert my CSS to inline styling.
However, I have noticed a few things with the HTML & CSS Tidy functions of this plugin that cause serious issues for Email Development.
HTML:
1.)The bgcolor html attribute gets a # added in front of it which causes Outlook to panic and ignore the background color declaration altogether.
CSS:
1.)6 digit hex colors get converted to 3 digits where possible. #FFFFFF becomes #FFF. Outlook does not support 3 digit hex colors and when it comes across one it panics and dumps all the inline styling defaulting to Times New Roman and the default fantasize and styling.
2.)The “Margin” hack is required for Outlook.com. Outlook.com ignores margin declarations in css, but not when a capital “M” is used. CSS Tidy always converts this capital “M” to a lowercase “M” causing all margins to be ignored by Outlook.com
I was wondering if there are currently any settings that could help me with these issues. And if not, if you could possibly add a preference for email development that takes those issues into account and does not make those changes while tiding to preserve compatibility with Outlook and Outlook.com.
Thanks
As of PHP 5.5+ you can access a class name statically by using the following:
static::class
PHP validation raises an error when validating this syntax. Is this the plugin itself or does it use the PHP engine on the local machine to perform validation?
PHP 5.5.30 running on OS X.
Just checked the advance settings tab and it is using a different PHP executable for validation. Have changed it and it is working fine now.
Sorry for the bother.
Tidy HTML causes Coda2 to freeze with rainbow spinner when ran on this quite simple HTML code: http://pastebin.com/cx8Ay7qJ
To reproduce the bug. Launch Coda2, create a new HTML document, paste in the code from pastebin, select Plug-ins – PHP & Web Toolkit – HTML – Tidy HTML.
Rainbow spinner runs forever, Application not responding, Force Quit is the only way out. OS X El Capitan 10.11.2, Coda 2.5.13 (17380), Coda PHP & Web Toolkit 4.2beta.
Are you going to upgrade the plugin to work with PHP 7?
Hi Mario,
I have the bad habit of pressing alt+space sometimes when I’m typing fast, e.g. ” || {”
(German keyboard)
This creates a different kind of whitespace that prevents JSHint from working. It says JSHint returned nothing and I am to check that the encoding be UTF-8, which it is, though.
There is actually the JSHint-option http://jshint.com/docs/options/#nonbsp for people like me, but it doesn’t seem to be supported by the version you’re shipping. (I tried the beta 4.2 as well)
It would be great if I finally had a way to automatically find that special white-space as it often breaks my code.
Also, when editing the custom options of JSHint, they don’t always get applied. JSHint picks up the old stuff and after a Coda restart the old stuff is there in the text field. It helps to click in another text field after modifying, e.g. on PHP tab.
Maybe you find the time to look into it and thank you for your time
Awesome plugin by the way!
Cheers
I really appreciate this plugin. Good work!
One request:
with “indent” it uses spaces. In Coda it is with tabs. Could you also offer indent with tabs?
Thank you very much for putting so much effort in helping others
Which function exactly does the wrong indentation?
Tidy doesn’t ouput tabs. It prefers large file size.
I also had the message
““coda php returned nothing make sure files has no error try usign UTF-8 encoding” when i save my php files in Coda 2.5” on my Mac.
I confirm it is because of /usr/bin/php
But I don’t have MAMP, so I can’t use the solution provided by Paris Paraskeva
When openning Mac Terminal, and doing /usr/bin/php I have the following message
dyld: Library not loaded: /usr/lib/libnetsnmp.25.dylib Referenced from: /usr/bin/php Reason: image not found Trace/BPT trap: 5
The solution is here : http://kaspars.net/blog/web-development/php-netsnmp-os-x
Straight forward : type the following command in terminal mode :
sudo ln -s /usr/lib/libnetsnmp.dylib /usr/lib/libnetsnmp.25.dylib
And the message disappears
Cool, thanks.
Hi, from the last version of Coda (2.5.11), now I have this error on php code validation :
PHP returned nothing
Make sure the file has no errors, try using UTF-8 encoding.
Any idea to help me ? Your plugin is so useful that i dont know what i can do if it is not working.
Thanks, mike
Hi –
Please enable “debug mode” in the advanced section of the plugin preferences, open “Console”, start using Coda 2 and copy all the lines from the console which contain “Coda PHP Toolkit” and send them to me ( mario (at) chipwreck (dot) de)
i started getting “coda php returned nothing make sure files has no error try usign UTF-8 encoding” when i save my php files in Coda 2.5.
Anyone has an idea how i can troubleshoot this problem?
I think this started after the latest Coda update.
See above :)
Hi Mario, your reply is much much appreciated! It turns out that my Macs php located under “/usr/bin/php” is broken so i simply changed in the preferences to use the mamp version instead which i am using to test my sites anyway “/Applications/MAMP/bin/php/php5.6.2/bin/php”!
Good to hear that the problem was solved.
Hello,
I am loving the Toolkit. Especially the minify on publish feature for Coda 2. Now that Google wants even html minified, is there any plans to implement this?
Thanks,
pbatts
We use comments extensively in CSS files to help keep things organized, especially when multiple developers are maintaining the files.
Is there a way to keep CSS minify from removing the comments?
That wouldn’t really make sense IMHO… Minify is all about saving space/bandwidth – so superfluous whitespaces, unnecessary line breaks and comments are removed.
In your case I’d recommend either using something like LessCSS or a minify tool that works “on the fly”, like Google Minify (code.google.com/p/minify/).
Hi
Does the “Minify JS/CSS automatically on publishing“ works? I want to use two css-files:
style.css for editing and style.min.css for the website. I always want to edit the style.css but on save there should be the style.min.css created.
greetings
Gurkenglas
Hi, currently it does just minify the file on publishing. For a minified version which is online only I’d recommend using Google minify: http://code.google.com/p/minify/
some reason it won’t pass this php line
$array[$key] = str_replace(’& nbsp;’,’ ‘,$value);
What do you mean with “won’t pass” exactly?
When I use Tidy HTML it alway obliterates the HTML5 main element, removing it completely. How to make it not do that?
Use “html5 compatible tidy”, this should do the trick.
Thanks for the reply, however, I AM using the “html5 compatible tidy” option. It still removes the html5 main element from the document when I employ HTML Tidy. Are you saying that you cannot replicate this? Am I the only one this is happening to?
If you use the configuration “body only” it’s removed, with the other configurations I can’t reproduce it.
When I run a Validate HTML on my sample document, this is the result…
line 231 column 1 – Error: is not recognized!
line 231 column 1 – Warning: discarding unexpected
line 313 column 1 – Warning: discarding unexpected
Info: Document content looks like HTML5
2 warnings, 1 error were found!
This document has errors that must be fixed before
using HTML Tidy to generate a tidied up version.
About this fork of Tidy: http://w3c.github.com/tidy-html5/
Bug reports and comments: https://github.com/w3c/tidy-html5/issues/
Or send questions and comments to html-tidy@w3.org
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
HTML language reference: http://dev.w3.org/html5/markup/
Validate your HTML5 documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium
hmm, the code for the main element is also removed from the pasted validation in my reply.
Should read:
line 231 column 1 – Error: (left caret)main(right caret) is not recognized!
line 231 column 1 – Warning: discarding unexpected (left caret)main(right caret)
line 313 column 1 – Warning: discarding unexpected (left caret)/main(right caret)
Info: Document content looks like HTML5
2 warnings, 1 error were found!
This document has errors that must be fixed before
using HTML Tidy to generate a tidied up version.
I see. Use “custom configuration” for the HTML tidy and add “main” to the option “new-blocklevel-tags”:
new-blocklevel-tags: article,aside,command,canvas,dialog,details,figcaption,figure,footer,header,hgroup,menu,nav,section,summary,meter,main
Hello there!
Great plugin. A couple comments:
PHP tidy behaves differently when selecting the command from the menu and when pressing the keyboard shortcut.
If selected from a menu, tabs are not replaced by spaces (the way it should be). But when run with keyboard shortcut, tabs get replaced by spaces.
The shortcut for tidying requires both hand and a forehead to hit all the keys. I’d like to be able to specify a shorter one. Even better, I’d like to auto-tidy at save time (an option to do that).
Hi –
php tidy should not behave differently in any way, because the keyboard shortcuts just trigger menu items…
Auto-tidy seems (given the rest of the comments and my experience) not the best idea in many cases. Therefore that’s not a top priority now.
About shortcuts: They can’t be easily changed given the Coda plugin setup, you have to put then in the code when creating the menu, therefore I’m afraid that won’t be possible for now.
Oh dear. Now that I test, there is no difference between tidying with a keyboard shortcut vs selecting from the menu. Earlier I was surprised and tested many times with unexpected results. Now I am not able to reproduce this. I guess it was how the stars were aligned (I refuse to acknowledge any fault of my own, ever).
Actually, I noticed that HTML-tidying replaces tabs with spaces. It may just be that the star alignment caused T and H to switch locations on my keyboard. Again, no fault of my own :-)
Thanks for your reply and for the plugin.
Thanks for this great plugin. If you’re having problems with HTML tidy striping out empty elements (such as “span” usage frequently found in bootstrap projects) then switch to HTML5 compatible tidy mode and add “drop-empty-elements: no” to the custom configuration. Seems to be working well for me. Look forward to further developments.
I’m using your Coda PHP & Web Toolkit 4.2beta and, as a self-confessed novice, am just starting to familiarise myself with all of the the functionality. I have also encountered issues with Tidy removing empty tag elements such as or . As advised, I’ve used custom configuration and added span and strong to the comma-separated list of tags but this is not changing the behaviour of Tidy.
However, I found through experimentation that if I select ‘Use HTML5 compatible Tidy’ in the Preferences and add ‘drop-empty-elements: no’ to my Custom Configuration, Tidy appears to start to behave.
Is this method using the experimental fork of Tidy on GitHub that you mentioned? Have I gone about setting this up the right way?
Thanks for a great plugin.
Great Plugin,
I just dont like the “success” floating windows, I wanted to edit the source code, but these part’s are in the compiled tidy files :(
could you make these open source or/and an option to disable the success floating windows?
thanks for sharing!
Hi –
I’ll make the source code available soon, as promised :) Takes still some time until I sort out some issues – which make the source code a bit more “readable”.
Great plugin.. the only thing that drives me nuts (and it could just be that I’m using syntax the plugin doesn’t like).. Is the way it cleans up @font-face.. Every (second?) time I run it, it will shift quotes around and cause my CSS to fail until I un-shift them..
So:
@font-face {
font-family:”coolveticaRegular”;
src:url(/images/Fonts/Coolvetica/coolvetica_rg-webfont.eot);
src:url(/images/Fonts/Coolvetica/coolvetica_rg-webfont.eot?#iefix) format(“embedded-opentype”),url(/images/Fonts/Coolvetica/coolvetica_rg-webfont.woff) format(“woff”),url(/images/Fonts/Coolvetica/coolvetica_rg-webfont.ttf) format(“truetype”),url(/images/Fonts/Coolvetica/coolvetica_rg-webfont.svg#coolveticaregular) format(“svg”);
font-weight:400;
font-style:normal;
}
Becomes:
@font-face {
font-family:”coolveticaRegular”;
src:url(/images/Fonts/Coolvetica/coolvetica_rg-webfont.eot);
src:url(/images/Fonts/Coolvetica/coolvetica_rg-webfont.eot?#iefix) format(“embedded-opentype)”,”url(/images/Fonts/Coolvetica/coolvetica_rg-webfont.woff”) format(“woff)”,”url(/images/Fonts/Coolvetica/coolvetica_rg-webfont.ttf”) format(“truetype)”,”url(/images/Fonts/Coolvetica/coolvetica_rg-webfont.svg#coolveticaregular”) format(“svg”);
font-weight:400;
font-style:normal;
}
Thanks for this very useful plugin!
And +1 for my previous posters feature request! Validation on the fly…
Searched a Plugin like this. Thank u for sharing this.
Heya,
1st thing: love the plugin.
2nd: it would be great if you could add an option, like you already have with paragraphs for other elements, or all elements. With the rise of font icons and the use of an empty “i” tag, its seems a good idea to have: drop-empty-tags as a configuration option.
Whenever I am working with code that includes, say, font awesome icons, they are deleted as they are empty tags
You can use “custom…” as configuration in the HTML tidy settings. There you can enter “drop-empty-paras: no”.
Totally, and i’ve done that, but that only keeps the “p” tags. I’m talking about using things like font awesome where you utilise empty “i” tags. For example…
If you tidy this…
Then the “p” tag remains but the “i” tag is removed. Thus if we could extent the custom options to add a “drop-empty-tags” in general rather than just “drop-empty-paras”
Yes, right. HTML tidy doesn’t support this in the included version. See here:
http://stackoverflow.com/questions/18372185/html-tidy-removes-empty-tags-such-as-i-class-icon-foo-i
You can exchange the included HTML tidy with the version mentioned in the stackoverflow question, but in this case you have to compile HTML tidy yourself. I’ll try to find some time the next weeks to update the plugin or I’ll put the source code online.
Looks like my code was stripped. Check it out here:
http://pastebin.com/yB8yiudX
Yes, that’s the normal behaviour of HTML tidy. But you can add custom tags in the plugin preferences, Tab HTML. Use custom configuration and then add a comma-separated list of tags, like this:
new-blocklevel-tags: article,aside,command,i,what,ever
I just installed the latest beta version of the plugin, and tested it on my HTML code. When I select to tidy the HTML, it strips out all of my custom tags. Is there any way to correct that?
Here’s a code example before and after:
[a href=”#” rel=”nofollow”][i][/i] Messaging[/a]
After:
[a href=”#” rel=”nofollow”]Messaging[/a]
Finding a plugin like this for a long time! Thank you!
There seems to be a problem with Coda 2.5.1 and Your beta 4.2. I get this:
Exception: TypeError: null is not an object (evaluating ‘JSHINT.errors[i].line’) JSHINTWRAP@/Users/asdf/Library/Application Support/Coda 2/Plug-ins/PhpPlugin.codaplugin/Contents/Resources/jshint-min.js:948:159 global code@/Users/asdf/Library/Application Support/Coda 2/Plug-ins/PhpPlugin.codaplugin/Contents/Resources/jshint-min.js:954:16
I hope it will work eventually, I have found a lot of use for this excellent plugin, so thank you developer :-)
Hi –
this looks like a specific error of a JS file – does this also happen with other JS files (smaller ones)?
OK, just installed 4.2 beta, I let you know fi I find anything :-)
Btw. the html formatter always starts with this:
isn’t it enough just write:
?
DI have been using your nice plugin in Coda 2.0. Does it work with the new Coda 2.5?
Yes, it should work with Coda 2.5. (It doesn’t use any of the new functions though…)
Hello
very nice plugin: is there a way to have inline check? Now we need to perform validation check: it would be great to be able to have php validation on the fly, like happens for IDE like Netbeans for example, when you forget a bracket , or a semicolon it always warns.
Ciao
Rudy
I’d like this as well. As much flak as Dreamweaver gets, the realtime errors you get with php has really spoiled me. I went back to Coda and can’t believe it doesn’t support it.