Hello,
Thanks for the detailed report, that really helps. The version comparison and the fact that you already tested with other plugins disabled saves us a lot of time. And sorry to hear you haven’t gotten a clear update by phone yet.
To answer your questions: we just tested this ourselves with version 6.9.0 of the MyParcel plugin, WooCommerce 11 and WordPress 7.1, and bulk label printing works fine on our end. So this doesn’t look like a general WordPress 7.1 compatibility issue, at least not with the latest plugin version.
Which version of the MyParcel plugin are you running? If it’s an older one, I’d suggest updating to the latest release first. There’s a good chance that already fixes it.
As for HPOS: that has been supported since version 5 of the plugin, so nothing new is coming there, it’s already in place.
If the problem is still there after updating, please reach out to our IT Support team at support@myparcel.nl and mention your plugin version. They can look into it further with you.
Kind regards,
Jochem
Hello Jochem,
Hello,
Thank you for your response.
The issue is that version 6.9.0 is not publicly available through WordPress.org or through the regular WordPress plugin update mechanism. The latest version listed on WordPress.org is 4.26.0.
I downloaded version 6.9.0 manually from GitHub and tested it, but bulk label printing still does not work on WordPress 7.1. Therefore, I cannot confirm that version 6.9.0 resolves the issue.
Although HPOS support may be included in version 5 and later, those versions do not appear to be publicly available to regular users through WordPress.org or the WordPress dashboard. The plugin page on WordPress.org currently states that the publicly available version has been tested up to WordPress 7.0.4.
This creates an important distinction:
- MyParcel has tested version 6.9.0 with WordPress 7.1;
- regular users cannot install or update to version 6.9.0 through the normal WordPress update process;
- the publicly available version on WordPress.org is 4.26.0;
- the publicly available version is only listed as tested up to WordPress 7.0.4;
- bulk label printing does not work for me with version 6.9.0 either.
Could you please clarify the following?
- Why are versions 5.x and 6.x not available through WordPress.org or the WordPress update mechanism?
- Is version 6.9.0 an official stable release, a beta, or an unreleased version?
- When will the HPOS-compatible version be made publicly available?
- When will the WordPress.org version be updated and tested with WordPress 7.1?
- Can you provide an officially supported version that resolves the bulk label printing issue?
I have already contacted MyParcel by phone. I was told that someone from IT would call me back, but I have not received a call or a clear timeframe. Referring me to IT again without providing a concrete version or workaround does not resolve the issue.
At the moment, the public plugin version appears to be outdated, while the version you tested internally is not available to regular customers through the normal update channel. That makes it impossible for customers to apply the version you are referring to.
I would appreciate a concrete answer regarding the public release and a supported solution.
Hello,
Thanks for the detailed follow-up, you’re raising fair points and I want to address them directly.
You’re right that the latest version on WordPress.org is 4.26.0. That does not mean versions 5.x and 6.x are beta or unreleased. Version 5 was a complete rewrite of the plugin, and because that is a big change for existing shops we deliberately chose not to push it to everyone at once through the regular update channel. These versions are stable and are already in full production use by a large number of customers. I don’t have a concrete date I can share right now for when the new version will be published on WordPress.org.
The key point for me is this: bulk label printing also fails for you on 6.9.0, while it works on our own environment with the same WordPress 7.1. That means something specific in your setup is going wrong, and we’d really like to look at it together with you rather than guess from a distance.
I’m sorry to hear IT hasn’t called you back yet. It’s unfortunately busy on their side, but I’ll ask them to reach out to you with priority so someone can actually dig into this with you. Under which company name can we find you in the MyParcel system? Then I can point them straight to your case.
Kind regards,
Jochem
Hello Jochem,
Thank you for the clear explanation.
You can find us in the MyParcel system under: 125560
Please ask IT to contact me directly and investigate this on the affected installation. As mentioned, version 6.9.0 does not work for us either:
- bulk label printing does not work;
- printing a label from an individual order does not work;
- clicking the MyParcel label button produces no usable result.
I can provide the exact WordPress, WooCommerce, PHP and MyParcel versions, and I can reproduce the issue while IT is connected with me. I can also provide browser-console output, network information and relevant logs if needed.
Please ask IT to contact me by phone. I would appreciate confirmation once the case has been assigned to a specific person.
Hello,
Thank you, we’ve located your account with that number.
I’ve assigned the case to a colleague from our IT Support team. They will contact you by phone as soon as possible. I expect that will be today, but I can’t promise that with full certainty, so please bear with us if it ends up being slightly later.
The information you offered is exactly what will help: the exact WordPress, WooCommerce, PHP and MyParcel plugin versions, browser console output, network details and logs. Please have those ready for the call, and being able to reproduce the issue live while connected will speed things up a lot.
Kind regards,
Jochem
We have exactly the same issue on our end. No working bulk export.
We are still on the older plugin, as we are missing filters on the new one.
Hello,
We are also experiencing issues after WordPress 7.1. I have installed MyParcel 6.9.0. When we try to export an order we get a fatal error:
PHP Fatal error: Uncaught RuntimeException: No default carrier available; shop has no default carrier set in /var/www/vhosts/fansi.nl/httpdocs/wp-content/plugins/woocommerce-myparcel/vendor/myparcelnl/pdk/src/Account/Model/Shop.php:63
This error is also triggered on the checkout thank you page.
It’s unclear for me where I have to select the default carrier.
Hi Jochem,
I have found additional confirmation that this issue is not unique to our environment.
Another user on the MyParcel forum reports exactly the same fatal error when using MyParcel 6.9.0 with WordPress 7.1:
PHP Fatal error:
Uncaught RuntimeException:
No default carrier available; shop has no default carrier set
The error occurs when exporting an order. They also mention that it is unclear where the default carrier should be configured.
Another user reports that bulk export is still not working in the older version 4, while version 6 is not a suitable replacement because important filters are missing.
This matches our situation:
- MyParcel worked correctly with WordPress 7.0.4;
- the issues started after upgrading to WordPress 7.1;
- version 4 returns a generic error when retrieving labels;
- version 6.9.0 throws the fatal “No default carrier available” exception;
- the API correctly returns PostNL and contract 9642;
- printing via the print icon also produces a JavaScript error in wcmp-admin.js;
- another plugin experienced a similar WordPress 7.1 compatibility issue and released a specific fix for it.
You previously told me that MyParcel version 6 should work in our environment. However, another customer using the same plugin version and WordPress 7.1 is now reporting exactly the same error. This strongly suggests a compatibility issue between WordPress 7.1 and MyParcel 6.9.0, or one of its PDK components.
Could you please escalate this to your development team and provide a concrete answer to the following questions?
- Is MyParcel 6.9.0 officially compatible with WordPress 7.1?
- Is the “No default carrier available” exception a known issue?
- Where exactly should the default carrier be configured?
- Why does the API return PostNL and contract 9642 correctly, while the PDK cannot determine the default carrier?
- Is there a patch, beta version, or supported workaround available?
- Is there a specific WordPress/MyParcel version combination that you recommend as a temporary solution?
- Are the missing filters in version 6 planned to be restored?
I am still waiting for the telephone call that was previously promised. This issue is blocking our production label generation and bulk export, so I would appreciate a concrete update and a phone call as soon as possible.
Kind regards,
Oscar
Good morning @emiel9d,
The “no default carrier found” error is a known issue and luckily it has an easy fix.
In the MyParcel plugin, open the options at the top and go to the debug options. There you’ll find the button “handmatig bijwerken” (manually update). This fetches all the necessary information about your account from the MyParcel API, including the default carrier. So you don’t need to select the carrier anywhere yourself, it comes straight from your account settings.
Could you let me know if this resolves the error for you? If it doesn’t, the best next step is to contact our IT Support team at support@myparcel.nl, so they can take a look at your environment as well.
Kind regards,
Jochem
Hi @photooseu ,
Let me go through your questions one by one.
- Yes, MyParcel 6.9.0 is officially compatible with WordPress 7.1.
- Yes, the “No default carrier available” exception is a known issue. It can be resolved by fetching your account settings again, using the steps I described above in my reply to @emiel9d (plugin options > debug options > the “handmatig bijwerken” / manually update button).
- You should not have to configure the default carrier yourself anywhere. It is retrieved from our capabilities API, which is exactly what the button above does.
- Most likely because these are different endpoints. The call you checked returns your contract data, while the default carrier comes from the capabilities data the plugin has stored. Refreshing that stored data, as in point 2, resolves it.
- Yes, see point 2. That is the supported workaround.
- With that refresh applied, the latest plugin version should work fine with WordPress 7.1, so a downgrade combination shouldn’t be needed.
- I’d like to hear which filters you are missing in version 6, so I can pass that on to the team.
I’m sorry you still haven’t received the phone call. I’ve asked our IT Support team again to call you if that hasn’t happened yet. I hope the steps above already get you unblocked in the meantime.
Kind regards,
Jochem
@jochemgrave Is there a way I can contact you about the needs for extra filters?
