Project

General

Profile

Actions
Copy link

Bug #60748

closed

Not possible to import static sql-entries (records shipped with extensions)

Added by Stefan Neufeind about 10 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Nicole Cordes
Category:
Extension Manager
Target version:
7 LTS
Start date:
2014-08-03
Due date:
% Done:

100%

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

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 :-)

Actions
Copy link
 #1

Updated by Jigal van Hemert about 10 years ago

  • 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?

Actions
Copy link
 #2

Updated by Stefan Neufeind about 10 years ago

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).

Actions
Copy link
 #3

Updated by Alexander Opitz almost 10 years ago

  • Status changed from Needs Feedback to New
Actions
Copy link
 #4

Updated by Franz Holzinger over 9 years ago

I can confirm this bug with TYPO3 6.2.10.
The file ext_tables_static+adt.sql is not even executed during the first installation. Only the empty tables are generated.
And the documentation says that this is still supported:

http://docs.typo3.org/typo3cms/CoreApiReference/singlehtml/

Actions
Copy link
 #5

Updated by DMK E-BUSINESS GmbH about 9 years ago

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.

Actions
Copy link
 #6

Updated by Markus Klein about 9 years ago

  • 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
Actions
Copy link
 #7

Updated by Markus Klein about 9 years ago

  • 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

Actions
Copy link
 #8

Updated by Alexander Opitz almost 9 years ago

  • Status changed from Needs Feedback to New
  • Target version set to 7.5
Actions
Copy link
 #9

Updated by Benni Mack almost 9 years ago

  • Target version changed from 7.5 to 7 LTS
Actions
Copy link
 #10

Updated by Nicole Cordes over 7 years ago

  • Status changed from New to Accepted

We have to allow to reimport provided static SQL data in EM!

Actions
Copy link
 #11

Updated by Nicole Cordes over 7 years ago

  • Assignee set to Nicole Cordes
Actions
Copy link
 #12

Updated by Gerrit Code Review over 7 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/51310

Actions
Copy link
 #13

Updated by Gerrit Code Review over 7 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/51310

Actions
Copy link
 #14

Updated by Gerrit Code Review over 7 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/51310

Actions
Copy link
 #15

Updated by Gerrit Code Review over 7 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/51310

Actions
Copy link
 #16

Updated by Gerrit Code Review over 7 years ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/51310

Actions
Copy link
 #17

Updated by Nicole Cordes over 7 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions
Copy link
 #18

Updated by Riccardo De Contardi almost 7 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF