PDF-ShellTools > Bug reports

Custom fields

<< < (3/4) > >>

Lisbeth:
I'm using Windows 8. I rebuild the index - but it didn't help.

RTT:

--- Quote ---I'm using Windows 8.
--- End quote ---
32 or 64 bits?
In here, Windows 8 64-bit, it is working just fine.

Do the fields show in the details pane and file properties details tab? If yes, can you edit these fields on these file details panes?

If you have not done so, reboot windows, or better, if you know how to use the task manager, restart the Windows Explorer that will also restart the shell extensions. All this is not usually needed, but better try it.

Lisbeth:
I'm using the 64 bit. I can see and change the properties in PDF Explorer. I can see the columns in Windows Explorer but not the content. I cannot see the properties, when I right-click on the file it self. I use a Danish version of Explorer, so I tried to name the columns with and English name, but that didn't help either. I have booted my laptop and restartet Windows Explorer, that didn't help either.

RTT:
Send me one of these PDFs edited in PDF Explorer, with these custom fields filled, so I can check how are you defining the custom fields.
Run also this tool STRegKeysChecker.zip and send me the text that will show, so I can inspect your system PDF-ShellTools related settings.

RTT:
I received your sample PDF, and the diagnostics tool output, and the most evident error is that you have the custom fields differently named in the PDF and in the PDF-ShellTools configuration. I suppose you used PDF Explorer to create the fields, and in PDF-ShellTools you also created the fields manually, instead of importing them.
What happens is that PDFE uses PDFECustomX as default name for the fields, and PDF-ShellTools uses PDFCustomX, so PDF-ShellTools is trying to read different fields from your PDFs.

To fix it, open the PDF-ShellTools manager and change the names to PDFECustomX. See first attached image.

This change field name operation, if done from the basic custom fields settings editor (don't happen if done from the advanced settings editor), will make the fields mapping to still refer the old name (due to a bug that will be fixed in the next release), so you also need to change the field label or use the mapping tab to map the field to another system defined property. In your case it's even what you should do, because one of your custom fields is named Kommentarer and the Windows property system already has a "comments" property defined, used by files that natively have this metadata field, such as MS Office documents.
So, let's map your Kommentarer field to the system.comments property. This way you can have the column comments showing metadata from PDFs, along with other file types that also populate this field.
Just use the property handler mapping tab to map your field to the system.comment one (check second attached screenshot for better reference).

The label of the system field may be different (than "Comments" as in the screenshot) if your Windows UI uses a different language The important is to find the property with System.Comment as the [canonical name].
Now check under the details pane items tab if the fields are still checked, and apply the changes.

When setting the Kommentarer field as visible column in Windows Explorer, and if your Windows UI language is also Danish, you may have two fields named kommentarer (I have no idea if the Danish Windows uses "kommentarer" for the system.comment property). If that's the case, the only way to know the correct one is to make visible the two and check the one that shows also the comments for MS office files too. In this situations it is better to label the custom fields with a different name, such as "PDF kommentarer", so you can better distinguish your fields from the system ones.

Navigation

[0] Message Index

[#] Next page

[*] Previous page