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

Provide inline 1:1 example with relation field on the parent side #102

Merged
merged 1 commit into from Aug 24, 2017

Conversation

@tmotyl
Copy link
Member

commented Aug 17, 2017

Example code for reproducing issue https://forge.typo3.org/issues/82121

@@ -92,6 +92,9 @@
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOnStandardPages('tx_styleguide_inline_1n');
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOnStandardPages('tx_styleguide_inline_1n_child');
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOnStandardPages('tx_styleguide_inline_1_1');

This comment has been minimized.

Copy link
@lolli42

lolli42 Aug 21, 2017

Collaborator

if you rename the tables from "_1_1" to "_11" and "_1_1_child" to "_11_child", the auto-data generator should find them and should create some data for it (hopefully correct data, but that should have a look into the generator, then).

This comment has been minimized.

Copy link
@lolli42

lolli42 Aug 21, 2017

Collaborator

i would prefer to get the naming right - the table names are a convention for the data generator to find "main" tables, see getListOfStyleguideMainTables() in class Generator.

This comment has been minimized.

Copy link
@tmotyl

tmotyl Aug 21, 2017

Author Member

on it

@tmotyl tmotyl force-pushed the tmotyl:inline1_1 branch from e8737b7 to 15f3c49 Aug 21, 2017

@lolli42 lolli42 merged commit a638326 into TYPO3:master Aug 24, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.