Coda 2 does not recognize .css file change for publishing

[maka-io]

Hi,

I noticed that Coda 2 does not recognize when the css file generated has been updated after saving the scss file. This makes it difficult when using the publish feature, as I can publish the scss file but have to manually file transfer my new generated css file.

Is there a setting?

Thanks!

[keegnotrub]

Thanks for the feedback. This is an issue with Coda 2, I believe Panic is working on an update. Until that lands I'll leave this issue open.

In the meantime, there is a way around it if you open the generated CSS file inside of Coda it will notice it has changed for publishing.

See http://hicksdesign.co.uk/journal/detecting-compiled-css-changes-with-coda-2

[keegnotrub]

I'll look into using - (NSString*)willPublishFileAtPath:(NSString*)inputPath; for this.

[keegnotrub]

@FBRTMaka - I was able to confirm this is now addressed in Coda v2.5. Closing this issue for now but if you have any more problems just respond to reopen.

[jodinathan]

Hi,

It is happening again. Coda stopped checking for local changed files outside the editor. :(

[Rayken]

Status?

[keegnotrub]

I'm trying to carve out some free time to test these. Just to confirm, this issue was closed but it reappeared sometime after v2.5 correct?

Also, the following doesn't fix the problem right?

http://hicksdesign.co.uk/journal/detecting-compiled-css-changes-with-coda-2

[Rayken]

Don't know when. It's not a fix though it's a work-around and it requires you to work with the publish feature - you can't simply connect to a remote server, go to your CSS folder and make a style.scss and start coding without a lot of tinkering.. On Feb 2, 2016 14:40, "Ryan Krug" notifications@github.com wrote:

I'm trying to carve out some free time to test these. Just to confirm, this issue was closed but it reappeared sometime after v2.5 correct?

Also, the following doesn't fix the problem right?

http://hicksdesign.co.uk/journal/detecting-compiled-css-changes-with-coda-2

— Reply to this email directly or view it on GitHub https://github.com/keegnotrub/coda-sass-plugin/issues/4#issuecomment-178577461 .

[keegnotrub]

Thanks @Quaked - I believe then this issue might not be the correct one to re-open as it deals with publishing. Perhaps #29 is more appropriate? I'll close this issue for now but let me know if that isn't correct.

[mattyfew]

I've been having this problem with Coda for a while now. One instance it works fine, the next it does not. I've tried everything. What gives?

[Warkman]

Im using 2.6.1 and it has just stared with this problem. On some sites it recognises the changes and ques for publishing then on other sites it does not pick up the changes? What do to Coda?

[padcreative]

I have this problem as well. It's intermittent. Sometimes Coda recognises the file sometimes not. I think this might be a Coda issue rather than an issue with the plugin. Sometimes if I change an image with Photoshop it doesn't queue it for Publishing and sometimes it does.

Can always ctrl-click on the css file and publish manually but it's far better when queued!

[padcreative]

Just to update, my problem with the files not queuing for publishing is due to the time on the saved files being in the past when compared with the versions on the live server. This is because our local Mac server's clock sometimes runs slow. When I look at the Mac server via a shared screen, you can see the time is a few mins late. By virtue of sharing the screen, it tends to then bring the clock back to the right time. There is a way to keep the clock in sync, but I haven't bothered to sort it out yet. I know that when I save my SCSS files, the compiled CSS file will be updated so I can just manually publish it if it's not queuing.

I hope that helps other people in the same situation – ie. if you work off a Mac server rather than your own computer, this could well be the issue.