[EMAIL PROTECTED] wrote:
We have a left_menu with many containers. We saw that offering an
actionMenu for each container is very bad for the performance, as all
the containers of this sub-pages are read and checked, whether they
are locked or not. So we decided not to show the actionMenu for each
container in this list, but only for the ones, which have a linked
page. For the direct pages the editor has to first access the page and
there he will get the buttons, where he can update or delete the page
and the container, where the page is included.
For the update this is no problem. It is only a problem for the
deletion, because after confirming the delete-popup, the current page
is reloaded in the javascript method CloseJahiaWindow. As the page has
been deleted this leads to an HTML error 404.
Do you have a suggestion, how we could change this behaviour, so that
either the parent page is loaded instead, or where we should place the
delete button, but still having a good performance.
Hmm... This is indeed a problem. The only way I see is to "duplicate"
all the Javascript code to have a special case in the case of a page
deletion. This means that when the user clicks on the DeleteContainer
link, just before the popup is opened, you should insert (with
Javascript) the URL of the parent page for reloading or something like that.
Regards,
Serge Huber.
