neve/appearance-update identity.logo_media_id updates custom_logo but header logo (logo_logo) is unchanged
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 55/100
調査の方向性
Read inc/abilities/appearance_update.php around apply_identity(), then inspect the custom_logo filter in header-footer-grid/Core/Components/Logo.php and its initialization in header-footer-grid/loader.php. First verify whether the filter is registered during an ability call in a REST request, then check whether logo_logo updates for the same, light, and dark variants. Done when the header displays the selected attachment and the ability reports the result accurately.
索引モデルが issue の本文から書いたものです。
説明
Summary
Calling the Neve appearance-update ability with identity.logo_media_id set to a valid image attachment reports success (updated: custom_logo, no warnings), but the header logo shown on the site does not change.
Expected: the visible Neve header logo uses the new image.
Actual: the Neve logo component's own setting keeps the old attachment, so the header still shows the old logo.
Impact: the logo cannot be changed through the ability, and no warning is returned.
Customer context
- Product / area: Neve appearance-update ability (identity block), called via the Easy MCP AI plugin 2.3.0
- Version: Neve version not provided
- Environment: Ability invoked through an MCP/REST context, not the Customizer
- Integration / third party: Easy MCP AI
- Reported error / symptom: custom_logo updated; logo_logo ({light,dark,same}) keeps the old ID
- Impact: Header logo unchanged
Reproduction notes
Reported steps: call the appearance-update ability with identity.logo_media_id set to a valid attachment ID, then inspect the logo_logo theme mod and the header. Not reproduced locally. Whether the logo sync filter is registered in the ability call context is unverified.
Diagnosis
Conclusion
The ability's identity handler writes only the custom_logo theme mod. Neve's header logo component keeps its own logo_logo mod, which is normally synced from custom_logo by a filter. The customer's observation is consistent with that filter not running in the ability context. This is inference; runtime was not reproduced.
Where this likely occurs
inc/abilities/appearance_update.php—apply_identity()approx. lines 607-622: calls set_theme_mod('custom_logo') and reports 'custom_logo' as updated; it does not touch logo_logo.header-footer-grid/Core/Components/Logo.php— constructor approx. line 96 registers thepre_set_theme_mod_custom_logofilter;update_logo_theme_mod()approx. lines 155-164 writes logo_logo.header-footer-grid/loader.phpapprox. line 58-60: the HFG main object is created onafter_setup_theme.
Engineering notes
The sync depends on the Logo component having been instantiated and its filter registered before the ability runs. Whether that happens in REST/ability requests was not verified. No warning is emitted when the visible logo is not updated.
Test coverage status
No relevant coverage was found during inspection for logo_media_id in the ability tests.
What to verify or explore next
May be worth verifying whether the filter is registered during an ability call on a REST request, and the resulting logo_logo value. Worth checking the same=true and dark variants.
Unknowns / follow-up
Neve version and the site's header builder state are unknown.
Confidence
Confidence: 60/100
Only the Neve logo report is supported by code: the ability writes only custom_logo while the rendered logo reads a separate mod. The other four are unconfirmed: WPML needs third-party runtime evidence, the tool description is intentional, the session guard is working as designed, and the wp_update_page path never sends status.
Source: automated in-product feedback — easy-mcp-ai, 2026-10-28
Generated by bug-report-triage (ID: bug-report-triage_6ae2d79682e0c2.61501712)
- 主要言語
- PHP
- スター
- 307
- フォーク
- 89
- 平均マージ
- 2日 20時間
- マージ済み PR（30日）
- 24
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
Codeinwp/neve のほかの issue
-
bug-report bug-report-triage crash-report
難易度 3/5 1〜2日 初心者へのやさしさ 45/100
メンテナーはふだん 1 日以内に返信
-
Duplicate H1: hidden screen-reader title H1 rendered alongside custom layout H1 when page title is hidden対応中かも @HardeepAsrani が 17 日前に担当しました。 オープンbug-report bug-report-triage customer report
難易度 4/5 1〜2日 初心者へのやさしさ 48/100
Codeinwp/neve#4652 · コメント 4 件 · 担当者 1 名 ·
メンテナーはふだん 1 日以内に返信
-
Enhance home screen and front page customization options in Neve Free対応中かも @faisalahammad が 9 日前に担当しました。 オープンfeature-request-triage
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
メンテナーはふだん 1 日以内に返信
-
Add basic Social Icons component to free Header and Footer builder対応中かも @faisalahammad が 9 日前に担当しました。 オープンfeature-request-triage
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
メンテナーはふだん 1 日以内に返信
-
customer report feature-request-triage
難易度 4/5 3〜5日 初心者へのやさしさ 52/100
メンテナーはふだん 1 日以内に返信
似ている issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
CMS video element: "CmsVideoPlugin" sets `volume = 0`, so videos cannot be unmuted on Android Chromeオープンneeds-triage Platform(Default)
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
GD decoder discards the finfo media type in mediaTypeByBinary() since 4.4.0対応中かも @lazerg が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
Intervention/image#1556 ·
メンテナーはふだん 1 日以内に返信
-
bug No Code Attached Yet
難易度 2/5 1〜3時間 初心者へのやさしさ 79/100
joomla/joomla-cms#48730 ·
メンテナーはふだん 1 日以内に返信
-
sync-en
難易度 1/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信