For some reason, the backend is refusing to create new documents.
Not sure when it started, but when I noticed it, the database was completely full (~0.3MB left).
I've made space available in the db again (~35MB), but the issue persist.
I can create nodes just fine if I use my own controller. The issue only appears in the backend.
I've cleared all possible caches.
Running Umbraco 7.2.4.
This is the error I get:
http://localhost:52099/umbraco/backoffice/UmbracoApi/Content/PostSave Failed to load resource: the server responded with a status of 500 (Internal Server Error)
angular.min.js?cdv=177235485:63 TypeError: data.indexOf is not a function
at umbraco.services.js?cdv=177235485:6855
at umbraco.services.js?cdv=177235485:6936
at angular.min.js?cdv=177235485:100
at o (angular.min.js?cdv=177235485:80)
at o (angular.min.js?cdv=177235485:80)
at angular.min.js?cdv=177235485:81
at Object.e.$eval (angular.min.js?cdv=177235485:92)
at Object.e.$digest (angular.min.js?cdv=177235485:90)
at Object.e.$apply (angular.min.js?cdv=177235485:92)
at j (angular.min.js?cdv=177235485:101)(anonymous function) @ angular.min.js?cdv=177235485:63
I've encountered the error before, but only with datatypes that were storing more data than nvarchar could handle (fixed by setting to TEXT).
But this is happening on all documents I throw at it - even completely raw document types.
I've actually come across the same error, but mine occurs when I try to save/publish a node after editing or creating anything.
I created the site in Visual Studio and migrated the database to one of our SQL databases and updated the connection string. It works fine locally when its connected via Visual Studio, but when I go to our website to update the content connected to the same database, I can't make any changes.
I want to say it's a permissions thing, but I'm a Frontend developer and shouldn't be playing in this stuff. :P
I had received help from one of our application developers, and he just checked a box for the user I created for that database to be an "owner" using SQL Server Management Studio and then it worked. I can't say I fully understood the problem or the solution, but mine works now too! Thanks!
Can't create new documents in backend..
Hi,
For some reason, the backend is refusing to create new documents.
Not sure when it started, but when I noticed it, the database was completely full (~0.3MB left).
I've made space available in the db again (~35MB), but the issue persist.
I can create nodes just fine if I use my own controller. The issue only appears in the backend.
I've cleared all possible caches.
Running Umbraco 7.2.4.
This is the error I get:
I've encountered the error before, but only with datatypes that were storing more data than nvarchar could handle (fixed by setting to TEXT).
But this is happening on all documents I throw at it - even completely raw document types.
Any help would be much appreciated :)
I've actually come across the same error, but mine occurs when I try to save/publish a node after editing or creating anything.
I created the site in Visual Studio and migrated the database to one of our SQL databases and updated the connection string. It works fine locally when its connected via Visual Studio, but when I go to our website to update the content connected to the same database, I can't make any changes.
I want to say it's a permissions thing, but I'm a Frontend developer and shouldn't be playing in this stuff. :P
Hi,
I believe we found the solution to that problem - and it had nothing to do with the database.
We had changed a snip of code in the Publishing event, and it was causing exceptions when creating new documents from the backend.
Maybe you should have a look at your events too?
Thanks for the reminder Crono,
Why didn't I think of that! Same problem ended up being a custom publish event that I had written.
I had received help from one of our application developers, and he just checked a box for the user I created for that database to be an "owner" using SQL Server Management Studio and then it worked. I can't say I fully understood the problem or the solution, but mine works now too! Thanks!
is working on a reply...