OSX sometimes places 31 character limit on file names. How can I get this error to stop?

Question

OSX sometimes places 31 character limit on file names. How can I get this error to stop?

This error notice doesn't make sense, since many of my file names exceed 31 char. This error message pops up when saving documents, esp. web pages. As a consequence, OSX will refuse to let me save the file, until I shorten the name and so remove informative identifying features of the file name. But most of the time, OSX is perfectly happy to save files with names longer than 31 char. How can I get this error notice and block to turn off?

MacBook Pro, Mac OS X (10.7.2)

Posted on Sep 3, 2014 9:48 AM

Reply

Answer 1

Linc Davis

Level 10

209,547 points

Sep 3, 2014 12:41 PM in response to Richard Kapit

Please post a screenshot that shows what you mean. Be careful not to include any private information.

Start a reply to this message. Drag the image file into the editing window to upload it. You can also include text in the reply.

Reply

Answer 2

Sep 5, 2014 12:05 PM in response to Linc Davis

Linc, I've been unsuccessful in trying to duplicate the problem. It is one that has cropped up dozens and dozens of times over a number of years. But next time it happens, I'll take note of the particular conditions under which it occurs. I thought it occurred when I tried to save a web page, or print/save a web page, as a pdf file. But I tried both those things, with a name that was longer than 31 characters, and it didn't happen. If it happens again during the next couple of days, I'll send you another reply with a screen shot.

Reply

Answer 3

Kikage

Level 1

0 points

Sep 7, 2014 6:35 PM in response to Richard Kapit

I have also seen this issue it occurs regularly when transferring word documents files from my Macbook Pro running OSX 10.5.8 to my iMac running 10.9.4.

My iMac HD should be formatted to factory standards as well since I have not mucked around with it since I bought it.

Reply

Answer 4

SGF01

Level 1

4 points

Sep 8, 2014 8:46 AM in response to Kikage

I am also getting the same problem. Today is the first time I experienced it since using my MacBook Pro for the last 2 years. I get the same error message as posted by Kikage when trying to save an email from Mail onto the internal HD. The strange thing is that the same HD location contains several files with names longer than 31 characters that I had saved myself prior to commencement of this problem. Any ideas how to resolve this issue would be greatly appreciated.

Reply

Answer 5

Sep 9, 2014 6:29 AM in response to Linc Davis

Hi Linc! It happened again. Here is the screenshot

Reply

Answer 6

Linc Davis

Level 10

209,547 points

Sep 9, 2014 7:00 AM in response to Richard Kapit

Are you sharing the folder via SMB? AFP?

Reply

Answer 7

Sep 9, 2014 8:35 AM in response to Linc Davis

I have a home network. Two Macbooks share folders.

Reply

Answer 8

Linc Davis

Level 10

209,547 points

Sep 9, 2014 8:46 AM in response to Richard Kapit

Turn off file sharing and see whether there's any change.

Reply

Answer 9

Sep 10, 2014 11:57 AM in response to Linc Davis

Before I try this, Linc, please tell me, is file sharing being on necessary to transfer files between the two Macbooks? I use both machines constantly, and if I was unable to share files between them, I would rather live by the 31 character limit.

Reply

Answer 10

Linc Davis

Level 10

209,547 points

Sep 10, 2014 12:11 PM in response to Richard Kapit

is file sharing being on necessary to transfer files between the two Macbooks?

On at least one of them, yes. I'm suggesting a test. You can turn it back on afterwards.

Reply

Answer 11

frankxiv

Level 2

458 points

Jun 3, 2015 7:41 AM in response to Richard Kapit

This is happening to me with OmniOutliner when I try to save something to the OmniPresence folder. The strange thing is that I am able to save the document as Untitled if I save it at the root Document folder. I am also able to save files from other programs in the OmniPresence folder. I have been trying to chase this bug with the OmniGroup for months and they have no answer for me. They do not think it is anything on their side and in fact, they pointed me to this thread to show that other people are having the same issue with other apps.

Reply