Magento 2.4 extension not working (Solved)

Well we were able to get the Magento Admin side working... and we've got our connection (sort of) successfully made between Magento 2.4.4 and ShipStation. But there's more problems.... let's say you DO get your Magento installation connected to ShipStation you are still going to face an uphill battle:

auctane_api.ERROR: Deprecated Functionality: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /chroot/home/xxxxx/vendor/auctane/api/Model/Action/Export.php on line 312

ShipStation hasn't made much of an effort to help Magento users fix these problems. We connected immediately and without any issues via ShippingEasy but their system is worse than ShipStation. No APP. Unable to send shipment notification emails for "MARK AS SHIPPED" orders. As much as we hate ShipStation V3 we'd love to stick around if we can get Magento 2.4.4 working properly. If not we've got to move on until ShipStation can get their act together.

Aloha

Can't help with the module install. Via Composer it went pretty smooth for us. No different than any other module. Unfortunately it still doesn't work. 😂

Search the interwebz and you'll find no shortage of Magento users that have MADE IT WORK eventually but it sure would be nice to have a working module for 2.4.4 right out of the box. OR... do what ShippingEasy does and skip the crap and just go straight to a User / Password approach. That makes it relatively easy to get going but the ShippingEasy product is weak sauce compared to the features ShipStation offers (when it works).

Aloha

Unfortunately the "support" that ShipStation is going to give you by email will most likely be next to useless. I think the ShipStation support employees make the minimum effort but it's hard to blame them as they aren't Magento Developers. Magento is downright difficult and one semicolon in the wrong spot brings down the house. I'm hoping that some Moderator will see the length of this thread and make a call to the person within ShipStation (or whatever agency they use for development) and get this fixed. An option we're exploring is to hire a professional Magento developer (we aren't pros, we run our own site because we're cheap) and get this fixed but that's a last resort.

Aloha

I'm having trouble with getting Shipstation to notify Magento 2.4.3 when an order is shipped... any advice?

Also, I have set Shipstation to send an order shipping confirmation to the customer, and BCC'd myself, but they don't seem to be sending to the customer, anyone else experienced this?

Shipstation does not seem to know what they are doing when it comes to Magento...

Did you guys get this to actual work properly on 2.4.4. I am on 2.4.4-p2 and this integration is not working now. I am on module version 2.3.2. I am doing my best with shipstation's development team, but my hopes are not high and this completely puts a halt on our operation. It was unfortunate because it said it was connected and syncing upon doing testing after upgrading to 2.4.4-p2, so we had no idea it was not actually working. 

@lighthouseleds 
Yes, it can be made to work just fine under 2.4.4 and it works great under 2.4.5 too. Unfortunately you probably won't get anywhere with Shipstation employees. My assumption after dealing with this is Shipstation hires an outside agency to handle their Magento 2.x integration. Nobody on staff at Shipstation was ever able to assist us. Our success eventually came about through trial and error and the ability to bounce ideas off @Swappart.  If you start at the 1st post of this thread and work your way down the solution is in here.

Aloha

@Swappart Thanks! I think I'll start off with installing 2.3.1 or 2.3.2 and do the adjustments and see what happens. I did not have a "shipping log" in var/log.

Here are the release notes for 2.3.2. It doesn't seem they fixed those issues, but who knows. I tried to download the extension directly, but magento doesn't seem to allow that anymore.

2.3.2:

• Compatible with Open Source (CE) : 2.3 2.4
• Compatible with Commerce on prem (EE) : 2.3 2.4
• Compatible with Commerce on Cloud (ECE) : 2.3 2.4
• Stability: Stable Build
• Description:

  - Fix issue with carriers not importing

I updated from 2.4.3-p3 to 2.4.4-p2 and shipstation integration quit working.

I went to look at the checkout rates as you suggested. Interestingly it gives me the below.

Checkout Rates
The Checkout Rates feature lets you control what services and rates your customers can select during checkout from your store. To calculate rates, this feature uses:
The product weights provided by Magento
Your ShipStation default warehouse: Business_Ship
The version of the ShipStation plugin installed on your Magento store does not support Checkout Rates.
Please update to the latest version of the plugin available in the Magento Marketplace. Checkout Rates is supported for Magento version 2.3.4 and higher.

Thanks. I'll head back to 2.3.1. I should be able to get to work on that in about 30 mins. It is debian

Now that I am thinking about this. What would be the best way to actually remove the shipstation module from mangento and reinstall 2.3.1.

Seeming, the following command to install: 

composer require auctane/api:2.3.1 --no-update

Edit: I do not have index.php, however that same url has been used for quite some time without issue. I am able to go to site.com/index.php and it will load the site, so I think it will load/respond. 

Ok. We are set, as far as I know. I did not have to apply your fix. I still have debug enabled and there are no errors. I have yet to post anything back to magento from shipstation (from shipping orders), but at least this can get the operation going.

Shipstation chat/help is able to do a different sort of refresh from their end. They did this and it picked up the missing orders.

Interesting. I'll look at the ssl logs and see. You have been an absolute godsend. I can't thank you enough. If I can buy you a "proverbial beer" let me know. It would be my pleasure.

Do you simply have a VM setup with the same OS and stack as the site you're "managing"?

Hello Swappart, I just updated the theme on my website which cause me to have to do a complete database overwrite. I dont know why this is causing issues with shipstation because the development site was a copy of the original where we made the changes. I have checked all the files that I previously changed and they are how we left them. So im not sure why I cant get them to import. I have look through the entire thread and have double checked everything we did last time. If you have any suggestions that would be great.

My store shows that is is connected in shipstation.

No Errors Show.

I have Attributes selected for export.

I have double checked line 312 in export.php

In my shipping log is the following:

[2022-11-11T04:47:07.876494+00:00] main.DEBUG: item Product Type simple [] []
[2022-11-11T04:47:07.876760+00:00] main.DEBUG: Product Type simple [] []
[2022-11-11T04:47:07.876821+00:00] main.DEBUG: Per Product Rate 19.950000 [] []
[2022-11-11T04:50:42.100203+00:00] main.DEBUG: item Product Type simple [] []
[2022-11-11T04:50:42.100654+00:00] main.DEBUG: Product Type simple [] []
[2022-11-11T04:50:42.100729+00:00] main.DEBUG: Per Product Rate 19.950000 [] []

There is a lot of them all the same.

We're running magento 2.4.5 with ShipStation module 2.3.2.

We weren't able to connect to the store but in walking through this whole thread we were able to get it to connect, create orders in shipstation and collect shipment tracking information back to magento. 

The edits we made were to .htaccess to fix the urls that were being asked for, might not work for all but fixed our issues...  

@Swappart  Just wondering if you are using the Amazon MCF extension on your Magento store? I recently installed it and there is a undefined variable error. I know that this should be a simple fix, but I'm not familiar enough with PHP to fix it. 

The Amazon extension developers are MIA, I already had to fix an issue prior to this one with the extension.

Thanks

Hello Swappart,

I am having the same issue again. I am getting a 500 internal server error. I tested and deselected the export custom attributes and then the connection shows no errors and "updates" but no orders come through.

[2023-02-22T06:22:47.400589+00:00] main.ERROR: [SHIPSTATION] From: Auctane\Api\Model\Carrier\Shipping [] []
[2023-02-22T06:22:47.401108+00:00] main.ERROR: [SHIPSTATION] Status Code: 400 [] []
[2023-02-22T06:22:47.401214+00:00] main.ERROR: [SHIPSTATION] URL: https://integration.shipengine.com/magento/deliveryoptions [] []

[2023-02-22T17:31:58.922514+00:00] main.ERROR: [SHIPSTATION] Response: {"request_id"","errors":[{"error_source":"shipengine","error_type":"validation","error_code":"bad_request","message":"The JSON value could not be converted to System.String. Path: $.items[0].weight.value | LineNumber: 0 | BytePositionInLine: 490.","field_name":"$.items[0].weight.value","field_value":"null"}]} [] []

This is what I see in the shipping log.

[2023-02-22T17:39:47.735015+00:00] auctane_api.ERROR: Deprecated Functionality: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home//html/vendor/auctane/api/Model/Action/Export.php on line 494 [] []

This is in the auctane_api.log

Hi,
Great input on this thanks to all.

Magento 2.4.5. + Extension 2.3.2.
Fixes mentioned to code and store to get a 'connection'.

I have tried the .htaccess tweaks (which I assume are the store root .htaccess file) this has made no difference.

The Shipstation Admin appears to drop the Api key and store url after "Testing Connection", when you go back to it. Although as noted below, there seems to be a connection......

The Shipstation Admin reports, after updating stores;

On the server, the log reports;

Any pointers greatly appreciated.
Cheers,

Shipstation "Support" have advised that I downgrade to Magento 2.4.3. !! Which is a version that was launched Aug 2021, with end of life Nov 2022. Impossible and embarrassing to even suggest such a solution.
The main impact here is probably php 7.4 => 8.1 - which I think most have hacked in the code to fix. The connection issue I and others are having, is probably the same as those with Mag 2.4.3. + extension 2.3.1 which is hopefully more tweaks of .htaccess ........

In case it helps, the following entered into the browser (taken from the server log);

Returns

I think this means that Shipstation is getting to the store ok. I am not sure how I can test sending the api key, since I guess this cannot be passed via the Url

For the benefit of others on this, you really are on your own, Shipstation support is just not interested.
1) I have advised them that when I put my Magento Api key and store Url into the Shipstation Connector (i.e. at https://ship8.shipstation.com/settings/stores) test connection (pass), when I return the fields are empty i.e. not saved
2) My server is receiving the connection (I can see in the logs). Shipstation is getting the error I noted earlier.
3) Their response is to downgrade to Magento 2.4.3. and just ignore the issue.
4) After some hacking I have used Postman Api to do a test Get "store-url.co.uk/index.php/api/auctane?action=export&start_date=03%2f14%2f2023+02%3a35&end_date=03%2f22%2f2023+03%3a35&page=1with the Header Auth Key = "ShipStation-Access-Token" and Value {my-magento-api-key}
5) I get xml order data back no problem!!!

This confirms that it is a Shipstation issue i.e. not passing the Api key (which was entered but not save as noted in 1) above.

Does anyone know a way of getting through to a level 2/senior support at Shipstation, to fix my account problem?

Thanks

We face the same issues been using Shipstation for years, upgraded to Magento 2.4.5 php 8.1 error shows up in admin 

Deprecated Functionality: error_log(): Passing null to parameter #1 ($message) of type string is deprecated in /home/maxed4/public_html/vendor/auctane/api/Model/NoConfigNotification.php on line 32

Exception in /home/maxed4/public_html/vendor/magento/framework/App/ErrorHandler.php:62

log auctane_api.ERROR: Deprecated Functionality: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/maxed4/public_html/vendor/auctane/api/Model/Action/Export.php on line 494 [] []

Shipstation seems not to be interested in fixing this and Magento keeps pushing developers to upgrade. 
Maybe they don't need Magento 2.4.5 customers. We have multiple sites so won't be upgrading those until they get this fixed. 

I tried the ShipStationFixer with no luck.
Anyone know how to fix this?

I agree, shipstation support is absolutely dismal and very surprising they could careless about magento integration. My guess is they get most of their business from the SaaS solutions (shopify, bigcommerce, volusion, etc...).

I used the fix by @Swappart and it is working well. I have not had any additional issues. I am now on 2.4.5-p2. I may recommend completely deleting your current shipstation extension and downloading the latest release. I have had issues with their releases and the files not being what they show on magento marketplace version. 

I hope this helps a little. 

I had a similar issue where it wouldn't import orders between when it was working before and then after it was "fixed". I think it is because it believes it imported them. I can't recall what I found when digging into that. I contacted shipstation support (chat) and they can initiate an import different than we can on the client side. I gave them the order numbers and they were able to initiate the import and it brought them in. I would only contact them with that once you confirm a new order imports properly.