Frequently Asked Questions

Find answers to common questions about our WordPress Database, pricing, and our premium services.

About The Database

What is OnlyTheOnline?

We are the web's largest structured index of WordPress errors. Our goal is to catalog every known conflict, error code, and compatibility issue in the WordPress ecosystem. We provide this data freely to help users diagnose why their site is breaking, rather than just guessing.

Is the database free to use?

Yes. You can search error codes, plugin conflicts, and log patterns in our database at no cost. We believe identifying the problem is the first step to solving it, and that information should be accessible to everyone.

Where does your data come from?

The database grows every time a new issue is resolved. It is a living record of the WordPress ecosystem's health, constantly updated with new 'Zero-Day' bugs and plugin conflicts as they are discovered and indexed.

How current is the data?

We update the index daily. As WordPress Core, PHP versions, and plugins update, new conflicts emerge. Our system ingests resolved tickets and adds them to the database continuously.

Can I download the entire database?

No. The database is a proprietary asset available only via search or our upcoming API. Bulk scraping of the data is not permitted.

Diagnostics & Self-Repair

I found my error code. Why don't you show the code to fix it?

We provide the diagnosis (the 'what' and 'why'), but we stop short of providing copy-paste code solutions. This is for your safety. A code snippet that fixes a site running PHP 8.1 might crash a site running PHP 7.4. Without knowing your specific server environment, providing raw code is irresponsible.

How do I use the database to fix my site?

The database tells you exactly where the conflict is (e.g., 'Plugin A conflicts with Theme B'). You can then use this information to deactivate the specific plugin via FTP, roll back a version, or contact the plugin developer with proof of the error.

Where do I find my WordPress error logs?

You can usually find your 'debug.log' file in the '/wp-content/' folder via FTP. If debugging isn't enabled, you may need to add 'define( WP_DEBUG, true );' to your wp-config.php file. Our database relies on these logs to find matches.

Can I search by Plugin or Theme name?

Yes. Our index allows you to filter issues by specific vendors. For example, you can search for 'Elementor' to see all known active conflicts associated with that plugin in our database.

My error isn't in the database. What now?

If your search returns no results, you are likely facing a 'Zero-Day' issue or a unique environment conflict. You can submit your logs to us for manual analysis. If we solve it, the solution is anonymized and added to the database to help future users.

What is a 'False Positive' in the database?

Sometimes an error message looks generic. Our algorithms assign a 'Confidence Score' to every match. If we are 90%+ sure the error matches a known solution, we display it. If not, we recommend further manual diagnosis.

Services (Paid)

I know the error, but I can't fix it myself. Can you help?

Yes. If you prefer not to touch backend files, you can request an 'Implementation Service' from us. Our engineers will log in, apply the specific patch for that error, and verify your site is back online.

How long does a manual implementation take?

If you hire us to apply the fix, most issues are resolved within 2 to 4 hours of us gaining access, because we usually know the solution before we even log in.

What if I pay for a fix and you can't solve it?

In the rare event that our engineers cannot resolve an issue after a manual review, you will receive a full refund. We only charge for resolved incidents.

Do you provide maintenance plans?

No. We are an Incident Response and Data entity. We focus on fixing the immediate break. We do not offer general monthly maintenance, SEO, or content updates. We simply get you back online.

Why do you need admin access to apply a fix?

We cannot edit your files or database from the outside. If you request our implementation service, we require a temporary administrator account. We recommend deleting this account immediately after we close the ticket.

What happens if the fix breaks something else?

This is why we recommend our implementation service for complex errors. We perform a 'Regression Check' after every fix to ensure that resolving a plugin conflict didn't break your layout or checkout flow.

Do you offer phone support?

No. To maintain the accuracy of our data and the speed of our engineers, all communication is handled via our ticket system. This allows us to share logs and code snippets efficiently.

Technical Scope

What is the difference between a Fatal Error and a Warning?

Our database indexes both. A 'Fatal Error' stops your site from loading (White Screen of Death). A 'Warning' or 'Notice' usually allows the site to run but indicates underlying code issues. We prioritize Fatal Errors in our search results.

Do you support WooCommerce?

Yes. A large portion of our database is dedicated to WooCommerce conflicts, specifically issues regarding checkout failures, payment gateway API errors, and variable product glitches.

Do you work with page builders like Divi or Elementor?

Yes. We have extensive indexes on JSON errors, loading failures, and editor timeouts specifically related to Elementor, Divi, Beaver Builder, and Oxygen.

Does your database cover server-side issues?

Yes. We track errors related to PHP version incompatibilities (e.g., running old plugins on PHP 8.2), MySQL database crashes, and memory limit exhaustion.

Do you fix hacked sites?

Our database primarily indexes technical errors, code conflicts, and server misconfigurations. While we can fix issues caused by malware damaging core files, full malware removal and security hardening is a separate discipline.

API, AI & Developers

Can I connect my application to your data?

We are currently finalizing a public API. This will allow hosting companies, plugin developers, and agencies to query our issue database programmatically. If you want to automate diagnostics for your own users, please join our developer waitlist.

How does the AI/ChatGPT integration work?

We are building a connector that bridges the gap between raw error logs and our structured data. Soon, you will be able to feed an error log into our custom ChatGPT model, and it will query our database to identify the specific plugin or theme causing the conflict.

Is the API free?

We will offer a tiered model. Casual usage for individual developers will have a generous free tier. High-volume enterprise access for hosting companies or support agencies will be a paid product.

I am a hosting provider. Can we partner?

Yes. We are looking for hosting partners who want to integrate our API into their support dashboards to reduce their own support ticket volume. Please contact our partnerships team.

Can I contribute a fix I found?

We are working on a 'Community Submission' feature. This will allow developers to submit errors and solutions they have discovered, earning credits and reputation on the platform once verified by our team.

Security & Privacy

Is my data safe?

We take data privacy seriously. When we index an issue, we strip all personal identifiable information (PII), domain names, and user paths. We only store the technical 'skeleton' of the error (e.g., the file path structure and error code).