Shared custom title issues

I share custom titles that I created with remote editors. It's purely preformatted text nothing fancy.

I have them install the titles in the exact same location/ path as I have the ones I created locally.

The issue is when they send me an xml of a cut, I get this error:



If they send me a library I can see the title in the timeline but when I highlight it and look in the inspector there is nothing under the text tab. I.e. the ability to format or change the text is missing. This ends up having me having to replace the title and do it over.

I've been banging my head against this for months and this is my first chance to reach out about it.

Hopefully it's something obvious I've overlooked.

Thanks!

Brian

Select the Library in the Browser.
Go to the Inspector.
Click Modify Setting button.
Change "Motion Content" to "In Library".
Click "OK".
In the Inspector, the Motion Content section, click the Consolidate button.
Breath...

Thanks for the suggestion.

I did everything you suggested and even breathed. No dice.

Just get this:



I also noticed that these titles are now greyed out (as if they are a gap clip but with the labeling you'd see on a title clip) and when I click on them and open the inspector it thinks they are generators.

Been pulling my hair out on this.

Brian

You may have to replace them with a fresh copy from the Title Browser. And not knowing exactly what title template you're using, can't really say much more.

I dug deeper into the xml from the project with the offending titles and compared it to the xml from my system's project that doesn't have problems.

It appears that in the file path /Titles.localized/Lower Thirds is missing the text .localized on the offending xml. When I add the missing text /Titles.localized/Lower Thirds.localized the titles now appear when importing the offending xml.

The big question now is: why?

I don't know enough about xml or fcpx to understand why that bit of text is missing from the offending xml.

.localized tells the operating system to treat that folder in a special way.

So the 1,000,000 dollar question is why does .localized get written to the xml on my end and not on the other end?