Project

General

Profile

Actions

Bug #67241

closed

FAL: Update storgae index doesn't save "Storage to index" on first save

Added by Viktor Livakivskyi over 9 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Must have
Category:
scheduler
Target version:
Start date:
2015-06-02
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

This bug is resut of #25805, but now core scheduler tasks are affected, so it becomes more critical.

In a nutshell:
1. You must have 2 or more FAL storages.
2. Create a scheduler's task "Update storage index".
3. Select any storage, except the first one, which appears in "Storage to index" drop-down.
4. Save.
5. No matter, what have you selected, you will always get the first storage form a drop-down.

You must edit tasks and select stoarge again.

The reason is in fact, that there is hidden set of fields for "Extract metadata in storage" system task, which also has a "tx_scheduler[scheduler_fileStorageIndexing_storage]" field and on task creation it overwrites selection.


Related issues 1 (0 open1 closed)

Blocked by TYPO3 Core - Bug #25805: Adding a new task with additional fields saves the wrong values in the additional fieldsClosedMichael Oehlhof2011-04-06

Actions
Actions

Also available in: Atom PDF