<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:windowtext}
span.EmailStyle18
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
-->
</style><style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" lang="EN-US" link="blue" vlink="purple">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi Brad,<br>
<br>
Thanks for your reply. Hearing you couldn't replicate it made me think it might be an issue with my local plugins; turning them off solved the problem. Guess I have some cleaning up to do in there...<br>
<br>
thanks again! I've noticed a few other, more minor layout issues with the new stylesheets, if you happen to want a list of those. -k<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF481610"><font face="Tahoma" color="#000000" size="2"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org [archivesspace_users_group-bounces@lyralists.lyrasis.org] on behalf of Brad Westbrook [brad.westbrook@lyrasis.org]<br>
<b>Sent:</b> Thursday, April 02, 2015 5:31 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi, Kevin,</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for reporting this problem. Unfortunately, I have not been able to replicate it. I tried to using two resource records in the sandbox:
<a href="http://sandbox.archivesspace.org/resources/6/edit#tree::resource_6" target="_blank">
http://sandbox.archivesspace.org/resources/6/edit#tree::resource_6</a> and <a href="http://sandbox.archivesspace.org/resources/13/edit#tree::resource_13" target="_blank">
http://sandbox.archivesspace.org/resources/13/edit#tree::resource_13</a>.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Perhaps there are some specific steps that trigger it. Can you provide any more details?
</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Kevin Clair<br>
<b>Sent:</b> Wednesday, April 01, 2015 5:15 PM<br>
<b>To:</b> Archivesspace Users Group (archivesspace_users_group@lyralists.lyrasis.org)<br>
<b>Subject:</b> [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Hello,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I’ve been testing v1.2.0 this week and noticed while editing records that the columns aren’t aligning properly, with the result being that the shortcuts on the left hand side are overlaying the actual editing form and making it difficult
to use. I’m attaching a screen shot to show what it looks like. So far I’ve noticed this with Resources and Archival Objects; not sure if it happens across the board or not. -k</p>
</div>
</div>
</div>
</div>
</body>
</html>