As for example when creating a new document... when using that code ! there is no result, after the handling, it is still redirect to the editcontent.aspx page.
I'm really trying to find some solution to have more userfriendly edit pages as our customers are completely novice, they do not need all properties to be displayed and we need some additional "edition" functionalities to improve the document translations. For now I have some action handlers that can by example synchronize new documents in different nodes of my languages subsistes... Some properties should not be editable in the translatable documents by example, only things that need to be translated should be displayed.
Some other properties should be changed through clearly displayed actions...
Is this possible within the handler ?
Within the application base ?
Is it possible to hide nodes from the content tree through the applicationbase ?
Handler to synchronize items to a subsite of different language (by example when creating a news item for EN, the page is automatically created in FR and NL)
LL
New Content Editor
Handler to be able to change the default content editor by redirecting to a custom page. This will enable more userfriendly interfaces by stripping unuseful data for content creator, reorganizing, giving more actions. And a way for translators to access only translatable fields with a view on the original data.
LL
Hiding Nodes from the content tree
The ability to hide nodes from the content tree should help us to show the effective “navigable content tree”. For company **** by example a lot of the children nodes are related to the content of the parent node, and some other nodes are the content. If we could find a way to hide those nodes, and make them editable through the content editor, we will win in usability, as the editor will only see the logical navigation structure of the site.
Bon !!! Nobody here in the umbraco space want to replace the editcontent.aspx page ? It sounds incredible !!!
I could override the existing one, but it's not upgrade safe ! I could create a new one, and redirect to the old one, or my new editor... But I guess I could miss some logics ! I'm still wondering how difficulet it should be to have a OnEdit event handler in the applicationbase to tell what page we wants to use for editing so we can override the default one !
Bon could I by example for some documents, hide the built-in EDIT option, and replace it by my own one ? but this doesn't solve completely my problem, in the case we are creating a document. Or I will have to replace the create flow with my own also ?
We noticed that the topic ‘Replacing the editContent.Aspx’ you created in the Umbraco Community Forum does not have a post marked as a solution. If a post helped answer your question or resolve your issue please mark it as a solution so others can quickly find it. You can view the topic and any posts here http://our.umbraco.org/forum/core/general/18775-Replacing-the-editContentAspx.
Replacing the editContent.Aspx
I'm trying the action handlers, and I was wondering if I could replace the defaut editContent.Aspx for some documents.
void
Document_New(Document doc, NewEventArgs e) {
umbraco.BasePages.BasePage.Current.ClientTools.ChangeContentFrameUrl(
string.Concat("StupidPage.aspx?id=" , doc.Id));
}
As for example when creating a new document... when using that code ! there is no result, after the handling, it is still redirect to the editcontent.aspx page.
I'm really trying to find some solution to have more userfriendly edit pages as our customers are completely novice, they do not need all properties to be displayed and we need some additional "edition" functionalities to improve the document translations. For now I have some action handlers that can by example synchronize new documents in different nodes of my languages subsistes... Some properties should not be editable in the translatable documents by example, only things that need to be translated should be displayed.
Some other properties should be changed through clearly displayed actions...
Is it possible to hide nodes from the content tree through the applicationbase ?
Module
Remark
Auth.
Pr.
More Handlers
Handler to synchronize items to a subsite of different language (by example when creating a news item for EN, the page is automatically created in FR and NL)
LL
New Content Editor
Handler to be able to change the default content editor by redirecting to a custom page. This will enable more userfriendly interfaces by stripping unuseful data for content creator, reorganizing, giving more actions. And a way for translators to access only translatable fields with a view on the original data.
LL
Hiding Nodes from the content tree
The ability to hide nodes from the content tree should help us to show the effective “navigable content tree”. For company **** by example a lot of the children nodes are related to the content of the parent node, and some other nodes are the content. If we could find a way to hide those nodes, and make them editable through the content editor, we will win in usability, as the editor will only see the logical navigation structure of the site.
LL
Here my wish list :-)
I'm so impressed by the reactivity on those forums :-)
Bon !!! Nobody here in the umbraco space want to replace the editcontent.aspx page ? It sounds incredible !!!
I could override the existing one, but it's not upgrade safe ! I could create a new one, and redirect to the old one, or my new editor... But I guess I could miss some logics ! I'm still wondering how difficulet it should be to have a OnEdit event handler in the applicationbase to tell what page we wants to use for editing so we can override the default one !
Bon could I by example for some documents, hide the built-in EDIT option, and replace it by my own one ? but this doesn't solve completely my problem, in the case we are creating a document. Or I will have to replace the create flow with my own also ?
We noticed that the topic ‘Replacing the editContent.Aspx’ you created in the Umbraco Community Forum does not have a post marked as a solution.
If a post helped answer your question or resolve your issue please mark it as a solution so others can quickly find it. You can view the topic and any posts here http://our.umbraco.org/forum/core/general/18775-Replacing-the-editContentAspx.
Who's fault ? :-)
is working on a reply...