Skip to main content

How to child proof a fireplace

DIY - Do it yourself fireplace child guard

Our wonderful 8.5 month old Sofia has become a crawling race car with an untamed thirst for exploration. And so with the cold nights approaching we needed to child proof the fireplace. This however proved to be more difficult than would reasonably expect, I've checked the local Toys "R" Us, Walmart, and even a Canadian Tire with no success for a ready to use product.

Internet search was more fruitful and returned a few online stores one could order from, however in all honestly they didn't look too sturdy to me. So I build my own relatively quickly and inexpensively.

Materials needed is a privacy plastic lattice - the smallest hole pattern - a few screws and anchors; tools needed are a drill, and a handsaw if you don't have the lattice cut at the store - that’s it. The construction consits of screwing the lattice into the wall and the final product is easiest explained through following pictures.

Feel free to +1 this post if you found it helpful.

Comments

  1. This is a great idea. I'm also looking for ideas on child-proofing my fireplace and I'm surprised at the lack of options. Thanks for sharing!

    ReplyDelete
  2. Are you still able to use the fireplace with this lattice?

    ReplyDelete
    Replies
    1. Absolutely, that was the whole point of this project :).

      Delete
  3. Where did you find this color lattice?

    ReplyDelete
  4. Replies
    1. I personally would still drill between the brick into the mortar to ensure it's sturdy enough. When the guard is no longer needed I would then use color matched grout to fill in the holes.

      Delete
  5. Looks great! You didn't have any issue with it melting?

    ReplyDelete
    Replies
    1. Was concerned about that too but there was no issues whatsoever.

      Delete
  6. How did you measure the amount of lattice you would need?

    ReplyDelete
    Replies
    1. I dry fit it then was going to cut it down but found full size piece worked best in my situation. If I had to try to measure I would use a piece of string laid in a convex pattern on the floor.

      Delete

Post a Comment

Popular posts from this blog

Storing passwords in PuTTY

How to save SSH username/password for auto login in PuTTy The answer is you can't do it...at least in plain PuTTy. However there is an awesome fork with that let's you store the username and password and other additional features called KiTTy.



So grab yourself a copy and +1 this if you do, thanks.

Duplicate value found: duplicates value on record with id: <unknown>.

System.DmlException: Insert failed. First exception on row 0; first error: DUPLICATE_VALUE, duplicate value found: <unknown> duplicates value on record with id: <unknown>.The above error is triggered in the database layer and caused by a trigger or workflow outside of your main code of block that is bubbling this exception. This is rather difficult to track down especially if you are unfamiliar with the code, I am sharing my procedure in the hopes this saves you time - if you find this helpful drop me a line or follow me on twitter @danielsokolows. This error is caused by unique field constraint on the object, so the first step is to examine the object and locate the API names of all unique fieds. You can do this through SF direclty 'Setup < Customize &lt <object being inserted> &lt Fields' or by downloading the `src/objects` metadata information and searching for <unique>; I preffer the latter and actually download ALL matadata information f…

Softeher 'Error occurred. (Error code: 2)' sollution

Protocol error occurred. Error was returned from the destination server.The Softether server by default to run on port 443, if you server also hosts normal https then 443 is already taken and so Softether can't bind to it. When you run `vpncmd` it attempts to connect, find an active port, but of course fails with 'Protocol error occurred. Error was returned from the destination server.' because it's not actually connecting to the vpn server. By default Softether also listens on 992, 1194, and 5555 so the sollution is to modify specify `localhost:5555` when executing the `vpncmnd`. If this has helped you feel free to comment or follow me on twitter @danielsokolows.