Most applications have settings that, when combined, can confound both novice and expert users. This post is a running tally of things to check if (or when) your FrameMaker experience goes awry. It’s one of my pieces of cornerstone content. View the Cornerstone Content category to check out other key articles.
Updated Jan 29, 2020- added info on reusing preferences folder content
If FrameMaker suddenly acts in new and mysterious ways, you may have shuffled, reorganized, or closed one of the pods that FrameMaker uses to display settings and information. If so, resetting your workspace may restore expected pod locations. If not, you may also have a corrupted preferences file. Follow the procedures below to see if either of these things will remedy your problem.
Resetting your Workspace
When moving quickly in FrameMaker, pods can often get stacked on top of each other, making it difficult to locate that one pod you really need. To put things back in their expected location, choose a workspace you know, and also choose the Reset Workspace option. Here’s a hot tip: This feature is especially helpful if you’ve saved one or more workspaces for your own work. In my case, the Auth Course workspace is what I enable and reset whenever I’m teaching Structured FrameMaker Authoring. Other times, I switch to the Blank workspace for when I record FrameMaker screencasts or just want a decluttered screen.
Creating a clean Preferences folder
Changing the name of your preferences folder (which forces FrameMaker to write a new preferences folder) is an easy way to check for a corrupted preferences file.
Follow the instructions below to locate the folder, and then change the name of the prefs folder to 14-old, or something similar to see if it resolves your interface issue. If the issue remains, it only takes a minute to delete the new folder, rename the old folder, and restart FrameMaker. You’ll be no worse for having done so.
Recovering workspaces or other things from the previous Preferences folder
In the interest of time and effort, the renamed Preferences folder contains a number of resources that you might want to reuse after creating a new Preferences folder.
Specifically, information about the following may be useful:
- customized Welcome Screen
- customized non-HTML5 output skins
- may exist if you run plugins that load upon startup (mine are usually from Rick Quatro)
- Contains custom pod locations and menu visibility. These can also be passed across machines to help ensure a consistent editing environment.
- customizations to DITA output from Fm
- A massive dumping ground for preferences within the application. I also suspect this is often the file that corrupts and thus requires recreation, so (re)use with caution.
- contains the user-specific definitions for customizations to Structured Applications, the rules that allow you to create structured content.
You are free to copy the older information into your newly minted prefs folder, but (of course) if the assets you are moving are the ones that corrupted your folder, you’ll simply be reintroducing the corruption into your new preferences. Does that make sense?!
Locating the Preferences folder
Ever since Windows 7, I’ve been annoyed at the location of preference and other files used by applications.
You might already know where they’re at, but generally speaking, they’re stored in a somewhat obscure location, similar to this:
C:\Users\USERNAME\AppData\Roaming, where USERNAME is the username you use to log into your PC.
That’s great, but I still get annoyed at shuffling up and down directories whenever I need to access it. As a result I long ago discovered that if I added that Roaming directory to my Favorites in Windows Explorer, things were a bit easier.
However, if you like memorization, or writing things down, there’s an even easier way. Just type (or paste) %appdata% or something more specific, like %appdata%\Adobe\FrameMaker\14 into the Explorer bar and you’ll jump straight to your needed location.
Here’s a short video to show how it works.
My thanks to Stefan Gentz, Adobe’s TCS Evangelist for posting this string in an Adobe forum.
Did this help you out?
Join the free Tech Comm Tools community and I'll give you a heads-up whenever I've got more content like this that you might like.