SShortSingh.
Back to feed

Doofinder and Queryra tested on WooCommerce search: plain-language queries show gaps

0
·1 views

A developer compared Doofinder, an established Spanish site-search service, with Queryra, his own hosted WooCommerce search plugin. He tested six live Doofinder-powered stores on 9 November 2026 by typing exact product names, typos, everyday-language needs, price limits and exclusions. Doofinder handled exact names and typos well but often failed on everyday phrasing, and in no store did it apply a typed price limit. The author's own demo store, which uses a smaller and partly self-chosen set of queries, produced stronger results for Queryra, a comparison he acknowledges is not like-for-like. The article also quotes Doofinder's marketing and documentation claims about NLP and semantic search, which the author contrasts with the observed results.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Moodle 5.1 moves web root to public/; nginx config must follow

Moodle 5.1 relocated the web-accessible files into a public/ subdirectory, which is now the dirroot. Servers still pointing their document root at the install root will expose source files such as config.php, composer files, vendor/, and .git. The article recommends checking what PHP reports for root, dirroot, wwwroot, and dataroot against the web server configuration. It also suggests probing the public hostname to confirm sensitive paths return 404 while index.php and pluginfile.php remain reachable. The dataroot should stay outside both directories and must not be moved into public/.

0
ProgrammingDEV Community ·

Who Owns Security? Why Responsibility Is Shared Across Three Core Areas

Many organizations spread security responsibility so thinly that nobody feels fully accountable, leaving gaps that attackers can exploit. Security is commonly divided into physical, technical (cyber), and administrative areas, and a strong program must cover all three rather than relying on software alone. Accountability is layered across senior leadership, the security function, plant and operations management, engineering, IT teams, employees, and vendors. The article notes that the merging of IT and operational technology (OT) has created a gray zone where tasks such as patching industrial systems often fall through the cracks. It recommends a responsibility matrix that assigns an owner, supporting party, and escalation contact for each key activity.

0
ProgrammingDEV Community ·

Cursor traces malicious extension to a leaked vendor key and marketplace cache breach

Cursor's November 13 incident update describes how an access key issued to AI infrastructure provider Fireworks let an attacker copy data from a shared read-only storage bucket. That data included coding-agent traces, some of which contained unredacted credentials, and the attacker used them to reach selected SaaS tools. On October 29 the attacker placed modified copies of Anthropic's Claude Code extension into the cache serving the Cursor VS Code extension marketplace, where they were reportedly available for about eleven hours. Cursor says fewer than 0.01 percent of customers had API credentials exposed and at most 5,000 users may have received the malicious versions. The company has since deactivated the key, moved inference off Fireworks, and rotated credentials, and advises affected users to check endpoints for persistence beyond removing the extension.

0
ProgrammingDEV Community ·

Developers Can Now Let AI Agents Send Email via the Model Context Protocol

AI agents typically need custom wrappers around email APIs to send messages, which are costly to build and maintain. The Model Context Protocol lets a service publish its own tool definitions so MCP-capable clients can discover and call them directly. The article demonstrates this with emitd, a transactional email API whose hosted MCP endpoint exposes tools such as send_email and get_message. Because the tools mirror the REST API's fields, agents can send messages and check delivery status without hand-written schemas. The piece also notes that email sends cannot be undone, so access controls such as scoped API keys matter before granting agents this capability.