Update widgetController.js #62
Conversation
Added the widget id to be edited.
Realised by fix only sorted the editor, not the actual display of the widget as it was writing the ID twice into the DB row
|
Realised my fix only sorted editing, not display of widgets so edited it again |
|
For DB provider, you might need to remove widgets from the table like: |
|
I am seeing the issue on MS SQL not My SQL. Also to confirm I did run that command to delete the old extensiontype 1 data (from step 3 of the manual upgrade process) as instructed in the post you mention. The problems I have seen (and this pull request tries to address) is after all this is done. Just looks like the load for the editor is not getting the extension ID to edit |
|
Yep, indeed - this ajax call just to check if file exists and works fine with xml provider, but db actually runs all the way with executing sql and always returns error, thinking file doesn't exist. |
Initially logged on CodePlex but this is a better home
I have attempted an upgrade of a multiblog instance backed by MS SQL of BlogEngine 3.2 to 3.3.
I could access all my blogs, post etc. As expected there were no widgets show (as they have been deleted). So I....
If I try to edit a widget to alter the settings the popup dialog is the right size but empty.
If I checked the server logs I see the error
The parameterized query '(@blogid nvarchar(36),@etype int,@eid nvarchar(4000))SELECT Sett' expects the parameter '@eid', which was not supplied.I have had a look at the source for the widget editors controller and it seems the widget id is not being set on the Url as a query string entry. If I alter the line to
var customSrc = SiteVars.RelativeWebRoot + "Custom/Widgets/" + name + "/edit.cshtml?id="+ id;It works, but I am not sure of any knock on effects, not sure if this is the real cause of the issue.