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
Coda PHP & Web Toolkit
I had a quick question…I noticed that when I use the html tidy option it automatically changes my doctype to strict when I would like it to stay in transitional…is there any way to change that so that it doesn’t change my doctype declaration? thanks in advance for any advice…ps. I love this plugin minus this small issue.
Hi -
which config setting do you use for HTML tidy?
I am using the default configuration
This should work, I tried it with this doctype:
!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN” “http://www.w3.org/TR/html4/loose.dtd”
Otherwise send me the HTML-file, then I’ll have look.
Hi Mario
I contacted earlier just thought you might want the crash report error:
Link (dyld) error:
Symbol not found: _objc_setProperty
Referenced from: /Users/KT/Library/Application Support/Coda/Plug-ins/PhpPlugin.codaplugin/Contents/MacOS/PhpPlugin
Expected in: /usr/lib/libobjc.A.dylib
Thanks
Steve
Hi -
okay, some additional questions:
So Coda runs without the plugin normally? The plugin crash happens at startup? Which OSX-Version and which platform (ppc/intel ~ 32bit/64bit) do you use?
thx,
mario
Hi Mario
Coda runs okay until the plugin is installed then I delete the plugin file to get it working correctly I am using osx 10.4.11 Intel Core duo (not sure on 32-64bit??)
Do you want the crash report?
Thanks again
Steve
Hi -
yes, please – could you send me the logfile via email? mario (at) chipwreck (dot) de
OSX 10.4 is 32bit – maybe 10.4 is the problem, since I haven’t been able to test it on 10.4.
Hi again -
I’m afraid the code isn’t compatible with OS X 10.4 (according to Xcode) – so if you’ve got any chance to upgrade to 10.5/10.6 the plugin should run without problems.
I think i will upgrade – thanks for all your effort and I look forward to using the plugin after upgrade. If there is anything I can do for you just let me know
Thanks again
Steve
Hi
I have tried to download the phptoolkit for coda which looks great. Only problem is it crashes coda when it starts and continues to do so, is there something I am missing ?? I am running MAMP and coda 1.6.10
Thanks in advance
Steve
Hi
I am afraid the plugin I have downloaded crashes coda 1.6.10 when it is opened and continues to do so is there something I am missing?? Thankyou in advance
Steve
Hei!
I cannot save settings in coda after install your plugin. Anyone else with this problem?
Greetings.
Markus
Hi -
I assume you clicked “save” :) Could you open the Coda Preferences file located here:
YOUR_HOME_FOLDER/Library/Preferences/com.panic.Coda.plist
(You need a plist-editor, included for example in the Apple Developer Tools)
..and look if you find keys named “dechipwreckCssTidyConfig” or similar? (If you haven’t got an appropriate editor, drop me a mail)
Regards,
mario
There ist no “save”button on global coda-settings. And no, i doent find somethink like “dechipwreck…”.
Okay, misunderstood :) Coda preferences can’t be saved.
Will try to find out if it’s got something to do with the PHP Toolkit and if so, how to resolve. If someone else has the same problem – don’t hesitate to post a comment here.
UPDATE: Problem found, fixed in the upcoming version (the next days I suppose)
The about-windows says v0.96 – is this the latest version?
Eh no, the current version should be 1.62 .. v0.96 is much too old. Simply go to: “your user folder -> Library -> Application support -> Coda -> Plugins”, delete the old PhpToolkit plugin bundle, download the current one and double click it. This should work.
Absolutely awesome. Thanks for this!
This version appears to ignore the ‘Default Line Endings’ set in coda’s preferences?
Set to use windows
http://lulzwut.com/php/before.png
http://lulzwut.com/php/after.png
Hi -
okay, I’ll have a look. One question though: Was that any different in the previous versions?
[UPDATE Jan,25th] And again – no API function from Coda to read the current line endings.. But I’ll try to find a workaround of course..
mario
Huge improvement on version1.6
interface and the way it’s function.
Great work and Thanks
It works great on my G5, thanks for the PPC compatibility.
This is fantastic. Thanks so much!!
When running Tidy PHP I get the following error:
An application error has occurred.
This error will cause instability and it is recommended you quit and relaunch Coda.
(NSInvalidArgumentException) *** -(NSCFArray insertObject:atIndex:]: attempt to insert nil
Running php-toolkit 1.4 with Coda 1.6.7
Any suggestions?
Could you look at the Console output – there should be some more lines .. Or send me the file if possible?
[Update Nov, 26th] No reply until now – so I’ll assume it hasn’t happened again. Otherwise: Send a mail or comment here.
I got the same error “(NSInvalidArgumentException) *** -[NSCFArray insertObject:atIndex:]: attempt to insert nil” here is what console saids.
12/11/09 7:33:04 PM Coda[21547] NSExceptionHandler has recorded the following exception:
NSInvalidArgumentException — *** -[NSCFArray insertObject:atIndex:]: attempt to insert nil
Stack trace: 0x43319a 0x929ebe3b 0x96565dcb 0x96565e0a 0x95a3c660 0x9595a8d4 0x9595a7e4 0×14876743 0x14874ec5 0x95dcdb9b 0x14874d8b 0x95d8be8f 0x95d8bdcc 0x95d8bc52 0x95d8b2ab 0x95d8aafe 0x95d8a3b8 0x95d88af7 0x95d556a5 0x95cb2fe7 0x95c801d8 0×3512 0×3439 0×2
12/11/09 7:33:04 PM Coda[21547] NSExceptionHandler has recorded the following exception:
NSInvalidArgumentException — *** -[NSCFArray insertObject:atIndex:]: attempt to insert nil
Stack trace: 0x43319a 0x929ebe3b 0x96565dcb 0x96565e0a 0x95a3c660 0x9595a8d4 0x9595a7e4 0×14876743 0x14874ec5 0x95dcdb9b 0x14874d8b 0x95d8be8f 0x95d8bdcc 0x95d8bc52 0x95d8b2ab 0x95d8aafe 0x95d8a3b8 0x95d88af7 0x95d556a5 0x95cb2fe7 0x95c801d8 0×3512 0×3439 0×2
I figured out the problem, if you dont save the document you get that error, once you save it and run it again it works fine.
Thx! Just updated the docs – I assume the document was new (=empty before you entered text and saved it) ?
The behaviour of the functions is a little bit inconsistent: php validation and php strip comment take the current editor buffer (regardless of what’s on the disk) – the other functions use the file on disk (so if you don’t save the file might be yet empty).
[UPDATE 1:] The beta version now handles this more graciously (beeps or tells you that you should save the file before).
[UPDATE 2:] One solution would be to save the file automatically (maybe not what everyone wants), another one to create a temp file with the buffer contents (nicer but creates lots of new error possibilites..:). I’ll have a look.
Thanks for the reply, (I got your notification). The document was new but not empty. I created a new document and pasted code from another document and did not save. I used the tidy functionality and that is when I got the error. Once I Saved the file it worked. Thanks for the update though.
Yes..that’s what I meant: The file on disk was still empty.
The beta version (see above) doesn’t have this problem anymore – you can automatically save the file before running CssTidy or PhpTidy. HtmlTidy works now with the current buffer contents (regardless of saving or not).
Awesome. Works a treat. Keep up the great work.
Thanks
Brent
[...] Coda PHP Toolkit | chipwreck [...]
[...] Coda PHP Toolkit [...]
This is great! Looking forward to trying this out! Many thanks for this :-)
[...] Coda PHP Toolkit [...]
This is great – seems to be exactly what Coda was missing for me… However: :)
When I try and validate the PHP I get an error: ‘Errors parsing -’ (with no further error details). If I click ‘Go to line’ nothing happens…
I’m on coda 1.6.5, PHP5.3.0 with Snow Leopard…
Thanks for your help!
Thanks.
Now…: “Go to Line” is a bit tricky if the erroneous line is out of focus.
“Errors parsing – ” is the “correct” answer from php, since the file is directly sent to php (without filename). What happens, if you open the Terminal and enter “php -l yourfile.php” ?
Hi Mario,
Sorry for the delay!
I’ve have tried what you suggest… with the following code error:
With the plugin, I get the ‘Errors parsing – ‘ message.
When I try in terminal I get:
PHP Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in test.php on line 3
Errors parsing test.php
So I guess the plug-in is picking up the second error rather than the first?
if there’s anything else I can try, please let me know.
Best wishes,
Kevin
Yes, it seems the first (and much more interesting) error is either not visible or somehow discarded.
Could it be that the window is too small and hides the first error? It can be resized and reacts somewhat strange then, see the screenshot (click here)
So could you try to restart Coda, maximize the Coda window and drag the error-window at the bottom right handle?
thx,
mario
Just uploaded a new beta version- the window handling is fixed now.
Hey Mario,
No luck I’m afraid… I downloaded the beta and tried that, and can see that the error is now presented in a textarea, but it still just says ‘Errors parsing – ‘.
Let me know if I can do anything else to help identify the issue!
Best wishes,
Kevin
Okay, please download the current beta again, I put in some debugging code. Try validating some erroneous php-file and open the Console (viewing all messages). The error is being reported there like this “Coda PHP Plugin – PHP error: Parse error: syntax error, unexpected T_STRING in – on line 9 Errors parsing -” – what does the Console say?
And: what PHP version is reported in the “About…”-window of the plugin?
Thx for your help.
Hi Mario,
Console is showing:
25/10/2009 17:17:01 Coda[2757] Coda PHP Plugin – PHP error: Errors parsing -
Only other message I receive is about the PHP Plugin starting…
In About PHP Toolkit, local PHP Version is PHP 5.3.0 (cli).
Hope this helps!
Cheers,
Kev
Okay, finally found the error: If you use a php.ini-file (like /private/etc/php.ini) and set “display_errors” to off, this happens.
Hey, for some reason, with certain files, I’m unable to save them after using HTML tidy. Permissions are correct, so I’m not sure what’s going on. Any ideas?
[Updated Nov, 12th] Had seemingly nothing to do with the plugin – a filesystem problem.
Very awesome, thanks a lot!
Mario I keep getting this error when trying to use TidyHTML in Coda 1.6.4:
“Error – No output received in replaceEditorTextWith”
I’ve gotten error this with every type of encoding option,
Any ideas? :(
Vielen Dank!
Is fixed in the latest version.
very very very nice! thank you
[...] Contact Coda : Plugin PHP 18 août 2009 No comments yet Hello there! If you are new here, you might want to subscribe to the RSS feed for updates on this topic.Powered by WP Greet BoxRécemment je vous avez écris un post complet sur les plugins pour Coda indispensable. Ce matin je vous en ai trouvé un autre tout à fait indispensable pour les développeurs php. Il s’agit de « PHP Toolkit ~ Coda Plugin » [...]
Nice work!!!!!!
Please integrate into coda via plug-in:
http://www.bluestatic.org/software/macgdbp/
I’ll have a look :) At the moment I’m trying to integrate the W3C Validator which is not that easy, since the API misses some methods needed..
But thanks for the suggestion.
[...] Plugins An open interface allows anyone to create plugins for the software, meaning some great addons are available like CSS Tools (compress and tidy your CSS) and PHP Validator. [...]
A new beta is available – see http://www.chipwreck.de/blog/2009/07/04/coda-php-toolkit-new-beta/
Any idea when the next version is coming to fix the issue with invisible text when using the tidy?
Hi – I suppose in about 2 weeks I’ll find some time to update the plugin.
At last! This means I can use coda as a proper development tool :) Thank you.
After I run php tidy in 1.6.4 all the end of line characters start to show – switching invisible characters on / off does nothing. How can I hide them?
Two questions: Do other invisible characters (like “->” for tabs) also appear and in which encoding is the php-file? You could also send me a small file in which those problems appear (see Contact for my mailaddress)
Regards,
Mario
Question answered – in the next update this bug will be fixed.
Great plugin, thank you! Coming from textmate, this is exactly the thing I missed (and which caused me to stay in textmate). I hope ISO-8859-1 support is coming soon. UTF-8 is great of course, but if you have older sites that you don’t want to convert, more encodings would help.
Thanks! As soon as the Coda API supports something like “getCurrentEncoding” I’ll put this possibility in the plugin.
The new version supports more encodings – you have to select the encoding, since the API doesn’t yet tell me which the right one is, but this should help :)
[...] PHP Toolkit This plugin makes it easy to validate and clean up PHP files. [...]
Hi,
Just wondering, I’m trying to use the Tidy HTML feature, but I’m getting “Error – No output received” … I’m on Mac OS X Tiger – does it matter only for the PHP features, or also the HTML? What to do?
Thanks
G
Yes, you need at least Leopard (or php5 installed) for the PHP-specific features (I updated the requirements above). But HTML tidy should work nevertheless. Could you try it out with another HTML-File? Or send me one per mail, which makes problems..
Hope this helps.
Seems to fail on 1.6.3. I’m getting this error using php tidy:
Parse error: parse error, expecting `T_VARIABLE’ or `’$” in /Users/aaron/Library/Application Support/Coda/Plug-ins/PhpPlugin.codaplugin/Contents/Resources/phptidy-coda.php on line 387
I hope this can be fixed, I’ve been looking for a PHP plugin for a while!
Aaron
Hi -
this shouldn’t have to anything with the 1.6.3 release. Do you encounter this also with other php-files? If possible, could you mail the offending php-file to me?
Another thing to check: Open the Terminal, enter “php -v” (without quotes) and return – what result do you get?
regards,
mario
Thanks for the fast reply!
I’ve tried it on multiple files, including nearly empty ones. ( fails) It might be that my php version is out of date? Does this work on php < 5?
aaron-mac:~ aaron$ php -v
PHP 4.4.9 (cli) (built: Sep 17 2008 14:54:01)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
Yes, php4 – that’s the problem. With php5 everything should work. Which OS X version do you use? In the current Leopard release php5 is included.
You can install a more recent php-version with MacPorts, but therefore you have to edit the path to php in the first line of the “phptidy-coda.php”-file.
Hope that helps.
Yes I’m on Tiger, that’s why. I’ll look into upgrading. Thanks again for your efforts and support on this plug-in.
Great plugin. Thanks.
[...] Coda PHP Plugin [...]
Thank you for contributing to the Coda community ! Using this plugin daily, saves me alot of time switching back between terminal windows!
Cheers !
Glad to hear that – as soon as the Coda-API offers some advanced functions, more features are to come..
This is awesome thank you!
Would it be possible to add a feature which lets you find an opening bracket’s closing bracket (and vice versa)? I know Coda has a feature which highlights them but its no use when there is lots of code between the brackets.!
Thanks :)
The bracket highlighting is at the moment not possible – for the Coda-API allows only a limited set of actions like replacing text, opening files etc., but no features like highlighting text.
Besides this would also be not easy writing such a feature (and doing it better than the Coda developers :)
Thanks for taking the time to do this, just starting to use PhP with Coda and this is a welcome resource!
Hey man, good work!
I’m not sure how you wrap your brain around this stuff, but keep it up!
Great script, works as advertised. Thank you!!!
Do you know how I could add a keyboard shortcut to run this?
Thanks,
Michael
Simply use the keyboard shortcuts in OS X System Preferences and add a new shortcut.. That’s the most easy solution I think.