Skip to content

Importers: Migrate Kit Legacy Forms#1127

Open
n7studios wants to merge 12 commits into
importers-support-multiple-attribute-detectionfrom
tools-migrate-legacy-forms
Open

Importers: Migrate Kit Legacy Forms#1127
n7studios wants to merge 12 commits into
importers-support-multiple-attribute-detectionfrom
tools-migrate-legacy-forms

Conversation

@n7studios

@n7studios n7studios commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Summary

As the Kit API evolves, existing API versions will be deprecated - which at some point would include Kit's legacy forms.

This PR adds an option in Settings > Kit > Tools to replace Kit Legacy forms with Kit non-legacy forms across shortcodes and blocks:

Screenshot 2026-06-30 at 14 23 17

Future PR's to follow covering:

  • a notice in the Plugin settings screens to migrate away from legacy forms,
  • notices in Post, Category and Plugin setting screens where legacy forms are specified,
  • removing legacy forms from dropdown selectors
  • removing calls to legacy forms
  • removing support for v1, v2 and v3 APIs

The idea is users are encouraged to migrate to non-legacy forms (given some refuse to move away from them), with the plugin being more and more opinionated over time as deprecation deadlines appear.

Testing

Checklist

@github-actions

Copy link
Copy Markdown

WordPress Playground

🚀 Your PR has been built and is ready for testing in WordPress Playground!

Click here to test your changes in WordPress Playground

@n7studios n7studios requested review from a team, ciccio-kit and noelherrick and removed request for a team June 30, 2026 09:53
@n7studios n7studios marked this pull request as ready for review June 30, 2026 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant