I'm using Umbraco v7.2.8 but since upgrading from v7.2.7 there are error messages wherever my custom grid editor is used, although things render in the front end with no problem.
Trying to edit the custom grid editor produces the error in the screenshot below.
I upgraded LeBlender from 1.0.7 to 1.0.8 via a local package rather than Nuget, as it had been mentioned that this was missing a file. All went well in my development environment and I can now edit any of the grid editors and save the changes. However, when I tried the same thing with my staging environment the same problems still occurred. I can make changes to my custom grid editor, but when it comes to saving it I always get the same error.
In fact I get the same error if I try to make a change to any of the grid editors. I have had to edit the grid,editors.config file directly to turn off the 'Render in grid', because any changes cannot be saved, so at least the huge error message has stopped appearing in the content back office as well.
The message in Chrome Inspector reports a 404 for [siteDomain]/umbraco/backoffice/leblender/Helper/SaveEditorConfig
I have stopped the site in IIS and cleared the dependency cache a couple of times now and still no change.
The only issue I can see may have caused a problem during the upgrade of LeBlender was with permissions. The AppPlugins permissions were set to read only, so the errors were still appearing. Having changed the permissions, I installed LeBlender again, checked the LeBlender files had been updated in AppPlugins, stopped the site in IIS and deleted the ClientDependency folder. On checking the site again, the errors still occur.
I also know that one of the custom datatypes in my custom grid editor needs to be updated as the Guid has changed, but this error still occurs for each of the Grid Editors, not just my custom one and the hiccup, looking at the error, seems to be with the Headline config.
Has anyone got any suggestions on how I resolve this?
404 for SaveEditorConfig
Hi,
I'm using Umbraco v7.2.8 but since upgrading from v7.2.7 there are error messages wherever my custom grid editor is used, although things render in the front end with no problem.
Trying to edit the custom grid editor produces the error in the screenshot below.
As this seemed like the same issue as Jonas & Anton were having in https://our.umbraco.org/projects/backoffice-extensions/leblender/bug-reports/66482-404-error-when-using-render-in-grid, I followed the advice there.
I upgraded LeBlender from 1.0.7 to 1.0.8 via a local package rather than Nuget, as it had been mentioned that this was missing a file. All went well in my development environment and I can now edit any of the grid editors and save the changes. However, when I tried the same thing with my staging environment the same problems still occurred. I can make changes to my custom grid editor, but when it comes to saving it I always get the same error.
In fact I get the same error if I try to make a change to any of the grid editors. I have had to edit the grid,editors.config file directly to turn off the 'Render in grid', because any changes cannot be saved, so at least the huge error message has stopped appearing in the content back office as well.
The message in Chrome Inspector reports a 404 for [siteDomain]/umbraco/backoffice/leblender/Helper/SaveEditorConfig
I have stopped the site in IIS and cleared the dependency cache a couple of times now and still no change.
The only issue I can see may have caused a problem during the upgrade of LeBlender was with permissions. The AppPlugins permissions were set to read only, so the errors were still appearing. Having changed the permissions, I installed LeBlender again, checked the LeBlender files had been updated in AppPlugins, stopped the site in IIS and deleted the ClientDependency folder. On checking the site again, the errors still occur.
I also know that one of the custom datatypes in my custom grid editor needs to be updated as the Guid has changed, but this error still occurs for each of the Grid Editors, not just my custom one and the hiccup, looking at the error, seems to be with the Headline config.
Has anyone got any suggestions on how I resolve this?
Many thanks
Anne
is working on a reply...