visualizer/upsert-chart fails with undefined wp_tempnam() in REST/MCP requests
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 57/100
Direzione di ricerca
Start in classes/Visualizer/Module/Abilities.php, reading buildManualSource() around lines 1153–1205 and tracing its call from executeUpsertChart(); compare _getCSV() in classes/Visualizer/Module.php for how another path handles the optional helper. Add coverage for manual-data upserts through fresh REST/MCP requests with dry_run both enabled and disabled. Done means valid requests return a preview or create the chart without an undefined wp_tempnam() error.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
Creating a chart with manual column and row data through visualizer/upsert-chart can fail with Call to undefined function wp_tempnam(). The submission reports the error while creating a combo chart, including with dry_run enabled. Valid requests are expected to create the chart or return a validation preview; affected requests terminate instead, preventing both creation and dry-run validation.
Customer context
- Product / area: Visualizer, visualizer/upsert-chart ability exposed through Easy MCP AI
- Version: Easy MCP AI 2.2.2 reported; installed Visualizer version not provided. The relevant defect is present in inspected Visualizer tags v4.0.9–v4.0.11.
- Environment: REST/MCP ability invocation; WordPress and PHP versions not provided
- Reported symptom: Undefined wp_tempnam() while creating a combo chart, with and without dry_run
- Impact: Chart creation and validation preview fail
Reproduction notes
Reported: invoke wp_ability_visualizer_upsert_chart to create a combo chart; both normal and dry-run calls fail with undefined wp_tempnam(). Source-derived verification case: enable the Visualizer ability on WordPress with the Abilities API, use an authorized account and a permitted chart type, supply valid typed columns and nonempty rows, and invoke it through a fresh REST/MCP request without the admin file helper preloaded. Repeat with dry_run true and false. Not executed locally; exact reporter payload and installed Visualizer version are unavailable.
Diagnosis
Conclusion
Visualizer's manual-data ability path calls an admin-file helper without establishing that its defining file is loaded. The reported undefined-function error matches this source defect. Valid typed columns and rows reach the call before the dry-run return. This is a dependency-loading defect, not evidence of mixed Visualizer class versions.
Where this likely occurs
classes/Visualizer/Module/Abilities.php—Visualizer_Module_Abilities::executeUpsertChart()lines 631–669 invokes manual-source construction; its dry-run return is later at lines 691–700.classes/Visualizer/Module/Abilities.php—Visualizer_Module_Abilities::buildManualSource()lines 1153–1205 validates the supplied data and then callswp_tempnam()without loading its defining include.index.php—visualizer_launch()lines 135–152 registers the abilities module outside the conditional admin-module branch;visualizer_autoloader()lines 43–51 resolves Visualizer classes, not WordPress functions.classes/Visualizer/Module.php—Visualizer_Module::_getCSV()lines 266–276 demonstrates that another Visualizer path explicitly accounts for this helper's optional availability.- Commit
54b9615dintroduced the abilities module. The unguarded call is present in release tags v4.0.9, v4.0.10, and v4.0.11. No previously working ability version was established, so this is not classified as a regression.
Engineering notes
The callback is implemented by the free Visualizer plugin; inspection of visualizer-pro found no replacement for this ability path. Easy MCP 2.2.2 bridges enabled abilities to their callbacks rather than implementing chart creation. The failure depends on whether another request component has already loaded the WordPress helper. WordPress's official wp_tempnam() reference was checked and identifies wp-admin/includes/file.php as its defining file; WordPress core was not present in the inspected plugin checkout. The constructed reachable input is a permitted chart type with valid manual columns and rows, regardless of dry_run. The reporter's precise input and installed Visualizer version remain unknown.
Test coverage status
tests/test-chart-data-sanitization.php — test_get_chart_ability_returns_stored_cells() lines 111–117 covers the read ability, not chart upsert or its non-admin dependency loading. No relevant upsert/dry-run coverage was found during inspection. Runtime reproduction and PHPUnit execution were unavailable because PHP is not installed in this workspace environment.
What to verify or explore next
- Reproduce through a fresh REST/MCP request in which
wp_tempnam()is initially unavailable, using valid manual columns and rows. - Compare dry_run true and false, checking validation output and chart persistence respectively.
- Confirm the reported combo-chart case with a plan that permits that chart type, and compare a supported free chart type.
- Check the installed Visualizer version and whether other active plugins incidentally load the admin file helper.
Unknowns / follow-up
The original chart payload, WordPress/PHP versions, and installed Visualizer/Pro versions were not supplied. The failure was source-confirmed rather than reproduced locally. No matching open issue was found in the Visualizer issue searches.
Confidence
Confidence: 96/100
The exact missing helper is called unconditionally on a reachable manual-data path before the dry-run branch, and its defining include is not established by that path in the inspected releases.
Source: automated in-product feedback — easy-mcp-ai, 2026-11-16
Generated by bug-report-triage (ID: bug-report-triage_6afbe41e54a3b6.69081491)
- Lingua principale
- PHP
- Stelle
- 108
- Fork
- 29
- Merge medio
- 3g 12h
- PR unite (30g)
- 15
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Codeinwp/visualizer
-
feature-request-triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 64/100
Codeinwp/visualizer#1388 ·
I maintainer di solito rispondono entro 1 giorno
-
Add a Default value for font settingsForse di nuovo libera Una pull request per questa issue è stata chiusa senza essere unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 25/100
Codeinwp/visualizer#1111 ·
I maintainer di solito rispondono entro 1 giorno
-
customer report doc-needed new feature
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
Codeinwp/visualizer#1058 · 4 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
question
Difficoltà 5/5 Più di una settimana Idoneità per principianti 15/100
Codeinwp/visualizer#1024 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
new feature
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
Codeinwp/visualizer#1002 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di Codeinwp/visualizer
Issue simili
-
Change: check an identifier filter the same way in every tool - the order of somcp_search_ordersApertaconsistency enhancement Orders
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
novalo-dev/Prestashop-MCP-Server#343 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
claude
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
sprain/sprainocchio#45 ·
I maintainer di solito rispondono entro 1 giorno
-
sync-en
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno
-
sync-en
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno