Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MAINTENANCE] TYPO3 v11 compatibility #885

Merged
merged 34 commits into from
Sep 15, 2023

Conversation

chrizzor
Copy link
Collaborator

This PR ensures that the DLF Extension is also compatible with version 11 of Typo3.
The biggest adjustment was the reorganization of the pagination, since the widgets were removed from Typo3. This required an own "Pagniator" for the Solr, as well as for the display of the "PageGrid"

@sebastian-meyer sebastian-meyer added ⚙ feature A new feature or enhancement. ⭐ development fund 2022 A candidate for the Kitodo e.V. development fund. 🛠 maintenance A task to keep the code up-to-date and manageable. and removed ⚙ feature A new feature or enhancement. labels Jan 4, 2023
@sebastian-meyer sebastian-meyer linked an issue Jan 4, 2023 that may be closed by this pull request
@sebastian-meyer sebastian-meyer changed the title Typo3 v11 compatibility [MAINTENANCE] TYPO3 v11 compatibility Jan 4, 2023
@sebastian-meyer
Copy link
Member

Could you please bring this pull request up to date with master? Thank you!

@sebastian-meyer
Copy link
Member

Could you please adjust the testing workflow in order to ensure testing against TYPO3 v10 and v11 instead of v9 and v10? Currently tests fail, because they are still run against v9.

@sebastian-meyer
Copy link
Member

sebastian-meyer commented Feb 23, 2023

I think we need to update Build/Test/runTests.sh as well. Have a look at the upstream file from TYPO3 CMS: v10, v11.

Constraints for tests and in composer.json for TYPO3 v10 and v11 should be (see also: https://get.typo3.org/):

  • PHP: 7.4 (v10 doesn't support PHP 8 and v11 requires at least PHP 7.4)
  • MariaDB: 10.3 (default for both TYPO3 versions)
  • TYPO3: 10.4.36|11.5.24 (latest safe TYPO3 versions)

Also please check if we can use the newest version of spatie/phpunit-watcher since we should be able to run PHPUnit 9.x now, are we?

After updating composer.json please also update composer.lock file accordingly (by running composer update locally).

@sebastian-meyer
Copy link
Member

sebastian-meyer commented Feb 23, 2023

There are a lot of mentions of TYPO3 v9 left in the documentation and code. All of them need to be updated according to the new supported versions. Also, some of them point to work-arounds for backwards compatibility which are no longer needed when dropping support for v9. Please check and remove those work-arounds.

@csidirop
Copy link
Contributor

csidirop commented Feb 24, 2023

I did a few tests (on TYPO3 v10 with DFG-Viewer) and while most of the parts I tested worked fine I found following error:

Using the search or collection plugin leads to Core: Error handler (FE): PHP Warning: A non-numeric value encountered in /var/www/typo3/vendor/typo3fluid/fluid/src/Core/Parser/SyntaxTree/Expression/MathExpressionNode.php line 77.

For me this results in some erroneous output:

Die Suche ergab 8 Treffer in 8 Dokumenten.

Einträge -24 bis 0 von 8. 

Here what it looks like: (without custom CSS)
grafik
and
grafik

@chrizzor
Copy link
Collaborator Author

@csidirop @sebastian-meyer : Do you both get the error with the wrong number of hits?
I can't reproduce this on my local dev environment. Can you give me more hints, so I can reproduce the error?
Bildschirmfoto 2023-02-28 um 19 26 06

@csidirop
Copy link
Contributor

csidirop commented Mar 1, 2023

First of all, could you please bring your branch up to date with kitodo:master as @sebastian-meyer requested one month ago. You are at 31dbff3 and 38 commits behind, some of which fixed bugs.

Now, I get the same results regardless weather I'm merging kitodo:master into your branch or not, its still the same error from above.

But it may also have something to do with my dev environment. I'll try that asap. But for the moment what I'm doing is checking out your branch in my Docker env after everything is set up (here may be the difference?). Plus I'm using DFG-Viewer which may have some influence. I'll test that too asap.

@csidirop
Copy link
Contributor

csidirop commented Mar 1, 2023

So I updated my docker setup to initially setup dlf with your branch, but as soon as I want to add Kitodo Elements to a subpage I get this error:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1478105826: Data structure file /var/www/typo3/public/typo3conf/ext/dlf/Configuration/FlexForms/PageView.xml could not be resolved to an existing file | RuntimeException thrown in file /var/www/typo3/public/typo3/sysext/core/Classes/Configuration/FlexForm/FlexFormTools.php in line 688. Requested URL: http://localhost/typo3/index.php?route=%%2Frecord%%2Fedit&token=--AnonymizedToken--&edit%%5Btt_content%%5D%%5B12%%5D=new&defVals%%5Btt_content%%5D%%5BcolPos%%5D=0&defVals%%5Btt_content%%5D%%5Bsys_language_uid%%5D=0&returnUrl=%%2Ftypo3%%2Findex.php%%3Froute%%3D%%252Fmodule%%252Fweb%%252Flayout%%26token%%3D95445b61554c1e3a30cd87be3f6451301c9e5fce%%26id%%3D12%%26&defVals[tt_content][CType]=list&defVals[tt_content][list_type]=dlf_pageview 

This issue can be resolved by merging kitodo:master. But after that I'm stuck at some config issue I have no time to resolve now.

But I can show you my workflow in case you want to follow this:

  1. git clone https://github.com/UB-Mannheim/kitodo-presentation-docker and cd into
  2. git checkout dfg-viewer-6.x-ocr (unfortunately solr is only on our ocr branches available so far)
  3. Setup the .env-file
  4. docker compose --profile with-solr up [--build]
  5. docker exec -ti kitodo-presentation-main bash
  6. And than go the dlf folder add your branch and check it out

I can't rule out, that the error only occurs in my environment. Hopefully sebastian can test it and see if he has the same errors.

@sebastian-meyer
Copy link
Member

sebastian-meyer commented Mar 22, 2023

  • The labels newTenant.formatNotOkay and newTenant.formatNotOkayMsg are still missing in v11.
  • Some labels for database fields are missing in the backend (in v10 and v11), for example for tables tx_dlf_libraries (tab 'Catalogs', tx_dlf_documents ('METS Label', 'METS Orderlabel'), tx_dlf_structures ('index_name') and maybe others as well.

@chrizzor
Copy link
Collaborator Author

I added the missing labels for the database fields. A faulty search and replace caused "Label" to get kicked out.
The labels "newTenant.formatNotOkay" and "newTenant.formatNotOkayMsg" are present in the language files. But also with my local system, the output remains empty.

@chrizzor
Copy link
Collaborator Author

I think the escaped single quotes cause problems in this case. With double quotes, it works for me.

@sebastian-meyer
Copy link
Member

I don't know why (because some lines below it works perfectly with single quotes), but now it works for me as well!

@sebastian-meyer
Copy link
Member

And tx_dlf_structures.index_name is wrong, too. Currently it is tx_dlf_structures.id_name.

@chrizzor
Copy link
Collaborator Author

I have adjusted the TCA accordingly and added information in development.md for v11 and v12.
With this the points should be finished so far. I hope that I have considered everything in the "Scan Extension Files". There were quite a lot of wrong information.

@csidirop
Copy link
Contributor

Unfortunately the missing search results are still an issue in my tests. Can you reproduce this?

@sebastian-meyer
Copy link
Member

I had to resolve a lot of merge conflicts, so maybe there are some issues now. Please extensively test the master branch and compare it to what your intended changes for TYPO3v11 compatibility should have been!

There is still some work to do, but for now this is finally merged!

@stweil
Copy link
Member

stweil commented Sep 15, 2023

CI tests now fail. Is this related to this PR?

PHP Fatal error:  Access level to Kitodo\Dlf\Controller\ToolboxController::setPage() must be protected (as in class Kitodo\Dlf\Controller\AbstractController) or weaker in /home/runner/work/kitodo-presentation/kitodo-presentation/Classes/Controller/ToolboxController.php on line 477

@sebastian-meyer
Copy link
Member

Yes, it most likely is. There probably are more issues than just that...

@sebastian-meyer
Copy link
Member

OK, that was my fault. I accidently duplicated a method while resolving merge conflicts. This is fixed now.

But tests still don't run through. @chrizzor Could you please have a look into this?

@csidirop
Copy link
Contributor

csidirop commented Sep 27, 2023

Tests under TYPO3 v10 with our DFG-Viewer:

  • Everything search related is still not working. See my comment from 24 feb. Is it just me?

  • The thumbnail preview (gridpage) shows only the first 24 pages and has no option to load more pages: (dfg-viewer issue?)
    grafik
    Short addition: On an other document the text part was partially linked. First 24 pages with working link for the next 24:
    grafik
    but the next page had only a working link back:
    grafik
    The two mentioned mets: https://digi.bib.uni-mannheim.de/fileadmin/vl/ubmaosi/59087/59087.xml and https://digi.bib.uni-mannheim.de/fileadmin/vl/ubmaosi/59088/59088.xml

  • In addition, the numbers 1 and 31 refer to the number of review pages. But are somehow incorrectly displayed / placed. For reference, how it currently looks (and should be looking):
    grafik

  • The image manipulation tools are missing: (dfg-viewer issue?)
    grafik

  • the same Metadata pairing/grouping issue described later

Tests under TYPO3 v11:

  • I could not get the viewer running. But that can be on me. I had always issues manually setting presentation up. Ill try more. Is there anywhere a step by step guide?
    -> I could not try the viewer or anything related
  • New Tenant Module:
    • Can not create a new Solr Core:
      grafik
      -> I did not set the correct solr configuration prior. But till v10 this wasn't necessary.
    • After creating namespaces, Structures and Metadata they aren't "grouped" or "paired" by language any more:
      grafik grafik
  • Analyze Database Structure shows:
Add tables
    CREATE TABLE tx_dlf_documents (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `tstamp` INT DEFAULT 0 NOT NULL, `crdate` INT DEFAULT 0 NOT NULL, `cruser_id` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `hidden` SMALLINT DEFAULT 0 NOT NULL, `starttime` INT DEFAULT 0 NOT NULL, `endtime` INT DEFAULT 0 NOT NULL, `fe_group` VARCHAR(100) DEFAULT '' NOT NULL, `prod_id` VARCHAR(255) DEFAULT '' NOT NULL, `location` VARCHAR(255) DEFAULT '' NOT NULL, `record_id` VARCHAR(255) DEFAULT '' NOT NULL, `opac_id` VARCHAR(255) DEFAULT '' NOT NULL, `union_id` VARCHAR(255) DEFAULT '' NOT NULL, `urn` VARCHAR(255) DEFAULT '' NOT NULL, `purl` VARCHAR(255) DEFAULT '' NOT NULL, `title` TEXT NOT NULL, `title_sorting` TEXT NOT NULL, `author` VARCHAR(255) DEFAULT '' NOT NULL, `year` VARCHAR(255) DEFAULT '' NOT NULL, `place` VARCHAR(255) DEFAULT '' NOT NULL, `thumbnail` VARCHAR(255) DEFAULT '' NOT NULL, `structure` INT DEFAULT 0 NOT NULL, `partof` INT DEFAULT 0 NOT NULL, `volume` VARCHAR(255) DEFAULT '' NOT NULL, `volume_sorting` VARCHAR(255) DEFAULT '' NOT NULL, `license` VARCHAR(255) DEFAULT '' NOT NULL, `terms` VARCHAR(255) DEFAULT '' NOT NULL, `restrictions` VARCHAR(255) DEFAULT '' NOT NULL, `out_of_print` TEXT NOT NULL, `rights_info` TEXT NOT NULL, `collections` INT DEFAULT 0 NOT NULL, `mets_label` TEXT NOT NULL, `mets_orderlabel` TEXT NOT NULL, `owner` INT DEFAULT 0 NOT NULL, `solrcore` INT DEFAULT 0 NOT NULL, `status` SMALLINT UNSIGNED DEFAULT 0 NOT NULL, `document_format` VARCHAR(100) DEFAULT '' NOT NULL, INDEX `parent` (pid), INDEX `location` (location), INDEX `record_id` (record_id), INDEX `partof` (partof), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_structures (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `tstamp` INT DEFAULT 0 NOT NULL, `crdate` INT DEFAULT 0 NOT NULL, `cruser_id` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `sys_language_uid` INT DEFAULT 0 NOT NULL, `l18n_diffsource` MEDIUMBLOB NOT NULL, `hidden` SMALLINT DEFAULT 0 NOT NULL, `l18n_parent` INT DEFAULT 0 NOT NULL, `toplevel` SMALLINT DEFAULT 0 NOT NULL, `label` VARCHAR(255) DEFAULT '' NOT NULL, `index_name` VARCHAR(255) DEFAULT '' NOT NULL, `oai_name` VARCHAR(255) DEFAULT '' NOT NULL, `thumbnail` INT DEFAULT 0 NOT NULL, `status` SMALLINT UNSIGNED DEFAULT 0 NOT NULL, INDEX `parent` (pid), INDEX `language` (l18n_parent, sys_language_uid), INDEX `index_name` (index_name), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_metadata (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `tstamp` INT DEFAULT 0 NOT NULL, `crdate` INT DEFAULT 0 NOT NULL, `cruser_id` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `sys_language_uid` INT DEFAULT 0 NOT NULL, `l18n_diffsource` MEDIUMBLOB NOT NULL, `hidden` SMALLINT DEFAULT 0 NOT NULL, `sorting` INT DEFAULT 0 NOT NULL, `l18n_parent` INT DEFAULT 0 NOT NULL, `label` VARCHAR(255) DEFAULT '' NOT NULL, `index_name` VARCHAR(255) DEFAULT '' NOT NULL, `format` INT DEFAULT 0 NOT NULL, `default_value` VARCHAR(255) DEFAULT '' NOT NULL, `wrap` TEXT NOT NULL, `index_tokenized` SMALLINT DEFAULT 0 NOT NULL, `index_stored` SMALLINT DEFAULT 0 NOT NULL, `index_indexed` SMALLINT DEFAULT 0 NOT NULL, `index_boost` DOUBLE PRECISION DEFAULT '1.00' NOT NULL, `is_sortable` SMALLINT DEFAULT 0 NOT NULL, `is_facet` SMALLINT DEFAULT 0 NOT NULL, `is_listed` SMALLINT DEFAULT 0 NOT NULL, `index_autocomplete` SMALLINT DEFAULT 0 NOT NULL, `status` SMALLINT UNSIGNED DEFAULT 0 NOT NULL, INDEX `parent` (pid), INDEX `language` (l18n_parent, sys_language_uid), INDEX `index_name` (index_name), INDEX `index_autocomplete` (index_autocomplete), INDEX `is_sortable` (is_sortable), INDEX `is_facet` (is_facet), INDEX `is_listed` (is_listed), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_metadataformat (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `tstamp` INT DEFAULT 0 NOT NULL, `crdate` INT DEFAULT 0 NOT NULL, `cruser_id` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `sys_language_uid` INT DEFAULT 0 NOT NULL, `l18n_parent` INT DEFAULT 0 NOT NULL, `parent_id` INT DEFAULT 0 NOT NULL, `encoded` INT DEFAULT 0 NOT NULL, `xpath` VARCHAR(1024) DEFAULT '' NOT NULL, `xpath_sorting` VARCHAR(1024) DEFAULT '' NOT NULL, `mandatory` SMALLINT DEFAULT 0 NOT NULL, INDEX `parent` (pid), INDEX `parent_id` (parent_id), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_formats (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `tstamp` INT DEFAULT 0 NOT NULL, `crdate` INT DEFAULT 0 NOT NULL, `cruser_id` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `type` VARCHAR(255) DEFAULT '' NOT NULL, `root` VARCHAR(255) DEFAULT '' NOT NULL, `namespace` VARCHAR(255) DEFAULT '' NOT NULL, `class` VARCHAR(255) DEFAULT '' NOT NULL, INDEX `parent` (pid), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_solrcores (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `tstamp` INT DEFAULT 0 NOT NULL, `crdate` INT DEFAULT 0 NOT NULL, `cruser_id` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `label` VARCHAR(255) DEFAULT '' NOT NULL, `index_name` VARCHAR(255) DEFAULT '' NOT NULL, INDEX `parent` (pid), INDEX `index_name` (index_name), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_collections (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `tstamp` INT DEFAULT 0 NOT NULL, `crdate` INT DEFAULT 0 NOT NULL, `cruser_id` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `sys_language_uid` INT DEFAULT 0 NOT NULL, `l18n_diffsource` MEDIUMBLOB NOT NULL, `hidden` SMALLINT DEFAULT 0 NOT NULL, `fe_group` VARCHAR(100) DEFAULT '' NOT NULL, `fe_cruser_id` INT DEFAULT 0 NOT NULL, `fe_admin_lock` SMALLINT DEFAULT 0 NOT NULL, `l18n_parent` INT DEFAULT 0 NOT NULL, `label` VARCHAR(255) DEFAULT '' NOT NULL, `index_name` VARCHAR(255) DEFAULT '' NOT NULL, `index_search` TEXT NOT NULL, `oai_name` VARCHAR(255) DEFAULT '' NOT NULL, `description` TEXT NOT NULL, `thumbnail` VARCHAR(255) DEFAULT '' NOT NULL, `priority` SMALLINT DEFAULT 3 NOT NULL, `documents` INT DEFAULT 0 NOT NULL, `owner` INT DEFAULT 0 NOT NULL, `status` SMALLINT UNSIGNED DEFAULT 0 NOT NULL, INDEX `parent` (pid), INDEX `language` (l18n_parent, sys_language_uid), INDEX `index_name` (index_name), INDEX `oai_name` (oai_name), INDEX `pid_cruser` (pid, fe_cruser_id), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_libraries (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `tstamp` INT DEFAULT 0 NOT NULL, `crdate` INT DEFAULT 0 NOT NULL, `cruser_id` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `sys_language_uid` INT DEFAULT 0 NOT NULL, `l18n_diffsource` MEDIUMBLOB NOT NULL, `l18n_parent` INT DEFAULT 0 NOT NULL, `label` VARCHAR(255) DEFAULT '' NOT NULL, `index_name` VARCHAR(255) DEFAULT '' NOT NULL, `website` VARCHAR(255) DEFAULT '' NOT NULL, `contact` VARCHAR(255) DEFAULT '' NOT NULL, `image` VARCHAR(255) DEFAULT '' NOT NULL, `oai_label` VARCHAR(255) DEFAULT '' NOT NULL, `oai_base` VARCHAR(255) DEFAULT '' NOT NULL, `opac_label` VARCHAR(255) DEFAULT '' NOT NULL, `opac_base` VARCHAR(255) DEFAULT '' NOT NULL, `union_label` VARCHAR(255) DEFAULT '' NOT NULL, `union_base` VARCHAR(255) DEFAULT '' NOT NULL, INDEX `parent` (pid), INDEX `language` (l18n_parent, sys_language_uid), INDEX `index_name` (index_name), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_tokens (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `tstamp` INT DEFAULT 0 NOT NULL COMMENT 'Timestamp of the token used to determine if it has expired.', `crdate` INT UNSIGNED DEFAULT 0 NOT NULL, `cruser_id` INT UNSIGNED DEFAULT 0 NOT NULL, `token` VARCHAR(255) DEFAULT '' NOT NULL, `options` MEDIUMTEXT NOT NULL, `ident` VARCHAR(30) DEFAULT '' NOT NULL, INDEX `parent` (pid), INDEX `token` (token), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE `tx_dlf_relations` (`uid` INT AUTO_INCREMENT NOT NULL, `uid_local` INT DEFAULT 0 NOT NULL, `uid_foreign` INT DEFAULT 0 NOT NULL, `tablenames` VARCHAR(30) DEFAULT '' NOT NULL, `sorting` INT DEFAULT 0 NOT NULL, `sorting_foreign` INT DEFAULT 0 NOT NULL, `ident` VARCHAR(30) DEFAULT '' NOT NULL COMMENT 'An identifier to describe which tables are matched.', INDEX `local_foreign` (uid_local, uid_foreign, ident), INDEX `uid_local` (uid_local), INDEX `uid_foreign` (uid_foreign), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB COMMENT = 'Pivot table for many-to-many relations between tables. In particular, this is used to match documents and collections by using ident=docs_colls.'
    CREATE TABLE tx_dlf_basket (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `tstamp` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `sys_language_uid` INT DEFAULT 0 NOT NULL, `l18n_diffsource` MEDIUMBLOB NOT NULL, `fe_user_id` INT DEFAULT 0 NOT NULL, `l18n_parent` INT DEFAULT 0 NOT NULL, `label` VARCHAR(255) DEFAULT '' NOT NULL, `session_id` VARCHAR(32) DEFAULT '' NOT NULL, `doc_ids` VARCHAR(255) DEFAULT '' NOT NULL, INDEX `parent` (pid), INDEX `language` (l18n_parent, sys_language_uid), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_printer (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `print` VARCHAR(255) DEFAULT '' NOT NULL, `label` VARCHAR(255) DEFAULT '' NOT NULL, INDEX `parent` (pid), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_mail (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `sorting` INT DEFAULT 0 NOT NULL, `mail` VARCHAR(255) DEFAULT '' NOT NULL, `name` VARCHAR(255) DEFAULT '' NOT NULL, `label` VARCHAR(255) DEFAULT '' NOT NULL, INDEX `parent` (pid), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB
    CREATE TABLE tx_dlf_actionlog (`uid` INT AUTO_INCREMENT NOT NULL, `pid` INT DEFAULT 0 NOT NULL, `crdate` INT DEFAULT 0 NOT NULL, `deleted` SMALLINT DEFAULT 0 NOT NULL, `user_id` INT DEFAULT 0 NOT NULL, `file_name` VARCHAR(255) DEFAULT '' NOT NULL, `count_pages` INT DEFAULT 0 NOT NULL, `name` VARCHAR(100) DEFAULT '' NOT NULL, `label` VARCHAR(255) DEFAULT '' NOT NULL, INDEX `parent` (pid), PRIMARY KEY(uid)) DEFAULT CHARACTER SET utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB

@sebastian-meyer
Copy link
Member

@csidirop I made your post into an issue (#1029). Please add all follow-up discussion and information there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⭐ development fund 2022 A candidate for the Kitodo e.V. development fund. 🛠 maintenance A task to keep the code up-to-date and manageable.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for new TYPO3 LTS version 11.5
4 participants