wp-sqlite-db VS WordPress

Before they added SQLite as WP plugin, I would use https://github.com/aaemnnosttv/wp-sqlite-db/ and I would use `define('DB_DIR', '/absolute/custom/path/to/directory/for/sqlite/database/file/');` to define the database location of my choice; I believe they would let users do the same with core support.

They basically took this implementation and just adapted it to coding standards:

https://github.com/aaemnnosttv/wp-sqlite-db

This has been around since some time and is itself a fork of a previous work.

The interesting part is that this drop-in replacement (mostly) already works well, there are a few issues that are related to some quirks in the WordPress core itself, for example: https://github.com/aaemnnosttv/wp-sqlite-db/issues/18

And maybe now they will be fixed.

Author here, here's an in-depth writeup on how this works and why it's useful:

https://make.wordpress.org/core/2022/09/23/client-side-webas...

To answer your questions directly:

WebAssembly is the magic sauce that transforms server-side code into client-side code. MySQL unfortunately is not yet supported by WebAssembly, so I applied a plugin that adds SQLite supports to WordPress [0]. The WebAssembly application has its own in-memory filesystem that lives in a specific browser tab and is scraped as soon as you close it.

So – technically it exposes db credentials, and even the entire DB, but that you are the only user of that DB so it's okay.

> What would the backend look like

The only backend is a static file server where the code and the database live. Your browser downloads a copy of the database and allows you to modify it in the current tab, but the updates are never saved back to the server.

[0] https://github.com/aaemnnosttv/wp-sqlite-db

1. Plugins that register their own database tables (however there already exists prior art such as https://github.com/aaemnnosttv/wp-sqlite-db for handling these cases)

2. Plugins that do direct queries against the standard database schema (broadly either for invalid (bad code) or performance (valid but slim use case) reasons)

Also, WordPress would of course keep the old query functions around and they would likely add a tag to the plugin repository so authors can mark plugins as supporting thes new ORM features.

Great idea in my opinion!

There's a WordPress plugin that adds support for SQLite as an alternative to MySQL.

Apparently it works really well. The implementation is (to my) simply astonishing: they run regular expressions against the SQL to convert it from MySQL dialect to SQLite! https://github.com/aaemnnosttv/wp-sqlite-db/blob/9a5604cce13...

This wp-sqlite-db one. Not super active, but maintained, at least.

Creating a high-performance website is essential in today’s digital age. Speed, efficiency, and a seamless user experience are the cornerstones of successful web development. This article explores how combining Next.js with WordPress can achieve these goals, providing a robust solution for developers looking to elevate their web projects.

WordPress as the backend headless CMS, offering a versatile content management foundation.

Open source CMS WordPress and Drupal introduced WYSIWYG editors and template customization to empower independent publishing but page building was still largely code-driven.

While specific CMS platforms were not directly listed in the sources as explicitly supporting Behat, it’s widely known in the development community that Behat can be integrated with several PHP-based CMS platforms. Drupal and _WordPress _are notable examples of PHP CMSs that support Behat testing, thanks to their flexible architecture and the availability of various plugins or modules that facilitate integration with Behat. For instance:

WordPress is the most popular CMS(Content Management System) among bloggers. The same fact has made WordPress more vulnerable to attacks by hackers. Especially for authentication vulnerabilities such as brute-force attacks.

I recent WordFence scan identified the plugin reCaptcha by BestWebSoft as a "critical" vulnerability adding that it has been removed from wordpress.org. Where can I find information as to why it was removed from wordpress.org or why it is a critical security vulnerability?

The Genshine Impact database site looks pretty custom, can't tell if there is any CMS involved. You could start with the tried and tested WordPress. I built my gaming site on WordPress, it's not as fancy as the site you linked but it has plenty of options and flexibility to build all sorts of sites.

Almost every host has one-click WordPress installs these days using either cPanel's WP Toolkit or Softaculous, so that should be a non-issue. You never have to visit wordpress.org if you go that route; the host is handling that for you. Watch Ferdy Korpershoek's videos on YouTube for tutorials on getting started with WordPress. Personally, I would not go with his hosting recommendations, however. I like iWebFusion, but there are other good recommendations over at /r/webhosting

I am on wordpress (commerce plan ) £55pm. wordpress.com is what I am using, however I have heard of wordpress.org also which requires more technical knolwedge which I am willing to invest in over the next 12 months.

wordpress.org requires that user input should be sanitized and validated, and output should be escaped, to prevent mischief by bad actors. This mantra is embedded in current wordpress.org plugin guidelines. Unfortunately older plugins may not comply, leaving them vulnerable. They always were vulnerable, but what's changed is the light has been shone on the issue by Patchman and others. Publicly available code can be scanned by both good and bad actors to detect where malware can be injected.