Programmatically Added Web Part Issues - Powershell

Question

Hello!
I have been doing quite a bit of research on this for the last few days but so far to no avail. What I am trying to do is use a powershell script to create a Content Editor Web Part on a basic sharepoint site created using the Team Site template. 
The issue I'm running into is when I use the script I have to add a new web part to the "wpz" zone. The webpart gets created properly and exists in the webparts collection however it does not show up on the page. I can bind to the webpart through
powershell and can see that the visible property is set to true while the hidden property is false. The webpart is not closed it simply doesn't show up. 
When I add the webpart to another zone it shows up properly however as soon as you edit the page the webpart disappears. However this only happens while the page is in edit mode. As soon as you save the page the programmatically added webpart immediately
shows back up in the zone it's supposed to be in. 
I was wondering if anyone else had ever experienced this specific issue and if there is anything I can do to fix it.
The environment is a development box running Microsoft Server 2012 and is hosting Sharepoint 2013. 
Thanks!

Answer 1

Hello Patrick,
Thanks for your response. The script I am using is in the following code block:
$SiteUrl = "http://maddevsp01.btdev.net/my/personal/14736"
$WebUrl = "http://maddevsp01.btdev.net/my/personal/14736"
function main() {
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
$OpenWeb = Get-SPWeb $WebUrl
$OpenSite = Get-SPSite $SiteUrl
$file = $OpenWeb.GetFile("$WebURL/SitePages/Home.aspx")
$WebPartManager = $file.GetLimitedWebPartManager([System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared)
Add-ContentEditorWebPart "$WebURL" "$WebURL/SitePages/Home.aspx" "wpz" 12 "Test" "Test webpart"
$OpenWeb.Dispose()
function Add-ContentEditorWebPart($SiteURL, $pageUrl, $webpartzone, $index, $title, $content)
$site = new-object Microsoft.SharePoint.SPSite($SiteURL)
$web=$site.OpenWeb()
$webpartmanager = $web.GetLimitedWebPartManager($pageUrl, [System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared)
$webpart = new-object Microsoft.SharePoint.WebPartPages.ContentEditorWebPart
$webpart.ChromeType = [System.Web.UI.WebControls.WebParts.PartChromeType]::Default;
$webpart.Title = $title
$docXml = New-Object System.Xml.XmlDocument
$contentXml = $docXml.CreateElement("Content");
$contentXml.set_InnerText($content);
$docXml.AppendChild($contentXml);
$webpart.Content = $contentXml;
$webpartmanager.AddWebPart($webpart, $webpartzone, $index);
$web.Close()
$site.Close()
function Get-SPSite([string]$url) {
New-Object Microsoft.SharePoint.SPSite($url)
function Get-SPWeb([string]$url) {
$SPSite = Get-SPSite $url
return $SPSite.OpenWeb()
$SPSite.Dispose()
main
I was investigating further after posting yesterday and used powershell to bind to a webpart created by the script and a webpart I created using the sharepoint interface. Then I exported all the properties and their values to two different text files and
used winmerge to compare the differences to see if there was a setting I was missing in the script or something akin to that. However when I did the comparison the only differences between the two were the following values: Title, Description, PartOrder, ID,
StorageKey, EffectiveTitle, DisplayTitle, ZoneIndex, ClientID, and UniqueID. All of which you would expect to be different. All other settings are exactly the same on both webparts.
I am at a complete loss as to what this issue might be.
Kindest Regards,
-Zach