[TYPO3-core] RFC #4885: AJAX pagetree update could be used when a new page is created

[Ingmar Schlecht]

Hmm, I don't get the strange bug any more, but for some reason the page 
just refreshes like in the old days instead of doing an AJAX request. 
The patch applied just fine though.

cheers
Ingmar

Benjamin Mack schrieb:
> Hey Ingmar,
> 
> ok. I needed to refine some of the paths / parameters in the Tree 
> object. Try it out with the new patch. Works like a charm for me.
> 
> Enjoy!
> 
> Ingmar Schlecht wrote:
>> Awesome! I've been waiting for this.
>>
>> But there seems to be a problem with the patch: I get an empty list 
>> module in the tree-frame after renaming a page.
>>
>> cheers
>> Ingmar
>>
>> Benjamin Mack schrieb:
>>> Hey guys,
>>>
>>> this is a SVN patch request.
>>>
>>> Branches: trunk only
>>>
>>> BT reference: http://bugs.typo3.org/view.php?id=4885
>>>
>>> Problem:
>>> When a new page is created, the page tree is triggered to be 
>>> refreshed by a javascript call: top.content.nav_frame.refresh_nav(). 
>>> This behaviour could also be achieved by the new AJAX pagetree. To 
>>> speed up reloading, only the updated branch of the tree has to be 
>>> loaded.
>>>
>>> Solution:
>>> I first made the BEfunc getSetUpdateSignal so it could take 
>>> additional parameters (here: the branch of the tree). Also, I didn't 
>>> like the coding design that one function does both setting the update 
>>> signal and retreiving the JS code for that. So I split that while 
>>> keeping backwards compatibility.
>>> Then I needed to fix the AJAX-call through using a absolute path for 
>>> the ajax.php in the. I also added the new function "refreshBranch" 
>>> which takes a list of pages to refresh. It takes the same AJAX call 
>>> as with the expand / collapse code.
>>> Additionally I implemented the first improvement when editing page 
>>> properties. Try it out: Edit a page record and e.g. change the title. 
>>> It will refresh only the branch.
>>>
>>
>>
> 


-- 
Ingmar Schlecht
TYPO3 Association Active Member