Skip to main content

Magento 2.4 extension not working (Solved)

  • Jun 20, 2022 6:15 PM UTC
  • 33 replies
  • 4 views

Show first post

33 replies

  • Mar 24, 2023 6:08 PM UTC

1) Magento 2.4.5. Have installed/followed all of "Swappart" brilliant work
2) I have not dug into my server logs yet
3) I am seeing the same at SS as before
4) Have put the Api key from Magento and store url into SS, "Test Connection" no problem, then Save.
5) If I  come back and ... "Edit Connection" in SS, the "Setup Marketplace Connection" form does not have the Api/Url details that I previously entered.
6) I have queried with SS and they say that is the same for everyone and that this is not the reason it is showing the red ! instead of a Green Tick.

Question. Is that correct, if you have a working connection and you ... "Edit Connection" in SS, are those fields blank for you, i.e. you cannot "Test Connection" and this can only be done when you first setup (daft if that is the case)?

Cheers


Since custom options were mentioned here, I am curious. Does this actually work for anyone? Unless I am understanding the functionality of it. I am assuming this will allow me to send any attribute from magento (from the selectable list) and import it into shipstation. I have an attribute selected and it never imports into shipstation. 

I am asking because I want to import harmonization codes for international shipping. From what I can see shipstation does not support this "natively" (baffling). I was hoping to set my HS code attribute as an export option and then maybe use that in shipstation to populate the Harmonization field. Typing this out, I doubt that possible but I may as well post it to see if anyone has any luck in getting anything like this to work.


  • May 4, 2023 7:35 PM UTC

This worked for me too.  Only issue I have is not all my order data is coming over on the feed. Anyone know how to edit that so I can add the missing details?


  • May 9, 2023 2:52 PM UTC

Hi, Thanks to Swappart for the huge fix.

We have Magento ver. 2.4.5-p1 and I believe the latest shipstation extension.

We just added a custom attribute in General Settings, and it worked again for importing orders.

However, every maybe 1 out  of 100 orders will not get imported for some reason.

Any ideas or things to check that may fix this?


More issues with updating magento and auctane. ugh.... trying to update from 2.4.6-p3 to 2.4.6-p4

I first tried this with auctane version 2.3.1 and then attempted on 2.4.1. Either version of auctane was unsuccessful. I then found an article regarding zend and adding it back in with composer require: 

public_html$ bin/magento setup:di:compile
Compilation was started.
Area configuration aggregation... 5/9 [===============>------------] 55% 49 secs 362.0 MiB
In ClassReader.php line 57:

Impossible to process constructor argument Parameter #15 [ <required> Zend\Http\Client $zendClient ] of Auctane\Api\Model\Carrier\Ship
ping class

In GetParameterClassTrait.php line 34:

Class "Zend\Http\Client" does not exist

setup:di:compile

 This also didn't work. I am now restoring back to 2.4.6-p3. All of the above mentioned resulted in that same error when trying to compile. How is this that difficult for auctane/shipstation to get this right???

Any advice @Swappart ?


Has anyone here updated M2 to 2.4.6-p4 and using the shipstation integration?


Yet another update from shipstation. Absurd. I think this message alone says they have abandoned magento support.

Thank you for reaching out. 
 
Our senior support team recommends reaching out to your Magento developer to assist with the error. I truly apologize for the inconvenience. I understand how frustrating this can be. 
 
If you need further help feel free to reach out. 
 
Kind regards, 

Itumeleng M.


  • Sep 10, 2024 9:28 PM UTC

I had this problem for months, then recently updated our Magento from 2.4.6-p6 to 2.4.6-p7.  That's when I noticed the Auctane API version in the composer.json file was set to the latest version 2.4.8, even though we're using 2.4.6.  It occurred to me that maybe you have to strictly set the version of the Auctane API module to the same version of Magento that you're using, not just that version or higher, like many modules/extensions.

So, I changed Auctane to 2.4.6 like our version of Magento, like below, went through the setup process like it shows in ShipStation.com again, and it worked perfectly.  Simply "requiring" Auctane at the command line using the "composer" command gives you the latest version, regardless of what version you actually have installed.

"require": {
"auctane/api": "2.4.6",
"magento/product-community-edition": "2.4.6p7"