Smalltalk › Frameworks & Tools › Seaside › Seaside General

Maybe a FileReference bug?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

JupiterJones

Maybe a FileReference bug?

Hi All,

I've got Pier3, seaside 3.0.8(9?) running in Pharo 2 and have an issue with FileUpload.

The issue appear to be in FileReference resolveString:

resolveString: aString

| thePath |

thePath := filesystem pathFromString: aString.

^ filesystem referenceTo: (path resolve: thePath)

aString is 'image.png', aFileReference path is the full path to the file:

eg.

/home/jupiter/image.png

however (path resolve: thePath) returns:

/home/jupiter/image.png/image.png

I think I may have an issue with the packages loaded since I also needed to chance a bunch of deprecated #pathName to #fullName. I kinda expected this in the Pier classes since I don't think it's ready for 2 (just guessing).

I also noticed that I have the FileSystem-Legacy package loaded and saw a comment about it being needed for seaside 3.0.x in Pharo2… which is what I'm running. Haven't looked deep enough to work it out yet, but wanted to ask if I'm running in circles with the wrong versions of things before I continue.

Any advice?

Thanks in advance.

Cheers,

Jupiter

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

DiegoLont

Re: Maybe a FileReference bug?

Hi Jupiter,

I recently fixed Pier3 to use Seaside 3.1 as it uses some functionality of Seaside 3.1. I do not know if Seaside 3.1 is already released, but I think it is stable enough, so I advice you to upgrade to Seaside 3.1 and then check if you still have these issues.

Cheers,

Diego

Hi All,

I've got Pier3, seaside 3.0.8(9?) running in Pharo 2 and have an issue with FileUpload.

The issue appear to be in FileReference resolveString:

resolveString: aString
| thePath |
thePath := filesystem pathFromString: aString.
^ filesystem referenceTo: (path resolve: thePath)

aString is 'image.png', aFileReference path is the full path to the file:

eg.
/home/jupiter/image.png

however (path resolve: thePath) returns:

/home/jupiter/image.png/image.png

I think I may have an issue with the packages loaded since I also needed to chance a bunch of deprecated #pathName to #fullName. I kinda expected this in the Pier classes since I don't think it's ready for 2 (just guessing).

I also noticed that I have the FileSystem-Legacy package loaded and saw a comment about it being needed for seaside 3.0.x in Pharo2… which is what I'm running. Haven't looked deep enough to work it out yet, but wanted to ask if I'm running in circles with the wrong versions of things before I continue.

Any advice?

Thanks in advance.

Cheers,

Jupiter
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside