This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Symbolic links to directories cannot be accessed when run as remote web site | ||
---|---|---|---|
Product: | php | Reporter: | maxevron |
Component: | Project | Assignee: | Tomas Mysik <tmysik> |
Status: | REOPENED --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.2 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
maxevron
2012-08-29 08:47:26 UTC
that's something to be done on php support side (copying from remote location to local one) or platform/filesystem side which currently won't work with symbolic links and/or with remote content? what filesystem are we talking about on linux side? (In reply to comment #1) > that's something to be done on php support side (copying from remote location > to local one) or platform/filesystem side which currently won't work with > symbolic links and/or with remote content? what filesystem are we talking about > on linux side? No, this a problem with NetBeans file browser. When you are working on project located on a remote server and synchronized through Netbeans ftp/sftp component, when clicking on "Download..." from the contextual menu, the list of files and directories candidates to download are shown, including symbolic links to directories located on the remote end (the file system of the server contains these symbolic links to directories located on the file system of the server itself). The thing is that, even if these these symbolic links are shown and can be selected for download, when starting the download process these symbolic links are simply ignored. I would expect these remote symbolic links to be considered as if they were regular directories as it happens if you are on a shell on the server and you type "cd <symbolic link name>": you can enter this directory pointed by the symbolic link and then handle its files and sub-directories as if they were part of the file tree. If I understand correctly, this issue says that symbolic links are not downloaded from the remote server - is this correct? If yes, then it is OK because symbolic links *must* be ignored (otherwise they would be overwritten during the next upload). Thanks for reporting. I agree with you, symbolic links *must* be ignored (otherwise they would be overwritten during the next upload). But I mean symbolic links as symbolic links *must* be ignored, but the thing they represent *must not*. A symbolic link would be considered and handled *AS* a symbolic link and, thus, be used for what it is: a linkage to another part of the file system. As a result, a symbolic link to a directory stored server side should be *considered*, viewed, interpreted as a directory on client side, and thus its content downloaded and uploaded transparently. This is also true for symbolic links to files: it's the file linked by a symbolic link that should be considered on client side, not the symbolic link itself. Managing symbolic links themselves is out of the scope of Netbeans and devoted to administrative tasks run on the server, through a shell for example. Sorry, changing to enhancement since right now it works as designed. |