In this article we look at solving two errors ("password_activations" or "password_resets" database tables not existing) that can appear once a Statamic 3 site has been configured to store users in a database.
In this article we will start with a fresh Statamic 3 website based on the Cool Writings Starter Kit, integrate Laravel Stripe, and develop customer Antlers tags that can be used to selectively restrict access to premium content.
Customizing a Statamic site's 500 Server Error page is a relatively simple process, as well as developing a custom Antlers tag to help test it.
In the root directory of your site, issue the following command to have Statamic generate the scaffolding we will need to build our custom tag. This will ...
Let's take into consideration the false starts (and restarts) as well as building a flat-file comment system that I thought "would only take two weeks or so"......
Here is a list of all of the add-ons this site is running (at the time of writing) as they appeared in the Statamic Control Panel. ...
Wrapping up Forte Phase 0 with the lexer and parser now in private alpha, and kicking off Phase 1 wi...
Read moreA Forte development update: the parser now supports backtracking, improvements to node metadata, ide...
Read moreWrapping up attribute parsing in Forte's HTML parser, from simple HTML attributes to complex, edge-c...
Read moreExploring how Forte's parser extensions can be used to handle complex Blade directives like nested s...
Read moreDigging into parsing Blade and HTML comments while building Forte's HTML parser for Laravel Blade.
Read moreThis week I’m tackling Forte's HTML parser - consolidating Blade, Flux, and Livewire components into...
Read more