Omar Rosales . 15 Years Ago Hi Brett,Do you know how configure the maximum file size in the version 5.2 Please sign in to reply. Reply as... Cancel Brett Swaim Omar Rosales . 15 Years Ago this is done in portal.properties. Take the portal.properties settings for the document library and add them to your portal-ext.properties file. Please sign in to reply. Reply as... Cancel
Brett Swaim Omar Rosales . 15 Years Ago this is done in portal.properties. Take the portal.properties settings for the document library and add them to your portal-ext.properties file. Please sign in to reply. Reply as... Cancel
RoK . 15 Years Ago Hi Brett,Nice new feature, but I have one comment. It is good to have general settings portal wide, but in practice these values will vary per community (or organisation). The platforms I used to work with could all configure this per community/group (or better: per portlet). Please sign in to reply. Reply as... Cancel Brett Swaim RoK . 15 Years Ago Hey RoK,You are absolutely right, and when I was implementing this my original intention was to make a global setting like I did here, as well as a community specific setting. Think of this as the first step to easier modification with plans to make it more granular as time goes on. The one thing I wasn't sure about was if I should make the setting on a per portlet basis, portal wide, system wide, or what. Would you feel that per community would be granular enough?Brett Please sign in to reply. Reply as... Cancel dan s Brett Swaim 15 Years Ago Hi,Where can i download 5.2.3? Please sign in to reply. Reply as... Cancel Brett Swaim dan s 15 Years Ago 5.2.3 hasn't been released yet, but you can always download the source code for Liferay and get a snapshot of what's coming up! Please sign in to reply. Reply as... Cancel Josh Asbury Brett Swaim 14 Years Ago Nice job, Brett. I was just getting ready to delve into changing some portal-companyID.properties files when I remembered this post. This is certainly very helpful since it gets pretty painful managing this kind of stuff across instances. To answer your questions, I think that type of stuff should be separated by communities/organizations (with different settings for public vs. private) and instances. Getting down into the thick of per-portlet settings might become cumbersome very quickly. Please sign in to reply. Reply as... Cancel Brett Swaim Josh Asbury 14 Years Ago Exactly what I was thinking. One of the pluses of working for Liferay is that I get to do core stuff for a while, then roll out to a project and get some more real world experience. Once I finish the project I'm on I'll get to narrowing this scope down. Please sign in to reply. Reply as... Cancel RoK . Brett Swaim 14 Years Ago Yes I think that per community is good enough for the time being... Please sign in to reply. Reply as... Cancel
Brett Swaim RoK . 15 Years Ago Hey RoK,You are absolutely right, and when I was implementing this my original intention was to make a global setting like I did here, as well as a community specific setting. Think of this as the first step to easier modification with plans to make it more granular as time goes on. The one thing I wasn't sure about was if I should make the setting on a per portlet basis, portal wide, system wide, or what. Would you feel that per community would be granular enough?Brett Please sign in to reply. Reply as... Cancel dan s Brett Swaim 15 Years Ago Hi,Where can i download 5.2.3? Please sign in to reply. Reply as... Cancel Brett Swaim dan s 15 Years Ago 5.2.3 hasn't been released yet, but you can always download the source code for Liferay and get a snapshot of what's coming up! Please sign in to reply. Reply as... Cancel Josh Asbury Brett Swaim 14 Years Ago Nice job, Brett. I was just getting ready to delve into changing some portal-companyID.properties files when I remembered this post. This is certainly very helpful since it gets pretty painful managing this kind of stuff across instances. To answer your questions, I think that type of stuff should be separated by communities/organizations (with different settings for public vs. private) and instances. Getting down into the thick of per-portlet settings might become cumbersome very quickly. Please sign in to reply. Reply as... Cancel Brett Swaim Josh Asbury 14 Years Ago Exactly what I was thinking. One of the pluses of working for Liferay is that I get to do core stuff for a while, then roll out to a project and get some more real world experience. Once I finish the project I'm on I'll get to narrowing this scope down. Please sign in to reply. Reply as... Cancel RoK . Brett Swaim 14 Years Ago Yes I think that per community is good enough for the time being... Please sign in to reply. Reply as... Cancel
dan s Brett Swaim 15 Years Ago Hi,Where can i download 5.2.3? Please sign in to reply. Reply as... Cancel Brett Swaim dan s 15 Years Ago 5.2.3 hasn't been released yet, but you can always download the source code for Liferay and get a snapshot of what's coming up! Please sign in to reply. Reply as... Cancel
Brett Swaim dan s 15 Years Ago 5.2.3 hasn't been released yet, but you can always download the source code for Liferay and get a snapshot of what's coming up! Please sign in to reply. Reply as... Cancel
Josh Asbury Brett Swaim 14 Years Ago Nice job, Brett. I was just getting ready to delve into changing some portal-companyID.properties files when I remembered this post. This is certainly very helpful since it gets pretty painful managing this kind of stuff across instances. To answer your questions, I think that type of stuff should be separated by communities/organizations (with different settings for public vs. private) and instances. Getting down into the thick of per-portlet settings might become cumbersome very quickly. Please sign in to reply. Reply as... Cancel Brett Swaim Josh Asbury 14 Years Ago Exactly what I was thinking. One of the pluses of working for Liferay is that I get to do core stuff for a while, then roll out to a project and get some more real world experience. Once I finish the project I'm on I'll get to narrowing this scope down. Please sign in to reply. Reply as... Cancel
Brett Swaim Josh Asbury 14 Years Ago Exactly what I was thinking. One of the pluses of working for Liferay is that I get to do core stuff for a while, then roll out to a project and get some more real world experience. Once I finish the project I'm on I'll get to narrowing this scope down. Please sign in to reply. Reply as... Cancel
RoK . Brett Swaim 14 Years Ago Yes I think that per community is good enough for the time being... Please sign in to reply. Reply as... Cancel
Claudio Patricio Rifo 14 Years Ago Hi there.. Congrats to all people working on the control pannel..i'm using it a lot under 5.2.3.Just some feedback.Everytime you speak about file size you shoud specifie on what unit must file size be.For instance MB GB KB, etc. Please sign in to reply. Reply as... Cancel
Kirk Stork 13 Years Ago Thanks for this info.I'm trying to adjust my portal to accept large files (250MB and up). These are video files.I'm on LR 6.0.5 CE, Tomcat 6, with the document library set to use Jackrabbit on the file system.I've adjusted, using the control panel as described above, the General and Document Library file sizes to4000000000Which I' believe should translate to about 4GB.But even at 250MB, I get "there was a problem" on the upload page, and a "exceeded file size" in the logs.You don't get this failure until you've waited the 30 or 40 minutes for the file to upload.Is there someplace other than this control panel setting that might be imposing a cap on my file size?Thanks Please sign in to reply. Reply as... Cancel Brett Swaim Kirk Stork 13 Years Ago It appears that we aren't checking in the database for a few file types, simply change this in your portal-ext.properties file: com.liferay.portal.upload.UploadServletRequestImpl.max.size=10485760000That should get you going. Please sign in to reply. Reply as... Cancel
Brett Swaim Kirk Stork 13 Years Ago It appears that we aren't checking in the database for a few file types, simply change this in your portal-ext.properties file: com.liferay.portal.upload.UploadServletRequestImpl.max.size=10485760000That should get you going. Please sign in to reply. Reply as... Cancel