These are chat archives for locomotivecms/v3

28th
Mar 2016
scoobyclub
@scoobyclub
Mar 28 2016 13:18
OK. somethings more are more concrete now.
persisting images/home_3.jpg [skip] persisting images/logos/HRS Logo3.png [failed] Resource invalid: local_path is already taken Resource invalid: local_path is already taken
This message seems to appear when the filename has a space in it and stops the deployment process. This may be an undocumented feature ( or at least one that I haven’t come across yet ). If it is that then the error message is wrong. If it should handle spaces then it is a bug. IMHO.
persisting stylesheets/application.css [skip] persisting stylesheets/application.css [skip]
This message is shown when I have an application.css and an application.scss in the public/stylesheets directory. For some reason the same name is used twice. This seems to cause the ‘Local Path already taken error’ when the site is new but is ok after as both files are skipped.
scoobyclub
@scoobyclub
Mar 28 2016 13:25
Some of my other confusion seems to be due to old, partial and outdated data lying around in the sites folder. Not sure where it came from but I got rid of it and it was easier to see what was going on. That and putting the sites directory into Git.
I am now putting pre-compile files outside of public directory and using codekit to compile them in. This is probably cleaner and better practice anyway.
Ted Sherwood
@dustb0wl
Mar 28 2016 19:49

For what its worth, I am seeing the same error with an image that does not have spaces in the name

'# Error description: Resource invalid: local_path is already taken'

scoobyclub
@scoobyclub
Mar 28 2016 22:01
@dustb0wl There was a problem with that in Wagon 2.0.0 I think which I had reported and Did fixed in 2.0.1 I think. Are you running the latest?
Ted Sherwood
@dustb0wl
Mar 28 2016 22:03
running 2.1.0.rc4 on the site in question
@scoobyclub only happens on the one image oddly enough
scoobyclub
@scoobyclub
Mar 28 2016 22:11

Hmm. I have been having quite a number of issues with Wagon. Some of them probably self inflicted but some not.

When I got the bug the first time I traced it down to a line in the push_theme_assets (?) command where it was a checksum for the file that wasn’t picking up a change properly. Did put in a fix, can’t remember if it was proved fixed though.