Contact FyrePress

Bug Reports

Found a tool that produces incorrect output, throws an error, or behaves unexpectedly in your browser? We want to know about it. Clear, specific bug reports are the single most helpful thing users can contribute. When you contact us about a bug, please include as much of the following information as possible:

• Tool URL: The specific page where the issue occurs (e.g., fyrepress.com/htaccess or fyrepress.com/wpconfig).
• Steps to reproduce: The exact sequence of actions that produces the issue. “I clicked Generate” is less helpful than “I selected option X, entered value Y, and clicked Generate.”
• Expected vs. actual output: What you expected to see, and what you actually received. If the output is code, include the specific snippet that is wrong.
• Browser and version: E.g., Chrome 122, Firefox 124, Safari 17. Also note if you’re on mobile.
• OS: macOS, Windows, Linux, or mobile OS and version.
• Console errors: If you’re comfortable with browser DevTools, check the Console tab (F12) and paste any error messages you see.
• Screenshot or recording: A screenshot or short screen recording (Loom, etc.) that shows the problem can cut resolution time dramatically.

We aim to acknowledge bug reports within 48 hours and resolve validated bugs in the next available update cycle.

Feature Requests

Have an idea for a new tool, a generator option we haven’t implemented, or an improvement to an existing workflow? We actively read and consider every feature request. We can’t promise to build every suggestion, but well-reasoned requests for repeatable, client-side use cases are at the top of our roadmap consideration queue.

When requesting a feature, the most useful format is: describe the workflow pain you’re trying to solve, not just the solution you have in mind. For example: “I regularly need to generate hreflang tags for 10+ language variants and doing it by hand is error-prone” is more useful to us than “add a bulk hreflang generator.” Understanding the underlying need helps us build the right solution.

We prioritize tools that: run entirely client-side, solve a repeatable WordPress or web development task, have clear and bounded output, and serve a broad enough audience to justify the maintenance commitment.

Accuracy & Corrections

If you identify an error in any generated output — a configuration directive that’s incorrect for a specific server version, a deprecated WordPress function, a SQL query with an edge case bug, or any other technical inaccuracy — please report it. We take accuracy seriously and treat correction reports as high-priority issues.

Helpful accuracy reports include: the specific tool and configuration options that produced the incorrect output, the expected correct output and why, the WordPress/PHP/server version context where the issue is observed, and any authoritative documentation or source that supports the correction. You don’t need to be certain something is wrong to report it — a well-reasoned “I think this might be incorrect because...” is enough for us to investigate.

Partnerships & Integrations

If you want to collaborate with FyrePress — whether that’s integrating our tools into a developer platform, featuring FyrePress in a WordPress course or publication, building on our tool ecosystem, or exploring co-marketing opportunities — we’re open to conversations with the right partners.

When reaching out about a partnership, please include: who you are and what you build, what kind of collaboration you have in mind, your target audience and estimated reach, and your timeline. We respond to partnership inquiries that align with our goal of making WordPress development more efficient and private for professional developers.

Press & Media

If you’re a journalist, blogger, or content creator covering WordPress development tools, developer productivity, or web privacy, feel free to reach out. We’re happy to provide quotes, context, or a walkthrough of the FyrePress platform for editorial coverage. Please use the same email address above and mention “press” in your subject line.