Unable to change Visual Plan back to Code because its invalid

[Guest]

I have a rather annoying issue.

One of my plans are stuck in limbo, I am unable to edit the plan because its invalid. (Think its because I changed one of the Call Templates)

Trying to change it from Visual to code is impossible, modifying it in Visual mode is impossible. And the Recent Errors displays the following error message:

An error occurred in the web application: Value cannot be null. Parameter name: literal
URL: http://localhost:82/plans/edit?raftId=1&planType=RoleConfigurationPlan&planName=SQL Server
Referrer: http://localhost:82/plans/edit?raftId=1&planType=RoleConfigurationPlan&planName=SQL Server
User: Express User
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36
Stack trace: at Inedo.Web.DP.DpPageBase.ProcessError(HttpContext context, Exception ex)
at Inedo.Web.Handlers.SimpleHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

How do I get the plan unlocked, so that I can fix it?

[Guest]

Hmm that's strange; we do have an outstanding bug with editing templates in the visual editor, so it might be related to that. We'll be shipping a fix on it quite soon.

But in the mean time, you can fix a "visually broken plan" using the following method:

1. Admin > Rafts > Export as Zip
2. Look in .zip file for the plan or template
3. Email us the template so we can reproduce bug
4. Delete plan or template from UI (for configuration plans, you can go to Plans > Configuration)
5. Create new plan/template, go to text mode, paste in text
6. Try to fix/identify issue in OtterScript (if possible? Hard to say since we don't know what it is right now)

[Guest]

Hi Alana

I am still having this issue with version 1.1.3 (Build 7)

[Guest]

This is, unfortunately, a new glitch related to the call template statement in the visual editor. We'll be fixing it in next maintenance release.

FWIW - we're also looking to add a "undo" mechanic that should, at the very least, allow for recovery to previous states when the visual editor creates an invalid model of a plan/OtterScript.