Hi eurohelmets - I’m sorry that the current settings do not allow you to use your full server path, but this is not a bug.  Feel free to post a Feature Request in the forums to have this modified.

Out of curiosity, what is the path you are trying to use?  I might be able to provide you with a workaround that will not require manually modifying your database.

I have a local setup for testing, so the path has gotten quite long.  I’m also trying to organise the upload directories, so I have paths like:

c:/web/Apache Software Foundation/Apache2.2/htdocs/expressionengine/images/uploads/<company name>/<blog name>/images

c:/web/Apache Software Foundation/Apache2.2/htdocs/expressionengine/images/uploads/<company name>/<blog name>/thumbs

These paths are too long.
Thanks for your help.

If I might make a recommendation, since this is a local server and you have complete control over the file structure, I would eliminate ‘Apache Software Foundation/Apache2.2’ in favor of just ‘apache’, and you can of course shorten or eliminate ‘expressionengine’ as well.  If that’s not acceptable, again, since this is a local development install, there would be little harm in modifying the database columns to allow 125 or 150 characters, whatever your needs may be.

In hosted environments, we have had only a couple people for whom 100 characters was too small for server path settings, and in those particular cases, I believe a .htaccess rewrite was implemented so that the public URL structure matched the lengthy version, but the files were stored in a much more simplified local structure.

Any of those three solutions should work for you.  Make sense?

Yes, thanks for all of your help.