flaxsearch / flaxcode

Automatically exported from code.google.com/p/flaxcode
4 stars 1 forks source link

FLAX mapping doesn't work #177

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Index some content with FLAX as the mapping
2. Search the content
3. Attempt to open the content using the link

What is the expected output? What do you see instead?

The link shown is just http://localhost:8090 or similar, no full link is
given This certainly used to work but something has changed!

Original issue reported on code.google.com by charliej...@gmail.com on 25 Jan 2008 at 1:18

GoogleCodeExporter commented 9 years ago
This actually only happens if you use the new Filebrowser, which generates a 
filespec
using forward slashes - it should probably use backslashes, or we should allow 
both
and translate them properly when making the source URL.

Original comment by charliej...@gmail.com on 25 Jan 2008 at 1:21

GoogleCodeExporter commented 9 years ago
I think the best solution is to allow both types of slashes in filenames 
submitted by
the collection properties form (since users can type into this box, and could 
use
either).  We should then transforming these slashes to store filespecs with 
system
specific file separators (ie, with os.sep).

That way, users can do whatever they like and it should work.

Original comment by boulton.rj@gmail.com on 25 Jan 2008 at 2:33

GoogleCodeExporter commented 9 years ago
Yes, agreed, even Windows users will use forward slashes occasionally.

Original comment by charliej...@gmail.com on 25 Jan 2008 at 3:22

GoogleCodeExporter commented 9 years ago
Fixed in 1.0.0.957 - forward slashes automatically change to backslashes when 
the
collection details are Applied

Original comment by charliej...@gmail.com on 25 Jan 2008 at 3:45