Earlier quoted context omitted.
WordPress is both free and open source, what are the extra dollars for?
If you don’t run it locally, then server rental.
Same with this
WordPress Playground: A WordPress that runs entirely in the browser
191–200 of 221 posts
Re: WordPress Playground: A WordPress that runs entirely in the browser
#192Just tried installing woocommerce and adding a product, but got a bug: Warning: require(/wordpress/wp-includes/post.php): Failed to open stream: No such file or directory in /wordpress/wp-settings.php on line 2 Fatal error: Uncaught Error: Failed opening required '/wordpress/wp-includes/post.php' (include_path='.:') in /wordpress/wp-settings.php:2 Stack trace: #0 /wordpress/wp-config.php(11): require_once() #1 /wordp…
It would be helpful if you could report this to the issue tracker.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#193Earlier quoted context omitted.
Does wordpress.com used a forked version? Last time I remember that the custom themes were limited for the hosted solution. Maybe this was for performance reasons?
On the business plan (25/mo) you can run any plugin or theme, or custom code. You also have full SSH/SFTP and wp-cli access.
That plan actually looks really reasonable. I'm pretty sure when I last looked at it many years ago that stuff wasn't possible.
Thanks for WordPress - it's great. I think I first started 'using' it around 2006/2007ish.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#194Re: WordPress Playground: A WordPress that runs entirely in the browser
#195Earlier quoted context omitted.
This is a reasonable position and with the utility sites I build for, say, bands I play with I totally agree. I toss some shit on commodity hosting and hope the band breaks up before the gcal integration breaks. -=-=-= However. I will now take this opportunity to vent a bit, though it has little to do with your imminently reasonable post. Mostly because I am procrastinating on porting a 3rd-party SSO system from a ve…
I'm happy to pitch in and help migrate those university sites, we can get them on a WordPress stack that's much more stable and forward-compatible.
Going to go out on a limb here and say that a sales pitch doesn't address parent's comment...but it does seem to be implicitly acknowledge that Wordpress is too cumbersome to maintain and even host yourself.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#196Apply the following styles, and it will become a practical tool: ._wrapper_5didy_26 { padding: 0; height: 100%; } ._window_5didy_31 { max-width: none; } ._experimental-notice_5didy_9, ._toolbar_5didy_64 { display: none; }
Or add `?mode=seamless` to the URL:
https://playground.wordpress.net/?mode=seamless
See https://wordpress.github.io/wordpress-playground/query-api/ for more cool options!
Re: WordPress Playground: A WordPress that runs entirely in the browser
#197Reporting from a budget Android Tablet with Firefox, the response times aren't exactly instantaneous but aren't any different than running full LAMP on a reasonable cloud instance or VPS which is surprising to say the least. Also imagine the software layers at play here. Whole PHP Interpreter plus whole thousands of lines from WordPress codebase plus SQLite. Amazing when that's all so much totally useable.
I've always found WordPress performance doesn't change much on lower vs higher end hardware. It seems to be limited by itself.
Yes, but: Number of concurrent visitors can change dramatically on lower vs higher. A caching plugin mitigates this somewhat, but I find that most companies don’t test whether their site can handle surges, or even if it can handle the projected traffic load.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#198Ooops! I suppose it does not work in private browsing mode.
Ooops! Would you file an issue on GitHub? This would really help us track it and fix it.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#199Earlier quoted context omitted.
I've always found WordPress performance doesn't change much on lower vs higher end hardware. It seems to be limited by itself.
What's the answer to making WordPress sites faster? I too have tried better hardware, CDNs, plugins like WP Super Cache, and others means of optimizing. Very little impact. Is the problem PHP? I'm thinking of trying one of those plugins that convert the WordPress site to static web site. I'd imagine that'd have a big impact, at least for sites that don't need e.g. login, shopping carts, etc.
Use a plugin like 'Cache Enabler' by KeyCDN, it's very lightweight and does exactly one thing very well.
Get rid of as many plugins as possible, many of them add a ton of load time and browser load. Woocommerce is especially bad.
Use a lightweight theme, there are a few good ones out there for that. Or just the default one it comes with.
And yeah if you have zero dynamic content needs then a static site generator can work fine. But with minimal plugins and a cache enabler, response time should be very fast anyways.
Re: WordPress Playground: A WordPress that runs entirely in the browser
#200I tried to make a big deal about this in my State of the Word keynote in December 2022: https://wordpress.tv/2023/01/04/matt-mullenweg-state-of-the-... It kind of blew my mind as an engineer to see it work, and know all the layers that had to interact for that to happen. It's fun to see it blowing up on HN 6 months later! :) Thank you to everyone for checking it out.
It's very interesting to me since I have an interest in porting various hitherto "server-side" applications to run in-browser. Doubly interesting because it's the first real product I've seen running SQLite -- so far I've only seen toy demos.
But, wondering about something -- poking around in the code a bit, and realizing I know next to nothing about present-day php, I realized this may be not using the "traditional" SQLite-over-OPFS approach to get persistence?
Actually, after a bit more reading it's not clear to me that persistent storage is available yet via Emscripten.
And after yet more poking around I found: https://github.com/WordPress/wordpress-playground/issues/19 which I guess means that persistence isn't yet possible for WP in the browser :(