#595 EndNote export broken with cutom fields

[Stéphane Aulery]

I tested with 3 resources from the test db and the Endnot export fails because $customArray is a string, not an array.

Fatal error: Uncaught TypeError: Cannot access offset of type string on string in C:\devel\www\wikindx\core\modules\export\ENDNOTEEXPORT.php:376 Stack trace: #0 C:\devel\www\wikindx\core\modules\export\ENDNOTEEXPORT.php(96): ENDNOTEEXPORT->getData() #1 C:\devel\www\wikindx\index.php(156): ENDNOTEEXPORT->process() #2 {main} thrown in C:\devel\www\wikindx\core\modules\export\ENDNOTEEXPORT.php on line 376

[Stéphane Aulery]

Hi mark,

I tried to fix the EndNote export and succeded by changing BIBCITEGATEWAY->getResourcesCustom() and ENDNOTEXPORT->getData().

The array was not cleanely build by BIBCITEGATEWAY->getResourcesCustom(). But since BIBCITEGATEWAY is central I'm concerned I could have broken some code.

Regards,

[Mark Grimshaw]

I've tested with a new style using both types of custom field and the resource displays the custom fields correctly with no error log.

Equally, the template preview of a resource template with custom fields works fine.

So I assume all is fine.

[Stéphane Aulery]

Ok, is the CMS feature a candidate?

[Mark Grimshaw]

I don't think so. A CMS export of a resource with a custom field gives:
a:1:{i:1265;s:55:"Director, A. (Director) (2023). <em>A film</em> [Film].";}

so we don't export custom fields to CMS (perhaps we should but just not now).

I have also checked with bibtex and RIS exports and all is fine. Likewise, we do not export the custom field to COINs.

Mark

[Stéphane Aulery]

It must be good then.

[Stéphane Aulery]

Tested (OK)