Import RDF fails #201
-
|
I was using PasswordMaker Pro from there. I disabled the other PasswordMaker Pro extension, and installed the one from here. Why can't I import my profiles from the RDF file? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Are you able to import this file into the old PasswordMaker Pro from which it was exported? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I can import it in the old Passwordmaker Pro. |
Beta Was this translation helpful? Give feedback.
-
|
@gwillegers I have tried exporting from dolohow's branch and importing was successful for me. Do you see any errors in the F12 developer console after you open it while on the options page after trying to import your profiles that you can include here? If you want, you could email me your profiles .rdf file, I'll try importing your profiles and see if I get the same problem you are having on your end. [email protected] is my email if you'd like to send that to me to do some debugging or see if it works for me. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the tip to check the console. It shows the following error message (my translation, because it is in Dutch):
At the right of the console there is a link ooptions.html:5296:22.
Column 22 is the h of http. If I remove that line and try to import again, the message remains the same. At the time of import, there are two profiles: Default and Alphanumeric. Checking "Delete all profiles, then iimport" does not change the result. I made a copy of the RDF, and removed all profiles, except the first one. I also removed the line referring to the defaults (line 5296 in the first quote). Now the error message refers to line 40, column 22.
I manually added a profile to the new PasswordMaker Pro, and created an export. I then imported that, which worked fine. Then I noticed a difference. In the RDF:Seq section, the RDF:Resource attribute has quotes around the value in the new PasswordMaker Pro. In the old one there are no quotes (as can be seen in my quotes above). So I guess I have to edit 248 RDF:Resource attributes.... |
Beta Was this translation helpful? Give feedback.
-
|
Hmm interesting, I suppose by fixing a bug in the old one I introduced a new one. Until I have a fix made for importing, you may be able to do a simple "Search & Replace All" in any editor of your choice to replace any things that cause a problem without quotes instead of manually adding quotes to each malformed line of XML from the older extension. |
Beta Was this translation helpful? Give feedback.
-
|
Also @gwillegers, if you wanted, you could paste your entire profile .rdf into https://jsonformatter.org/xml-validator or https://onlinexmltools.com/validate-xml or https://xmlable.com/validator/ to get where the errors actually occurred in that file to fix them. So just make sure between each = and /> there is a string in quotes or double-quotes. After your profile data xml/rdf data checks as valid, then try to import. A hint for the https://jsonformatter.org/xml-validator you can hold alt + click and drag down to vertically edit right after the = sign to edit every line selected vertically to easily add a quote to each profile line all at once, and can also do it for the closing string quote as well before the closing xml tag |
Beta Was this translation helpful? Give feedback.
-
|
Glad you were able to import @gwillegers :) |
Beta Was this translation helpful? Give feedback.
Hmm interesting, I suppose by fixing a bug in the old one I introduced a new one. Until I have a fix made for importing, you may be able to do a simple "Search & Replace All" in any editor of your choice to replace any things that cause a problem without quotes instead of manually adding quotes to each malformed line of XML from the older extension.