Deprecated property: 'process'

[DarkChris86]

Hey @imranhsayed!

I got the following message in frontity app:

Bests, Chris

[luisherranz]

Hey @DarkChris86, thanks for the PRs 🙂

If you look at the docs, the signature of the functions also changed. Now they receive objects, like this:

const processor = {
  test: ({ node }) => { /* ... */ },
  processor: ({ node }) => { /* ... */ },
};

The change is backward compatible but we will deprecate the old API at some point. Would you mind adding that change to your PRs? Thanks!!

[DarkChris86]

Hey @luisherranz .

Yes, I'm going to modify them like this! Thank you for friendly note! ; )

[luisherranz]

Thanks to you @DarkChris86! 😄

[DarkChris86]

It's done. Could you check them ( @luisherranz )?

Thanks, Chris

[imranhsayed]

@DarkChris86 Approved and merged the PR.

[DarkChris86]

@imranhsayed When it will be available via npm update? https://www.npmjs.com/package/frontity-contact-form-7

Thanks, Chris

[luisherranz]

Thanks @DarkChris86! 🙌 🙂 (and @imranhsayed)

[davidrhoderick]

I'm still getting this error on the latest version installed by NPM (0.1.4)~~, plus the form isn't showing up on a page that renders the code to a page via a custom field using <Html2react />~~. Anything I can do to fix the error and will it fix the contact form?

EDIT: The form works, I just needed to use a WYSIWYG field instead of a text area as provided by ACF Pro.

[luisherranz]

@imranhsayed can you please release a new version in npm?

[davidrhoderick]

@imranhsayed any update on releasing a new version in npm? The contact form isn't even showing up on my site now.

It's funny, on my laptop, I don't get this error, so it might be related to the version of npm being used. I'll look into this a bit more...

[imranhsayed]

Released the new version on npm

[davidrhoderick]

Thanks @imranhsayed the latest version doesn't have this bug but I have found a new error with the latest version I will create another issue about.