adobe-dmeservices / custom-metadata

The home for a Custom Metadata Panel extension for Creative Cloud
https://exchange.adobe.com/creativecloud.details.103752.html
17 stars 8 forks source link

TypeError: i.substring is not a function #23

Closed matt77vinyl closed 1 year ago

matt77vinyl commented 2 years ago

Experiencing a reproducible error, occurs when I click on what so far seems to be one particular pdf in the content tab, leads immediately to red alert "something went wrong" appearing in the custom metadata panel --- the copy function from the error shows "TypeError: i.substring is not a function". I thereafter cannot utilize the custom metadata panel (it's completely empty) for any pdfs, until I reopen Bridge (using v12.0.1 btw on OS Big Sur), but then recurs each time I select the particular pdf. I deleted the offending pdf and made a new version of it, but after some time where it does allow me to enter metadata like usual, the error recurs. I tried purging all cache which did nothing.

thanks in advance for any suggestions. Matt

jameslockman commented 2 years ago

Can you please share a file that exhibits this behavior? Can you share what version of the panel you’re using?

-- James Lockman Senior Manager, Digital Media Services Adobe @.**@.> (917) 284-2268 Mobile Sent from his iPhone

On Apr 19, 2022, at 11:28 PM, matt77vinyl @.***> wrote:



Experiencing a reproducible error, occurs when I click on what so far seems to be one particular pdf in the content tab, leads immediately to red alert "something went wrong" appearing in the custom metadata panel --- the copy function from the error shows "TypeError: i.substring is not a function". I thereafter cannot utilize the custom metadata panel (it's completely empty) for any pdfs, until I reopen Bridge (using v12.0.1 btw on OS Big Sur), but then recurs each time I select the particular pdf. I deleted the offending pdf and made a new version of it, but after some time where it does allow me to enter metadata like usual, the error recurs. I tried purging all cache which did nothing.

thanks in advance for any suggestions. Matt

— Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fadobe-dmeservices%2Fcustom-metadata%2Fissues%2F23&data=05%7C01%7Cjlockman%40adobe.com%7Cbff989a8d13840c0bd6308da227dc7cc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637860220888539367%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p2xW72rk18AebeX2e%2FGgnDXucNQyxjQ89TAfK%2F58Tsk%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAUJHGLJCZWEHA2CZ24SSZTVF52UFANCNFSM5T2VROMA&data=05%7C01%7Cjlockman%40adobe.com%7Cbff989a8d13840c0bd6308da227dc7cc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637860220888695604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HUhcKBBTdESi1k4%2BplTrEVvGUgF2MDl8PTU7FBhc5EM%3D&reserved=0. You are receiving this because you are subscribed to this thread.Message ID: @.***>

matt77vinyl commented 2 years ago

thank you -- panel version 1.5.0 file attached (I had to compress/resize for upload. mwd0000000002smaller.pdf

bhunut-adobe commented 2 years ago

@matt77vinyl Can you provide us with the exported JSON of the metadata view? I'm unable to replicate this issue so far and wondering if it specific to reading a particular field that is throwing this error.

matt77vinyl commented 2 years ago

thank you --- I haven't traced it to one field yet, but it does seem to allow me to do some metadata editing for awhile before the error recurs. I'll do a few more trials to see if I can pinpoint a field.
Attaching JSON share.json.zip .

matt77vinyl commented 2 years ago

after more testing, I did find that it's when I enter data into my field for "event date" that the error occurs. Is there something I can change to allow that field to work?

bhunut-adobe commented 1 year ago

@matt77vinyl Sorry for the late response. I look deeper into this. At the moment, our date field doesn't support "Array of Date." We will add this as a priority to do for the next major release.

image
<dc:date>
  <rdf:Seq>
     <rdf:li>1978-06-02T17:00:00.000Z</rdf:li>
  </rdf:Seq>
</dc:date>

As a workaround, I recommend you change DC:Date to the MultiText field instead. You won't have Date Parsing, but it should allow you to read and modify this field.

image

See attached for modified JSON of the change. share 3.json.zip

jameslockman commented 1 year ago

Closed by 1.7.0 release, which adds Multi Date field.