Does that mean I can deploy 1.2 into production?

 


Thank you,
 
Steve Schofield
Windows Server MVP - IIS
http://www.iislogs.com/steveschofield
 
http://www.IISLogs.com <http://www.iislogs.com/> 
Log archival solution
Install, Configure, Forget

 

From: Renaud Paquay [mailto:[email protected]] 
Sent: Monday, June 13, 2011 9:04 PM
To: [email protected]
Subject: RE: Orchard 1.2 RC

 

Ok, I misunderstood your original email: issues a) and b) is actually only
one issue, which, as I mentioned, was fixed in the final 1.2 release.

 

For 3, let us know if you run into it again (log files are sometimes
helpful, because they contains pretty all errors Orchard ran into, and it
can be a series of errors which leads to the last reported one).

 

Thanks,

Renaud

 

From: Steve Schofield [mailto:[email protected]] 
Sent: Monday, June 13, 2011 5:17 PM
To: [email protected]
Subject: RE: Orchard 1.2 RC

 

HI,
 
#1 - I attached a log from the latest command line error, stopping w3svc,
running the command worked running feature enable Orchard.Recipes

#3 - I don't have the original log file, I reverted my site back to original
environment to work on my site.   The event log entry I attached was the
complete unhandled exception logged.  When I ran through the process again,
the error didn't come up.  Could be a red-herring or the method of which I
was trying.  I tried again and didn't get the error.   Anywho, an IISReset
fixed the issue.

 

Misc - the version shows 1.1.3.0 instead of 1.2 RC.  The formatting of my
site was clean the 3rd time.  The last couple times the CSS was all messed
up.  

 

Hope this helps.

 

 

Steve Schofield
Windows Server MVP - IIS
http://www.iislogs.com/steveschofield

 

From: Renaud Paquay [mailto:[email protected]] 
Sent: Monday, June 13, 2011 4:06 PM
To: [email protected]
Subject: RE: Orchard 1.2 RC

 

Hi Steve,

 

a)      Command line errors with log file conflict: these errors are
actually a bit of a misnomer, they should be recoverable (as the last
message says "Attempting
[C:\inetpub\iislogs3.com\App_Data\Logs\orchard-error-1] instead."). You are
correct these errors don't happen is the IIS worker process is stopped, but
I am surprised that you got a "Error starting up Orchard command line host"
message right after that (orchard.exe should still start properly). Does
this still reproduce for you?

b)      Command line error with compilation ("The type or namespace name
'FrameworkName' could not be found (are you missing a using directive or an
assembly reference?)")): This is a bug which was fixed last week:
http://orchard.codeplex.com/workitem/17728

c)       Errors in the event log: I have never seen this before. Can you
check the Orchard log files (~/App_Data/Logs) to see if there is more
detail?

 

Thanks,

Renaud

 

 

From: Steve Schofield [mailto:[email protected]] 
Sent: Saturday, June 11, 2011 9:23 PM
To: [email protected]
Subject: RE: Orchard 1.2 RC

 

I've tried the upgrade two times and here are some observations.  My entire
site was running locally on my "staging" machine with 1.1.3.0 before
attempting the upgrade.  I couldn't get the upgrade to go smoothly.

 

1)      I'd suggest using WinMerge (http://winmerge.org free tool) to
compare the Themes, Modules folder.  That made it super simple to tell what
needed to be copied from existing site to new folder with 1.2 RC

2)      If you have IIS running, you need to stop w3svc before running
Orchard.exe  After I stopped IIS (net stop w3svc), I was able to run the
Enable command

3)      I use the Contoso theme, after the upgrade my site running locally
didn't have the theme, but could log into the dashboard

a.       Inside the dashboard, the current version still shows 1.1.3.0

b.      I show all *new* modules except BlogML (1.2.0) (I have 35 modules
installed)

c.       No modules showed needing to be updated

4)      I got an error when trying to load the first time, I needed to
perform an iisreset.  Event Log error attached.

 

I attached the errors.  Hope this helps.


Thank you,
 
Steve Schofield
Windows Server MVP - IIS
http://www.iislogs.com/steveschofield
 
http://www.IISLogs.com <http://www.iislogs.com/> 
Log archival solution
Install, Configure, Forget

 

From: Bertrand Le Roy [mailto:[email protected]] 
Sent: Tuesday, June 07, 2011 4:18 PM
To: [email protected]
Subject: Orchard 1.2 RC

 

Hi all,

We have a new version available for you. It's not quite 1.2 officially, just
what we believe could be it. We are making it available early to give you an
opportunity to catch any last minute blocking issue over the next few days.

Upgrading an existing site can be done following the instructions from this
page:
http://orchardproject.net/docs/Upgrading-a-site-to-a-new-version-of-Orchard.
ashx

The download can be found here:
http://orchardproject.net:8080/repository/download/bt9/2994:id/MsDeploy/Orch
ard.Web.1.2.391c0dc6b3e6.zip (web site)
http://orchardproject.net:8080/repository/download/bt9/2994:id/Source/Orchar
d.Source.1.2.391c0dc6b3e6.zip (source code) 

For those of you using a clone of the repository, you can sync to change set
391c0dc6b3e6 from the integration branch.

Please report any issue you find in the Issue Tracker, and don't forget to
mention in your description that you are using this version.

This release is mainly about bug fixes, performance improvements, but not
new features, except for editable creation dates (which we now use
everywhere by the way), or debugger visualizer for shapes (only in full
trust but I think that is still going to make a few people happy).

Please let us know what you think.

Bertrand on behalf of the core team

 

--- 
You are currently subscribed to orchard-discuss as: [email protected]. 
To unsubscribe send a blank email to
[email protected]. 

--- 
You are currently subscribed to orchard-discuss as: [email protected]. 
To unsubscribe send a blank email to
[email protected]. 

--- 
You are currently subscribed to orchard-discuss as: [email protected]. 
To unsubscribe send a blank email to
[email protected]. 



---
You are currently subscribed to orchard-discuss as: [email protected].
To unsubscribe send a blank email to [email protected].

Reply via email to