ICEfaces
  1. ICEfaces
  2. ICE-1611

<ice:inputFile/> does not create a session-specific folder for the uploaded file

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.6DR#4
          • Fix Version/s: 1.6DR#5, 1.6
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            Tomcat 5.5.17 / Liferay 4.3.0 (pre-release)

            Description

            The attached portlet requires a C:\Uploads folder (as specified in web.xml)

            When the file is uploaded, it goes right into C:\Uploads, unlike ICEfaces 1.5.3, which would create a unique sub-folder based on the sessionid, something like this: C:\Uploads\asdf123421


            Neil

              Issue Links

              blocks

              New Feature - A new feature of the product, which has yet to be developed. ICE-1809 Support for Liferay Portal

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                Adnan Durrani added a comment -

                It came across that, even if you set the uniqueFolder="true" on inputFile component, it still does not create a unqiueFolder.

                Show
                Adnan Durrani added a comment - It came across that, even if you set the uniqueFolder="true" on inputFile component, it still does not create a unqiueFolder.
                Hide
                Permalink
                Neil Griffin added a comment -

                Adnan,

                Is the "uniqueFolder" attribute new for 1.6? I can't say for sure, but I think the creation of a unique folder was true by default in 1.5.3. If I have to specify "uniqueFolder" = true in the component, that's OK too. But I was just curious.

                Neil

                Show
                Neil Griffin added a comment - Adnan, Is the "uniqueFolder" attribute new for 1.6? I can't say for sure, but I think the creation of a unique folder was true by default in 1.5.3. If I have to specify "uniqueFolder" = true in the component, that's OK too. But I was just curious. Neil
                Hide
                Permalink
                Adnan Durrani added a comment -

                Neil your findings are right. The uniqueFolder attribute was in 1.5.3 and by default it was true but with 1.6.x it is not implemented completely. so even if you specify "uniqueFolder" = true in the component, it still won't work. So I am going to fix it.

                Show
                Adnan Durrani added a comment - Neil your findings are right. The uniqueFolder attribute was in 1.5.3 and by default it was true but with 1.6.x it is not implemented completely. so even if you specify "uniqueFolder" = true in the component, it still won't work. So I am going to fix it.
                Hide
                Permalink
                Adnan Durrani added a comment -

                uniqueFolder functionality implemented completely. The default value is set to true. The Meta data has been updated as well. revision 13953

                Show
                Adnan Durrani added a comment - uniqueFolder functionality implemented completely. The default value is set to true. The Meta data has been updated as well. revision 13953

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    Neil Griffin
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: