<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Nick Hamlin</title><link href="https://world.optimizely.com/blogs/nick-hamlin/" /><updated>2024-07-30T16:31:07.0000000Z</updated><id>https://world.optimizely.com/blogs/nick-hamlin/</id><generator uri="https://world.optimizely.com/blogs/nick-hamlin/" version="2.0">Optimizely World</generator><entry><title>Bug Fixing: Lazy loaded property value is not supported by the current property instance</title><link href="https://blogs.perficient.com/?p=366611" /><id>https://blogs.perficient.com/?p=366611</id><published>2024-07-30T16:28:35.0000000Z</published><updated>2024-07-30T16:31:07.0000000Z</updated><author><name>nick.hamlin@perficient.com</name></author><category term="Blog post" /><summary type="html">While upgrading from CMS v11 to v12, we ran into an error that read &amp;#8220;Lazy loaded property value is not supported by the current property instance&amp;#8221;. Unfortunately, the stack trace didn&amp;#8217;t really say what the problem was. Here is that stack trace: System.InvalidOperationException: Lazy loaded property value is not supported by the current property instance [&amp;#8230;]</summary></entry><entry><title>Uploading blobs to Optimizely DXP via PowerShell</title><link href="https://blogs.perficient.com/?p=358010" /><id>https://blogs.perficient.com/?p=358010</id><published>2024-03-01T05:51:48.0000000Z</published><updated>2024-03-01T06:01:33.0000000Z</updated><author><name>nick.hamlin@perficient.com</name></author><category term="Blog post" /><summary type="html">We had a client moving from an On-Prem v11 Optimizely instance to DXP v12 and we had a lot of blobs (over 40 GB) needing uploading to DXP as a part of the conversion. &amp;#160; This was my first experience doing both a version and environment upgrade and I leaned heavily on Optimizely support to [&amp;#8230;]</summary></entry><entry><title>Local HTTPS for Optimizely, IIS, and Kestrel using certificates (Pt 2)</title><link href="https://blogs.perficient.com/?p=342691" /><id>https://blogs.perficient.com/?p=342691</id><published>2023-08-15T22:15:37.0000000Z</published><updated>2023-11-15T23:31:08.0000000Z</updated><author><name>nick.hamlin@perficient.com</name></author><category term="Blog post" /><summary type="html">In part 1 of this two-part blog series on securing your local development with HTTPS and Self-Signed Certificates, I described how to create a local self-signed certificate. In this part, I&amp;#8217;ll explain how to use that certificate to safeguard your development environment and make it even more similar to QA &amp;#38; Production. Bind the certificate [&amp;#8230;]</summary></entry><entry><title>Local HTTPS for Optimizely, IIS, and Kestrel using certificates (Pt 1)</title><link href="https://blogs.perficient.com/?p=341608" /><id>https://blogs.perficient.com/?p=341608</id><published>2023-07-31T18:40:28.0000000Z</published><updated>2023-11-15T23:31:10.0000000Z</updated><author><name>nick.hamlin@perficient.com</name></author><category term="Blog post" /><summary type="html">Wasn&amp;#8217;t it around 2006 when HTTPS started becoming popular? You&amp;#8217;d go to a secure page and almost always see a message saying, &amp;#8220;This page contains both secure and nonsecure items. Do you want to display the insecure items?&amp;#8221; 1 &amp;#8220;Helpful&amp;#8221; people online posted how to disable the error. Then browsers got smarter and just stopped [&amp;#8230;]</summary></entry></feed>