Skip to content
This repository

Name collisions are causing not all files to be copied #205

Closed
eliasdawson opened this Issue May 09, 2012 · 4 comments

2 participants

Elias Dawson Benjamin Arthur Lupton
Elias Dawson

I'm working on converting a site to use DocPad as an experiment and I've discovered that several files are silently ignored when generating. Some files of the same type are copied, but others are not. Problem extensions seem to be .svg, .ttf, .eot, and .otf. If there isn't some processing specified for a file, shouldn't it just be copied?

Benjamin Arthur Lupton
Owner

Hrmmm, those extensions should work. Can you provide me with access to the repository that you're working on, and I'll try and figure out what's going fishy.

If there isn't some processing specified for a file, shouldn't it just be copied?

For a little background, there are several patterns that DocPad should always ignore, the land of filesystems is very convoluted in this way. For instance certain operating systems and editors will often like to create several different types of cache files inside a directory that we always want to ignore. Also things like .svn folders we do not want to copy over, as they are specify to that path, and not the output path - will cause a corrupt svn repository. However, it doesn't seem like this would be related to this issue.

Elias Dawson

That makes a lot of sense., and I should say I really like DocPad. I've been experimenting with several Static Site Generators and it's my favorite so far.

I can't share the repository since it's for work, but I did some more testing, and I'm convinced it's actually a name collision. If I have multiple font or image files with the same name and different extensions, only one is copied. This issue didn't occur in previous versions when using the public directory.

I think it's related to #Num: #190, and I would cast a vote for going back to not processing the public directory. I think it's probably the case that there will always be some situation where a user would want some files ignored and copied verbatim. It's a good safety net and adds flexibility. For example it offers a work-around for Issue #Num: #192.

Benjamin Arthur Lupton
Owner

Name collision problem fixed in the just released 5.2.2.

Benjamin Arthur Lupton balupton closed this May 17, 2012
Benjamin Arthur Lupton balupton referenced this issue from a commit May 17, 2012
Benjamin Arthur Lupton v5.2.2. Bug fixes.
- v5.2.2 May 17, 2012
	- Fixed [#208](#208) - Multiple
file extensions being trimmed
	- Fixed [#205](#205) - Name
collisions are causing not all files to be copied
	- Changed file `id` to default to the `relativePath` instead of the
`relativeBase`
	- Finding layouts now uses `id: $startsWith: layoutId` instead of `id:
layoutId`
588e40a
Elias Dawson

Finally got back to this and it's working as expected. Thanks.

Benjamin Arthur Lupton balupton referenced this issue from a commit May 17, 2012
Benjamin Arthur Lupton v5.2.2. Bug fixes.
- v5.2.2 May 17, 2012
	- Fixed [#208](#208) - Multiple
file extensions being trimmed
	- Fixed [#205](#205) - Name
collisions are causing not all files to be copied
	- Changed file `id` to default to the `relativePath` instead of the
`relativeBase`
	- Finding layouts now uses `id: $startsWith: layoutId` instead of `id:
layoutId`
565c1f5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.