Release#457
Merged
Merged
Conversation
Bumps [codeinwp/themeisle-sdk](https://github.com/Codeinwp/themeisle-sdk) from 3.3.50 to 3.3.51. - [Release notes](https://github.com/Codeinwp/themeisle-sdk/releases) - [Changelog](https://github.com/Codeinwp/themeisle-sdk/blob/v3.3.51/CHANGELOG.md) - [Commits](Codeinwp/themeisle-sdk@v3.3.50...v3.3.51) --- updated-dependencies: - dependency-name: codeinwp/themeisle-sdk dependency-version: 3.3.51 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…/codeinwp/themeisle-sdk-3.3.51 chore(deps): bump codeinwp/themeisle-sdk from 3.3.50 to 3.3.51
Collaborator
Widget instances exported from another site reference menus by numeric term_id (e.g. `nav_menu` => 3), which never match on the target after a fresh import. `Slug_Mapping::rewrite_value()` only rewrites URL strings, so the integer passes through and `wp_nav_menu(['menu' => 3])` silently renders nothing. Add a pre-import resolver that consumes a `_ti_nav_menu_slug` hint (carried by companion exporters), looks the slug up on the target site via `wp_get_nav_menu_object()`, rewrites `nav_menu` to the fresh term_id, and strips the hint so it never persists into `widget_nav_menu`. Unresolved slugs are non-fatal. Expose the resolution step as a `ti_tpc_widget_pre_import` filter so future ID-by-reference widgets (taxonomies, products) can plug in without further core changes. Covered by `tests/widgets-import-test.php` with three cases: successful resolution, unresolved-slug fallback, and filter-hook invocation. Made-with: Cursor
…tion fix(importer): resolve nav_menu widget term_id from slug hint
When the TI_ONBOARDING_DEFAULT_SITE constant is defined, the post-activation redirect now lands on the preview/import screen for that site (admin.php?page=neve-onboarding&site=<slug>) instead of the default search/welcome screen. The onboarding store resolves the ?site=<slug> query param against the bootstrapped sites list (across all builders) and starts at step 3 with currentSite preset; if the slug is unknown the app falls back to the existing search screen. This lets distributions and embedded environments (e.g. WordPress Playground) deep-link a user straight to the import flow for a chosen starter site. Made-with: Cursor
…direct feat(onboarding): support TI_ONBOARDING_DEFAULT_SITE redirect
Collaborator
|
🎉 This PR is included in version 1.2.27 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
pirate-bot
added
the
released
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.