New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Templates deleted #292
Comments
Seems to be an upgrade issue. Probably fixed by Friday. |
Let me know if I can help test on my install. |
Note that after looking into your issue again, it's not the upgrade issue I thought it was, it's simply invalid data. Just remove the template-definition and create a now one - and you should be good to go in about 60 seconds. Will close this now. |
Remove the template definition? Going to the templates section is what generates the error. Let me fully explain: Imported default 2sxc apps/content http://screencast.com/t/hzhUeco2yek1 So do I need to go through the database and remove these definitions? |
No, not in the DB. Now just add a &scope=2SexyContent-System, so it will be something like here you should be able to clean up your entity. |
Could not find a secret view and the only iframe i see is the dumb one in the getting started tab (whole other issue in itself that I don't quite understand). I'm going to try to export/ uninstall/ reinstall and see if this will work. |
I was able to track down the URL to go to the entities for the templates/views. The iframe through me off and I just modified the URL from the tab. So going forward, if I delete a view in the admin, I should go to this secret page and delete the associated entity? |
@ech01 that's correct. Deleting that entity in the entity-admin is the same as deleting a view/template in the normal admin. |
Ran into this issue with 7.22 and was able to solve the issue thanks to this thread. However I made the same bonehead mistake and we are now in 8.1.2. That requires a different method I believe so I used the one here: http://2sxc.org/en/Blog/post/advanced-dynamic-data-content-understanding-content-type-scopes. That is the correct method, right? That does get me to what appears to be the Entity Admin, but when I click 2SexyContent-Template I get back 'Had an error talking to the server status 500'. Looking at the Console from Chrome I can see that it's trying to reach: http://www.cui.edu/desktopmodules/2sxc/api/eav/entities/GetAllOfTypeForAdmin?appId=2&contentType=2SexyContent-Template I appreciate any direction here. We are stuck and I am trying to rollout some new features for our client. |
I believe it has to do with Null-Values which were officially not allowed, but internally necessary for special stuff like templates & content-groups. I think we actually implemented a fix for this is 08.01.03. So I think you're in luck - update to 08.01.03 and it should work :) |
Thanks for writing. Well I tried out 8.1.3 on the staging server but I am still getting the same error messages. Are there any stored procs or other tools in the 2sxc kit that I can use to delete the renegade View/Template? I am willing to dig in but I don't want to make it worse. Trying to get more detailed error messages. Firefox gives me these message but it appears the first part (contentTypeListController/vm.changeScope) appears before I even click on 2SexyContent-Template:
|
Note: I've created a new issue to include pdb-files in the future which will help in giving line-numbers in error messages - #649 It must be a data-delivery problem. Basically you see the
which obviously means, the server wasn't able to deliver the data properly. It usually means that there is a serialization problem - the server tried to make a JSON out of the data but ran into a problem - often an unexpected "object doesn't exist" or similar. There are a few ways to continue, but a simple one would be to just go into the DB and mark this item as deleted. Steps should be: Find out which template-ID you are talking about, by going into admin > views > click on the template. Even though you see an error, you should see the template id (which is also the entityid) in the url, like this http://2sxc.org/en/blog/mid/3002/ctl/edittemplate/appid/78/templateid/**6881**?popUp=true Then you should go into sql and find this entity, something like this
Then set the ChangeLogDeleted to the same number as ChangeLogModified. Don't use a random number, please use this changelogmodified. In the eyes of 2sxc / eav, this item is now deleted. Basically the entity is now deleted. You'll need to reload your cache. |
Thanks for your help Jungleboy. You guys Rock! I wasn't able to see the View tab to get the EntityID because this null value issue causes that whole View tab to blow up. So I reversed engineered your table structure and built an SQL to find cases where a ContentType was deleted while a referencing View/Template still lives. Then using your instructions I copied the ChangeLogModified value to the ChangeLogDeleted for that naughty Entity. That worked! We're back in black. Here is my SQL: /*
*/ SELECT e.[EntityID], v.[AttributeID], v.[Value], a.[Name], a.[Scope], a.[AttributeSetID], |
Great - love to help :) A word of warning to anybody copy/pasting the code above - don't just copy-paste, use your brains :). Your ID-Numbers will be different :) |
See: https://sexycontent.codeplex.com/workitem/1877
The text was updated successfully, but these errors were encountered: