<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.method.me/cs/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Method:Classic General Q&amp;amp;A</title><link>http://forums.method.me/cs/forums/13.aspx</link><description>Ask technical support questions, how do I? Questions... Or anything else you want to know from the Method Team and other Method users.</description><dc:language>en</dc:language><generator>CommunityServer 2007.1 SP2 (Build: 31113.47)</generator><item><title>Re: Screen display issue on some Method accounts</title><link>http://forums.method.me/cs/forums/thread/5405.aspx</link><pubDate>Sun, 06 Mar 2011 16:38:00 GMT</pubDate><guid isPermaLink="false">3393c1ec-311b-4812-96cb-ad8c611bba4f:5405</guid><dc:creator>jnoneiliv1</dc:creator><slash:comments>0</slash:comments><comments>http://forums.method.me/cs/forums/thread/5405.aspx</comments><wfw:commentRss>http://forums.method.me/cs/forums/commentrss.aspx?SectionID=13&amp;PostID=5405</wfw:commentRss><description>&lt;p&gt;Good job on the fix!&lt;/p&gt;
&lt;p&gt;The innovation on Method is worth a few glitches and keeping an identical but separate test environment to control releases is always a challenge.&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;James&lt;/p&gt;</description></item><item><title>Re: Screen display issue on some Method accounts</title><link>http://forums.method.me/cs/forums/thread/5404.aspx</link><pubDate>Sat, 05 Mar 2011 17:06:59 GMT</pubDate><guid isPermaLink="false">3393c1ec-311b-4812-96cb-ad8c611bba4f:5404</guid><dc:creator>Method_Paul</dc:creator><slash:comments>0</slash:comments><comments>http://forums.method.me/cs/forums/thread/5404.aspx</comments><wfw:commentRss>http://forums.method.me/cs/forums/commentrss.aspx?SectionID=13&amp;PostID=5404</wfw:commentRss><description>&lt;p&gt;I wanted to provide an update and an&amp;nbsp;apology.&lt;/p&gt;
&lt;p&gt;Everything was back to normal yesterday at 5:10 PM&amp;nbsp;Eastern time.&amp;nbsp; The issue started about 3pm,&amp;nbsp;so&amp;nbsp;the disruption lasted 2 hectic&amp;nbsp;hours before we were able to figure out what went wrong and how to rectify it.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Who was affected?&lt;/strong&gt; Accounts that signed in to Method between 3pm and 5:10pm Eastern.&amp;nbsp; Accounts that were already signed in and using Method likely didn&amp;#39;t not see the problem.&amp;nbsp; This only happened to some standard QuickBooks and CRM screens.&amp;nbsp; Custom screens were not affected.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;So, what happened?&lt;/strong&gt;&amp;nbsp;It was a failure on our side in our quality assurance (QA) process.&amp;nbsp; We didn&amp;#39;t actually do an update to the production web servers yesterday, although I know it appeared that way to affected accounts.&amp;nbsp; What happened is actually a bit more complicated.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Complicated and technical overview of what happened&lt;/strong&gt;: We&amp;#39;ve been working on an update since December that brings in features to calendars, the report designer, HTML editors, enhanced Safari and Chrome compatibility, and bunch of other big changes.&amp;nbsp; It has been going through our QA process for the last month, which entails slowly moving it through QA stages.&amp;nbsp; All but the final stage are on separate test environments that have no impact on the production servers.&amp;nbsp; Yesterday, however, we moved the update to the final test web server which shares one resource with the production web&amp;nbsp;servers: the production &lt;em&gt;database&lt;/em&gt; server.&amp;nbsp; When we published our standard Method screens on our test environment, a software bug caused the database server to get updated in a way that broke compatibility to production versions of the standard Method screens using the same database server.&amp;nbsp; In hindsight, our development team&amp;nbsp;looking at the code can&amp;#39;t believe we made such a mistake....but we did.&amp;nbsp; It took us about an hour to figure out what had occurred, and another hour to write, test and run a program that reversed the new changes to the database.&lt;/p&gt;
&lt;p&gt;Our sincere apologies for the disruption.&amp;nbsp;We are evaluating our QA process to see how we can tighten it to make sure this doesn&amp;#39;t happen again.&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>Screen display issue on some Method accounts</title><link>http://forums.method.me/cs/forums/thread/5402.aspx</link><pubDate>Fri, 04 Mar 2011 21:07:16 GMT</pubDate><guid isPermaLink="false">3393c1ec-311b-4812-96cb-ad8c611bba4f:5402</guid><dc:creator>Anonymous</dc:creator><slash:comments>0</slash:comments><comments>http://forums.method.me/cs/forums/thread/5402.aspx</comments><wfw:commentRss>http://forums.method.me/cs/forums/commentrss.aspx?SectionID=13&amp;PostID=5402</wfw:commentRss><description>&lt;p&gt;Hi Method Community,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It has been brought to our attention that some Method accounts are unable to see their screens properly. &amp;nbsp;We are now aware of the situation and will update you once we have more news.&lt;/p&gt;
&lt;p&gt;To stay updated with our status, follow us on twitter&amp;nbsp;&lt;a href="http://twitter.com/followmethod"&gt;http://twitter.com/followmethod&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We apologize for any in convince this might have caused. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Danny&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item></channel></rss>