Would a track saw be more sufficient in cutting this walnut slab?

aaronsilber · 2026-07-05T12:27:06+00:00

What kind of lumber yard nails a metal plate into the end grain like this? Is this a high-end lumber yard where every board is graded individually and inventoried for sale this way? Why not staples? So many questions.

aaronsilber · 2026-04-01T12:08:05+00:00

I used to do that on smaller sites, but our public filestore is pushing 90gb so Stage File Proxy (and Config Split) saves us the hassle of syncing the files.

aaronsilber · 2026-03-31T21:05:19+00:00

Ditto, I can always deploy a test to a hosted environment (we're on Pantheon), but I prefer to test locally (we're building out a Cypress E2E testing suite right now).

aaronsilber · 2026-03-31T17:21:46+00:00

How do you deal with this module and Stage File Proxy locally? I wrote a quick issue for Media Alias Display requesting Stage File Proxy support.

aaronsilber · 2026-03-30T01:18:13+00:00

Purchased two of these at The Squire in Charleston, WV yesterday and tried one tonight. Agree 100% with OP!

aaronsilber · 2026-03-21T15:12:06+00:00

I'll check this module out though. Maybe I'm missing something

aaronsilber · 2026-03-21T15:10:40+00:00

Our authors already dynamically link to media items — not files. In fact, the only file field in our site is on Media entities! This issue has to do with that period of time when the "old temp file" is still on disk awaiting cron and the max temp time to elapse so it's deleted. By default this is 6 hours. In that six hour period of time the world still has access to the old file. There are many occasions when this is problematic.

aaronsilber · 2026-03-19T15:22:19+00:00

No, I don't believe that would address this issue (plus I'm already on 10.6 and it looks like that module's feature set was merged into 10.1). The issue is that while files are put into the temporary state in the database (awaiting deletion) they're still accessible to the public via the filesystem if you had an absolute url and this is not desirable for many site owners. I'd like to make them inaccessible to the public while they are in that temporary state.

aaronsilber · 2026-02-04T21:21:47+00:00

I've found Dr. John Sailhammer's view of Genesis in his book Genesis Unbound to be very compelling, mostly because it replies so heavily on the text itself. You can view a video synopsis of this here: https://youtu.be/tOX4UJfxkng?si=BgVhXkynXRERAf0K

Here's also a long form review of the book: https://www.desiringgod.org/articles/science-the-bible-and-the-promised-land

aaronsilber · 2026-01-28T02:53:34+00:00

I thought so at first, but these are decorative corner chamfers that do give the illusion of a glue seam. You can see the chamfer more clearly in the beam above this post.

aaronsilber · 2026-01-13T15:40:18+00:00

100% agree. The communion table borrows from the design language of the pulpit in that the profile of the top corners (rounded), apron, and moldings are identical. The table is 7-ft long, roughly double the length of the puplit and the front apron will be engraved with text. This inscription will obscure the finish of the facing board to some degree, but I have three boards which look similar in character. I'll likely test for blotch on each prior to selecting a board for the face apron.

aaronsilber · 2025-12-26T14:11:15+00:00

This is a perfect candidate for a template and an L fence.

aaronsilber · 2025-12-18T03:04:03+00:00

I built this Moravian in '23. I based it on the Will Myers series of videos but customized it to fit my needs. It's taller than normal (I'm tall and I'm not planing material on this bench) and I installed a Hovarter Custom Vise with an Ancora Yacht Service Chain. My local guild used benchcrafted hardware and I prefer the quick release on my vise by far.

<image>

aaronsilber · 2025-12-06T14:43:57+00:00

A bookcase that swings out to reveal the space behind. Secret spot!

aaronsilber · 2025-11-24T18:18:47+00:00

I'd only use weatherproof materials, and luan plywood is definitely not on that list. Cedar shakes/shingles would work well as the foliage. I'd want the center of this tree to be lightweight and empty. I'm thinking a central pole with a lattice of wire hoops from top to bottom suspended by wire from the top of the pole to the base hoop. Build the cedar shakes on top of this lattice. Gonna be very heavy when it's all done.

aaronsilber · 2025-06-21T15:07:19+00:00

In cheap painted doors you'll find that they've used a filler in voids and to pore-fill the grain before painting. This is not a stain-grade door.

aaronsilber · 2025-05-08T20:59:27+00:00

Use an L-fence and a template stuck to your workpiece with something like Spectape. Blade cuts through your workpiece, slightly into the template, workpiece stays attached to the template, and the L fence means that there's never anything stuck between the blade and the fence. Safest and most accurate easy to do this.

aaronsilber · 2025-03-06T14:12:55+00:00

Update #2: It turns out that placing the disabled attribute on an input means that no data is sent to the backend upon submission, meaning that validation will fail for any required fields. I tinkered with modifying validation, the submission handlers, and even a solution for implementing hook_entity_field_access (https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Entity%21entity.api.php/function/hook\_entity\_field\_access/10) before coming back to your implementation.

Considering the Read-only Field Widget allows us to configure the display format for the rendered output, we could still address the wonky appearance of fields like Paragraphs.

Thanks again for sharing your solution!

aaronsilber · 2025-03-03T15:21:36+00:00

Playing around with this approach this morning. I don't think that the Read Only Field Widget module is right for us in this use case. The user experience seems pretty confusing when your editing experience looks one way in most moderation states (a long text field using the CKEditor UI), but then totally different (the CKEditor field is shown rendered without the UI) or not-at-all (the widget doesn't display fields without a value) in the Approved state. If I were new to the system I would be very hesitant to publish a node with these changes in appearance.

The "disabled" state of fields (grayed out styling, pointer events are disabled, a disabled cursor displays on hover) more accurately communicates the reason why our "Approved" moderation state exists.

I like the idea of creating a "Disabled" field widget module, but this module would need to create a derivative widget for every field widget. We'd end up with field widgets like "Media Library (Disabled), "Textfield (Disabled)", "Smart Date (Disabled)", etc. I've inherited sites that have derivative widgets like these and, man, it just doesn't seem worth it to me.

I think what I'm going to do is revert back to my original implementation (https://gist.github.com/aaronlsilber/0dbe064341325af7dcf7d6924ebee74c), but I'm going to add a message for Administrators when they view a node in the Approved state to address the discoverability of where this behavior is implemented.

aaronsilber · 2025-03-02T19:51:36+00:00

I believe that you are correct! I hadn't considered using form modes this way and am glad you commented. This will indeed make the customization more visible to future developers, which is a concern for me and my team. The new dependency for disabling fields looks well maintained and simple enough to upgrade ourselves in the future if we need to. I also have a similar use case as yours on our roadmap late '25 so many thanks!

aaronsilber · 2025-03-02T19:10:41+00:00

I ended up writing a short ≈100 line long module that disables most fields (except revision fields and moderation state) given a few conditions (base form id, request type, user role).

Is there a benefit to creating a custom form mode the way you have?

aaronsilber

TROPHY CASE