Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem with WAFileMetadataLibrary>>#deployFiles #735

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 2 comments
Closed

Problem with WAFileMetadataLibrary>>#deployFiles #735

GoogleCodeExporter opened this issue Mar 25, 2015 · 2 comments
Labels
auto-migrated FileLibrary Priority-Medium Type-Defect Version-Seaside3.1

Comments

@GoogleCodeExporter
Copy link 

If the filepath of a WAFileLibraryResource object does not contain a path 
separator ('/') then the file is deployed in the wrong place.

For example the file mystyle.css in MyLib is exported to 
'MyLib/mystyle.css/mystyle.css'.

The correct location should be 'MyLib/mystyle.css'.

Seaside version 3.0.7 on Pharo 1.4

Original issue reported on code.google.com by jvdsa...@gmail.com on 10 Aug 2012 at 2:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated FileLibrary Priority-Medium Type-Defect Version-Seaside3.1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter