Need Guidance for Migrating Wishlist Notes to Plugin v3

[wolf-ms]

Question

Environment

• Craft CMS Version: 5.6.11
• Wishlist Plugin Version: 3.0.6 (recently upgraded from v2)
• PHP Version: 8.2
• Database: MySQL

Problem Description

We recently upgraded to Wishlist v3 alongside Craft 5, and we need guidance on the recommended approach for migrating our custom wishlistNote field to the new format.

The field previously stored notes directly in the content table, but with Craft 5, the data is stored as JSON in the element_sites table. We want to ensure we migrate the data correctly while maintaining all relationships between notes and their parent lists.

Questions for the Developer

1. What is the recommended approach for migrating custom fields when upgrading to v3?
2. Are there any specific considerations we should be aware of when migrating alongside Craft 5?
3. Is there documentation or example migrations we could reference for this type of upgrade?

Additional Context

• We have approximately 611 notes that need to be migrated
• The notes are currently stored in the old format in the content table
• We want to ensure we maintain all relationships between notes and their parent lists during the migration

We'd appreciate any guidance on the recommended approach for this migration. Thank you!

Additional context

No response

[engram-design]

Is your wishlistNote custom field just a field on the list type? If so, that should be automatically migrated to Craft 5's format in the element_sites table.

Or, are you saying this relationship was far more custom in nature? As in, did you quite literally add a new column to the content table in Craft 4 outside of being a custom field? If that's the case, that's beyond out support as that's not something that Craft itself would encourage, as it sort of breaks the nature of the content table and element-field relationships.

All upgrade docs can be found here, but as we handle all the content migration, there's nothing special you need to do.

[wolf-ms]

Hey Josh,

I appreciate the response. Unfortunately, the wishlistNote custom field was just a plain text field on the list type, nothing fancy, but none of the content migrated over when we moved to Craft 5. We haven't been able to piece together why it didn't migrate, but do you have any recommendations for how to bring it over now? I've started work on a migration script, but haven't had any luck with it yet.

[engram-design]

Ah, I see - thanks for confirming. Let me triple-check that today and let you know! We should certainly be taking care of that migration for you.

[engram-design]

Fixed for the next release. To get this early, run composer require verbb/wishlist:"dev-craft-5 as 3.0.6". The bad news is that you'll need to run your migration again from Craft 4/Wishlist 2, as the migration is skipped and won't run again, and has since "missed" the field content. Sorry about that!

If you really need to trigger this on demand, you could give the following a go in a module:

$migration = new \verbb\wishlist\migrations\m231229_000000_content_refactor();
$migration->safeUp();

[wolf-ms]

Thank you for this, Josh! I really appreciate it. Will this overwrite existing wishlist content or merely add the missing content from the custom field? The client has had the site in operation for a few weeks now and wouldn't want to lose the lists that have been created since then. They're wanting just to restore the old notes that were in the wishlistNote custom field. Thanks again!

…

On Sat, Apr 12, 2025 at 8:57 AM Josh Crawford ***@***.***> wrote: Fixed for the next release. To get this early, run composer require verbb/wishlist:"dev-craft-5 as 3.0.6". The bad news is that you'll need to run your migration again from Craft 4/Wishlist 2, as the migration is skipped and won't run again, and has since "missed" the field content. Sorry about that! If you *really* need to trigger this on demand, you could give the following a go in a module: $migration = new \verbb\wishlist\migrations\m231229_000000_content_refactor();$migration->safeUp(); — Reply to this email directly, view it on GitHub <#155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7R4EF2XGDFBNSP447GXOYT2ZEESLAVCNFSM6AAAAAB2USDIVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHAZDEMRUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***> *engram-design* left a comment (verbb/wishlist#155) <#155 (comment)> Fixed for the next release. To get this early, run composer require verbb/wishlist:"dev-craft-5 as 3.0.6". The bad news is that you'll need to run your migration again from Craft 4/Wishlist 2, as the migration is skipped and won't run again, and has since "missed" the field content. Sorry about that! If you *really* need to trigger this on demand, you could give the following a go in a module: $migration = new \verbb\wishlist\migrations\m231229_000000_content_refactor();$migration->safeUp(); — Reply to this email directly, view it on GitHub <#155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7R4EF2XGDFBNSP447GXOYT2ZEESLAVCNFSM6AAAAAB2USDIVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHAZDEMRUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[engram-design]

I think the main issue here is that the content is essentially gone once you've upgraded to Craft 5, due to how the content tables work, so you're going to need to get that content back in some fashion.

[wolf-ms]

Gotcha, but this is an active Commerce site where wishlists are added frequently. We want to be sure that we won't lose those wishlists if we create a module and run the migration.

…

On Thu, Apr 17, 2025 at 5:20 PM Josh Crawford ***@***.***> wrote: I think the main issue here is that the content is essentially gone once you've upgraded to Craft 5, due to how the content tables work, so you're going to need to get that content back in some fashion. — Reply to this email directly, view it on GitHub <#155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7R4EFYSNUJWMQIQH3UGBN322ALJDAVCNFSM6AAAAAB2USDIVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJUGA2DONJXGA> . You are receiving this because you authored the thread.Message ID: ***@***.***> *engram-design* left a comment (verbb/wishlist#155) <#155 (comment)> I think the main issue here is that the content is essentially gone once you've upgraded to Craft 5, due to how the content tables work, so you're going to need to get that content back in some fashion. — Reply to this email directly, view it on GitHub <#155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7R4EFYSNUJWMQIQH3UGBN322ALJDAVCNFSM6AAAAAB2USDIVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJUGA2DONJXGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[engram-design]

So I don't believe running that will remove any content, it's just going to transfer content from the content table, and ensure that a field layout exists for the list types list and item elements. But I'm happy to test that scenario (I was running this command a few times on an existing install)