Bug #60748
closed
Not possible to import static sql-entries (records shipped with extensions)
Added by Stefan Neufeind almost 10 years ago.
Updated over 6 years ago.
Category:
Extension Manager
Description
The file ext_tables_static+adt.sql may contain (static) data to be inserted to the database upon installation of an extension. Afaik that was part of the extension-manager in previous versions but is currently not possible with the current version.
Show should static data / default records be shipped with an extension? If not with that said sql-file anymore, then let's find another way - and be it XML-data or whatever :-)
- Status changed from New to Needs Feedback
\TYPO3\CMS\Extensionmanager\Utility\InstallUtility::importStaticSqlFile() does this, but it does it only once (registry entry to keep track).
Is the problem that it's only done once?
Hmm, then I'm unsure why exactly my tables were empty. I didn't install the extension through TER but checked it out via git and just activated it. Might that have been a problem?
Would it maybe make sense to offer a way to (selectively) import data from the extension-configuration or some similar dialog? static_info_tables had similar needs to re-import data (and afaik found their own way to "do it by hand", right?) This way upon upgrade or update of data users could be advised to check if they want to re-import the static data (and loose their local modifications to that table).
- Status changed from Needs Feedback to New
Is there any progress? I would love to see this feature back again. As TYPO3 6.2 core is feature frozen, is this considered as a bug or a feature, which would mean there is no chance this will come back in 6.2?
If it is a bug I'm willing to contribute a solution.
- Status changed from New to Accepted
- Assignee set to Markus Klein
- Priority changed from Should have to Must have
Edit:
I verified this issue now and I'm able to reproduce.
It was a SQL syntax mistake of mine.
Multiple things that "annoy" me:
- The registry entry is written also for extensions that do not even provide a _static+adt.sql file
- There is no sane way to force re-importing these static data
- Status changed from Accepted to Needs Feedback
- Assignee deleted (
Markus Klein)
Currently you can only enforce the re-import of the static data by deleting the according row in sys_registry, where the entry_key hold the path to your sql file
- Status changed from Needs Feedback to New
- Target version set to 7.5
- Target version changed from 7.5 to 7 LTS
- Status changed from New to Accepted
We have to allow to reimport provided static SQL data in EM!
- Assignee set to Nicole Cordes
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by