Bug #75270
closed
Pages inserted twice when copied via the backend
0%
Description
For some weird reason all pages i copy and paste in the backend are inserted twice.
Can someone reproduce that?
Files
Updated by Mathias Schreiber about 8 years ago
- Status changed from New to Resolved
Sorry, can't reproduce on 6.2, 7.6, 8.0 or master :(
Updated by Philipp Wrann about 8 years ago
It definitly happens, i am using TYPO3 7.6.4 and this patch: https://review.typo3.org/#/c/46996/ (can not be related i think - because thise only affects extbase)
Can you give me a hint where to dig?
I assume this is caused by some specific configuration - i googled some more issues that have been reported the last years with the same problem.
Updated by Philipp Wrann about 8 years ago
- File timed-out-ajax.png timed-out-ajax.png added
The request is fired a second time if the response was not 200.... In my case the action of copying the page tree takes too long, i receive a nginx gateway timeout. Typo3 handles this by repeating the request - that results in multiple inserted pages.
In my case i might be able to avoid this by simply increasing the maximum execution time for php-fpm - but i think this could be a common problem. It really looks like the request is sent 2 times...
Updated by Philipp Wrann about 8 years ago
This could be solved by using a queue. That way you could also receive the progress - but you would need to start an additional php worker process.
So request a new pagetree action / return a process-ticket-id
repeat request to get progress for last action
The actual copy-process would be handled async and update the progress field in the queue registry.
Alternatively the pages could be copied one by one, the process could take much longer but you would also have some progress to show the user and that would be a massive ux improvement.
Updated by Philipp Wrann almost 8 years ago
I would like to set this to Target version 8, having some progress and fail-safe copy/paste process would be a major improvement i think. Can someone change this?
Updated by Riccardo De Contardi over 6 years ago
- Status changed from Resolved to Closed