I have typo3 version 7.6.18. $this->someRepository->remove($object);
it's just set delete = 1 in DB. I need remove completely, using repository query. Is it possible? How to do it ?
Just avoid defining delete option in ctrl section of TCA for your table. This is the flag that toggles "soft deletion" which is what you are encountering.
Could you use $this->someRepository->removeAll(); this function removes all objects from repository as says the official documentation of TYPO3 in this link.
Related
Extensions change TCA in ext_tables.php
Check for ExtensionManagementUtility and $GLOBALS["TCA"].
During upgrading typo3 version 7 to 8
How to solve this?
If you're the owner of this extension, it is recommended to migrate the TCA changes into the extensions' folder Configuration/TCA/ for new TCA tables, and Configuration/TCA/Overrides/ when adding fields or manipulating TCA.
This way, all changes from ext_tables.php should be moved in there, due to a better performance in frontend. See also this change:
https://docs.typo3.org/typo3cms/extensions/core/latest/Changelog/8.5/Breaking-78384-FrontendIgnoresTCAInExtTables.html
In TYPO3 8.7 you can choose whether you want to translate or copy content elements. How can I disable the "translate" option in the first step of the wizard?
In a current project the customer prefers to have only the copy possibility.
The Core itself supports this starting with version 9, so there is currently no core-wise solution in 8.x.
But: You may write an extension supporting the same configuration parameters as v9 does by XClassing PageLayoutView.php. Please see the change that introduces the possibility to configure these buttons.
Thx to the hint from Andreas Fernandez I was able to backport the feature from TYPO3 9.x to 8.7.x by xclassing the method.
I've put everything together into a Gist:
https://gist.github.com/peterkraume/1c0feb30440449ba1c708aa5ea8d7991
I am just using a css-based solution.
Just add the following to "ext_tables.php"
// Custom Backend CSS
$GLOBALS['TBE_STYLES']['skins']['base'] = [
'name' => 'cytrus Base Backend Skin',
'stylesheetDirectories' => ['EXT:myext/Resources/Public/Backend/']
];
And then create a file "mycss.css" in "EXT:myext/Resources/Public/Backend/" with the following content:
[data-slide="localize-choose-action"] > div > div:first-child {display: none;}
that's it!
this is the result
I looked at this Similar Question on here but I didn't understand half of what everyone is saying there as I'm not very familiar with TypoScript...
Let me start from my point of view: I got a backend tree in TYPO3 6.2 that looks like this:
Data is of type "Folder" where I want to store my records.
Userroles, Admins and Lawyer are of Type "Standard" while the last two contain the Plugin "Website Users".
Now I want to add a new fe_usergroup to page Userroles:
I get following error:
It's the same when I try inserting a new fe_user in Admins:
So in the other answers from mentioned question they're talking about Page-TS-Config - I looked at my Userroles Page and saw this:
and I went to the Template Analyzer and searched for allowedNewTables and deniedNewTables but no results. And to the comment: section ctrl which value has rootLevel - but those TCAs are from Extbase right? So why would they be wrong...
I must have done something wrong but I have no idea what it could be.
It worked before I think...although I don't know about the usergroups, didn't try to add a new one recently.
I placed
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOnStandardPages('tx_myext_download');
into the ext_tables.php of myext to allow this kind of records.
Maybe that helps.
Add in Your ext_tables.php in Your Extension following code:
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOnStandardPages('tx_your_extension_table_name');
In TYPO3, you have to define, which tables are allowed on standard pages. There is a method in the ExtensionManagementUtility, that does extacly that:
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::allowTableOnStandardPages('tx_yourtable');
If you have a look at the source, you'll see, that this method ist just one line of code that concatenates table names into the global configuration array, specifically at
$GLOBALS['PAGES_TYPES']['default']['allowedTables']
Its possible that something in your TYPO3 installation messes with this line.
Check the value of this configuration value in either the Install Tool or the Confuguration tab in the backend. If this line contains anything other than comma seperated table names, something is wrong. TYPO3 base table names like pages,tt_content,fe_users,fe_groups and so on should also be listed there by default.
Is the page that you are trying to add usergroups to of type "page" or "directory" (see "General"-tab). Probably it must be of kind "directory" or "folder"
Since updating from Flux 6.0.2 to the newest Flux TER-Release (7.0.0) I have the problem that all my defined flux:field.select items are switched. I have them defined as an array like this items="{0: {0: 'value shown as a CSS class in the frontend',1: 'value shown in BE'},}". But now I get the BE value in the frontend template.
Also all my content elements from my provider extension are shown twice (without a title) in the backend and the fields defined in the 'Configuration' section of my content element are shown twice.
There's also a RTE field shown at the bottom of my content element that has not been there before.
BE Output: view
Code on Pastebin: http://pastebin.com/CNcphn2k
Any help deeply appreciated.
EDIT:
I just set up a fresh instance of TYPO3 6.1.9 (blank package) and installed my extension with the above mentioned content elements. Dependencies were resolved automatically as it should (newest versions). Via the content wizard I tried to create a new element and I get the same result as in my existing install I first noticed this bug in.
EDIT2:
I was able to narrow it down to the flux:form.container tag. This duplicates the output in the BE. The select values are still switched though.
It is possible that you missed this official announcement:
http://fluidtypo3.org/blog/news/new-colpos-value.html
Failure to run the update script before letting TYPO3 change the type of the colPos value will result in the symptoms you describe. There is, unfortunately, no way to restore this (since your SQL will have cropped off all negative values and made them zero without any backup).
Restore from a backup and run the script and you should be fine.
We're trying to implement a mobile version of our Typo3 site, but whenever I add a new Template Object and select something in "Make this a sub-template of", I get this error:
I'm not very good with typo3, so if anyone could point me in the right direction it would be great. Thanks.
Go to Install Tool > Database Analyser > COMPARE and mark the checkboxes to add missing fields and tables (you don't need to remove suggested things)
Repeat the operation as long as required, if some field can not be added by COMPARE, you need to include it manually via phpMyAdmin. Most probably in such case you'll need to resolve some conflict.
Next go to Extension Manager, find the TemplaVoila ext and search for Update button, to make sure that the config is saved correctly to the file.