klaviyo / magento2-klaviyo

37 stars 51 forks source link

Error when accessing Klaviyo Newsletter in Configuration #277

Closed nix0x00 closed 6 months ago

nix0x00 commented 7 months ago

Environment details

PHP version: 7.4 Magento version: 2.4.3-p3 Klaviyo extension version: 4.1.0 Anything else that would help a developer reproduce the bug?

Screenshot 2023-12-01 at 1 18 48 AM

Steps to reproduce

  1. Install Klaviyo 4.1.0
  2. setup:upgrade & s:d:c
  3. deploy static-content
  4. Enter the API public and private keys in Stores > Configuration > Klaviyo
  5. Access Newsletter from Stores > Configuration Klaviyo > Newsletter

Expected result

Should have shown the newsletter configuration, however throws an error.

Actual result

On frontend or browser following error occurs.

 <form action="https://www.domain.com/admin/admin/system_config/save/key/4b62758f04d5d27e9d4c8e2976f1ed799566f8a7c45ebd71edb795bbc908fbd6/section/klaviyo_reclaim_newsletter/" method="post" id="config-edit-form"
  enctype="multipart/form-data">
<div><input name="form_key" type="hidden" value="zXFYWHBrbhW3Sc2K" /></div>
<div class="accordion">
    An error has happened during application run. See exception log for details.

Additional information

Klaviyo 4.1.0 is not working, and recently 4.0.x version stopped working and integration was not being established with Klaviyo. upon contacting support they asked to upgrade the version to 4.1.0. however, 4.1.0 is causing this error.

jordanleslie commented 7 months ago

Hey, would you mind sharing your klaviyo public key? [docs]

nix0x00 commented 7 months ago

Hey, would you mind sharing your klaviyo public key? [docs]

Hey, sure it's RiPczu.

jordanleslie commented 7 months ago

We were able to recreate this by entering an invalid private api key into the general config section of the klaviyo settings. We're going to throw up a fix for this but in the meantime please check that you're using a valid private api key that has the proper access permissions. The key should be a "Full Access" key with all permissions enabled. That should resolve the issue.

https://help.klaviyo.com/hc/en-us/articles/115005254348

cykolln commented 6 months ago

This has been merged and the fix is in the latest release!