[ENGA-276]: Issue of our cronjob script looking for a charge in the d…

[aashishgurung]

1. Objective

Fix the issue of an order getting canceled citing Payment expired when the charge was completed successfully.

Jira: #276

2. Description of change

Similar to this PR #336, our cron script was looking for a charge in the default store where instead of the the store from where the order was ordered.

• Added a code that gets the store ID from an oder and sets the store ID property of the config class. With this, the plugin will fetch the correct keys from the DB instead of the default store's keys.
• Made a slight change in the Model/SyncStatus.php so that we check the data key from the refund object instead of the whole object because data key holds the actual refund object.

3. Quality assurance

Run these commands

// create crontab
$ bin/magento cron:install

// run our cron group
$ bin/magento cron:run --group omise

🔧 Environments:

• Platform version: Magento 2.4.4
• Omise plugin version: Omise-Magento 2.27.0
• PHP version: 7.4.28

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication