Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
douglsmith
6 months agoNew Contributor
MrC Converter Suite error and question
I'm trying out MrC's Converter Suite for the first time. Thanks for sharing your work on this great tool! Here is the command line I'm using: perl convert.pl onepux --verbose --to_format csv --pe...
douglsmith
6 months agoNew Contributor
Using --debug, hundreds of records show things like the examples below that are missing a field name. The xxxxxxxxxxxx represents what is usually a copy of the password for the record. When I look up those records in 1Passwords, sometimes I see autosaved web details that include the data from those rows, but not always.
add_fv_pair : field: = Login
add_fv_pair : field: = xxxxxxxxxxxx
MrC
6 months agoSuper Contributor
Ok, thanks for confirming. Now comes the hard part since I have no idea how to reproduce this. So I'll have to ask questions...
- When you look at one such record in 1Password, do field labels exist where they don't in the --debug output?
- If you enable 1Password's Settings > Advanced > Show debug tools, and then right-click an offending record and Copy item JSON, and paste the copy into a plain text editor, do you see field labels whereas you don't in the --debug output? I'll explain below what to look for.
- Were these records created by way of another password manager's export, which were then imported into 1Password?
- Are you be able to create a temporary vault and reproduce the issue with a new Login record in that vault?
- If you can't reproduce the problem with a new record, can you reproduce it with a copy of a problematic record stored in the temporary vault?
- If you can reproduce the issue with either (3) or (4), would you be willing to send me a sanitized version of the record as JSON. If you don't know how to do this, I explain below.
Each record has an array (list) of sections, and each section has an array of fields. Each field should have a title attribute (the field's title or label). If you've not provided a title when you created the field, it will appear blank in 1Password, but should have a generic name based on the type of the field. The yellow arrows below show two such custom fields, whereas the title attribute where I provided a label (red arrow) shows its label.
Login records also have two additional legacy "fields" contained in a different structure. These are in the loginFields array. There are usually two entries, one for the username, one for the password (and these are indicated by the fieldType and/or designation, and typically these have the name attribute of username and password, respectively:
Here's the complete sample Login record:
{
"uuid": "vxch6x3iyj2jcj7tyl6jkxirza",
"favIndex": 0,
"createdAt": 1749225554,
"updatedAt": 1750690632,
"state": "active",
"categoryUuid": "001",
"details": {
"loginFields": [
{
"value": "password3",
"id": "",
"name": "password",
"fieldType": "P",
"designation": "password"
},
{
"value": "user3",
"id": "",
"name": "username",
"fieldType": "T",
"designation": "username"
}
],
"notesPlain": "what is the meaning of life?\nSuper Dooper Party Pooper\nè ÿ æ Ą Ǝ Dž Ƙ\nEND",
"sections": [
{
"title": "",
"name": "add more",
"fields": [
{
"title": "a custom text field",
"id": "xyy2zu2wcsjw6k6mcshaxbkdga",
"value": {
"string": "value 1"
},
"guarded": false,
"multiline": true,
"dontGenerate": false,
"inputTraits": {
"keyboard": "default",
"correction": "no",
"capitalization": "sentences"
}
},
{
"title": "text",
"id": "sruswjp2vduqe5ftkqyy2f636i",
"value": {
"string": "value 2 for empty label custom field 1"
},
"guarded": false,
"multiline": true,
"dontGenerate": false,
"inputTraits": {
"keyboard": "default",
"correction": "no",
"capitalization": "sentences"
}
},
{
"title": "text",
"id": "w23zcb4l7xsjbzywuyvzlxbpf4",
"value": {
"string": "value 3 for empty label custom field 2"
},
"guarded": false,
"multiline": true,
"dontGenerate": false,
"inputTraits": {
"keyboard": "default",
"correction": "no",
"capitalization": "sentences"
}
}
]
}
],
"passwordHistory": []
},
"overview": {
"subtitle": "user3",
"icons": null,
"urls": [
{
"label": "website",
"url": "http://mail.example.com/",
"mode": "default"
}
],
"title": "Web Account with 3 links (user3)",
"url": "http://mail.example.com/",
"watchtowerExclusions": null
}
},Ultimately, we're looking for fields that have no values for the title attribute within the 1PUX's data.
To view the raw 1PUX data, make a copy, change the suffix from .1pux to .zip, and then expand that zip. Inside there's an export.data text file. That's the contents of your vault's data, minus the file exports stored in the files folder, and metadata stored in the export.attributes file. View the export.data with a plain text editor.
Hopefully you are able to detect some pattern, or the answers to my questions help me reproduce the issue.