I have an empty <body> after migration from typo3 4.5 to 6.2.10.
Hello world in body works but with the typoscript with the extension automaketemplate there is an empty body tag. Anybody have an idea why ?
Thank you very much in advance.
Mohamed
After Migration Follow this step:
1) Upgrade all the compatible extension and disable those extension which is not compatible.
2) Check the typoscript , some of typoscript has been removed in 6.2 version. need to removed or need to replace with latest.
3) Check the install tool > upgrade wizard. is there anything that remaining to be execute ?
For error debug :
Add this into LocalConfiguration.php under the 'sys'
'debug' => '1',
'displayErrors' => '1',
'enable_DLOG' => '1',
'enable_errorDLOG' => '1',
'enable_exceptionDLOG' => '1',
#Mohamed Masmoudi : Just add the debug code in your Localconfiguration.php. that will show the error which not loading frontend.
I hope this things helps.
I had the same issue. In my case, the extension css_styled_content was not installed and selected in TS. After that it worked fine.
I have this in the admin panel :
Setting language and locale 9 Locale "de_DE" not found.
Page generation 40
page PAGE 60 Content Object "" does not exist
Content Object "" does not exist
Content Object "PHP_SCRIPT" does not exist
Include libraries
page 6 Files for inclusion: "typo3conf/ext/automaketemplate/pi1/class.tx_automaketemplate_pi1.php"
Include libraries
page 1 Files for inclusion: "typo3conf/ext/automaketemplate/pi1/class.tx_automaketemplate_pi1.php"
Page generation/XHTML clean, all 10
Page generation/Local anchor fix, all 0
Print Content 5
Related
Trying to add a new page in a Laravel BackPack project, using the PageManager addon gives the following error:
SQLSTATE[HY000]: General error: 1364 Field 'template' doesn't have a default value
Expanding the Ignition error message shows the following:
INSERT INTO
`pages` (
`name`,
`title`,
`slug`,
`content`,
`extras`,
`updated_at`,
`created_at`
)
VALUES
(
dghj,
fghj,
fghj,
?,
{ "meta_title": NULL,
"meta_description": NULL,
"meta_keywords": NULL },
2022 -09 -12 16: 19: 59,
2022 -09 -12 16: 19: 59
)
...there's no sign of a template in this query but (I believe) it should be added by the PageManager addon so isn't something I have control of.
None of the frames in Ignition show files I've worked on, they're all illuminate or vendor files, however I've set up a new base app containing Laravel, Backpack and Backpack PageManager only, which works as expected so I don't think this is a bug in a package. I'm at a loss as to what I've done wrong or how to go about finding/resolving the problem.
Further info:
Selecting a template in the CRUD view DOES prompt the JS pop-up 'Are you sure you want to update the page template', confirming DOES update the URL to include the GET parameter e.g. [domain]/admin/page/create?template=standard
PHP Version: 8.1.9
Backpack version: 5.3.12
I also have the MenuCRUD addon installed which is reliant upon PageManager and is working as expected.
I managed to find the issue.
For whatever reason a view had been published to resources\views\vendor\backpack\crud\fields\select_page_template.blade.php
This file included:
<select class="form-control" id="select_template" name="select_template" ... >
Changing the name to 'template' resolved the issue:
<select class="form-control" id="select_template" name="template" ... >
Neither of these variations match what's in the original version of the file here, which doesn't even include a name attribute on the input. I'm not sure why mine does, but is all seems to be working now so I'll let sleeping dogs lie and leave this page up in case it benefits anybody else.
I have a new TYPO3 9.5.15 installation and added gridelements 9.5.0 and t3sbootstrap 4.4.5 to make content elements with 3 columns in a own 1 column backendlayout which is defined in PageTsConfig.
In older TYPO3 versions, this is working fine (i.e TYPO3 7) but in TYPO3 9 I get the following error in FE:
Tried resolving a template file for controller action "Standard->three_columns" in format ".html", but none of the paths contained the expected template file (Standard/Three_columns.html). The following paths were checked:
xxx/typo3/sysext/fluid_styled_content/Resources/Private/Templates/, xxx/typo3conf/ext/gridelements/Resources/Private/Templates/, xxx/typo3conf/ext/t3sbootstrap/Resources/Private/Templates/Content/, xxx/typo3conf/ext/t3sbootstrap/Resources/Private/Templates/, ,
I've double checked and can confirm, that both, gridelements and t3sbootstrap are included in the roottemplate of the website.
As far as I found out, the templates are available in xxx/typo3conf/ext/t3sbootstrap/Resources/Private/Templates/Gridelements/
but are called ThreeColumns.html
Has anyone an idee what causes the error and how to resolve it?
Thanks in advance
At a first look it seems that there are 2 problems with your combination here:
The message "Standard->three_columns" points to a wrong static template, so I guess you included the new DataProcessing static of Gridelements, while t3sbootstrap depends on the old Plugin and USER based static.
The root path xxx/typo3conf/ext/t3sbootstrap/Resources/Private/Templates/Gridelements/ is missing in your setup.
At a second look it might even be enough to change the Gridelements static, since t3sbootstrap takes care of the root path based on that setup.
I was using the page wizard, but after upgrade i had to switch to the
'renderType' => 'inputLink',
in my extensions TCA.
This results the following output:
t3://page?uid=19
If i debug the variable in my template, this is shown:
<f:debug>{domainmodel.page}</f:debug>
external => 'http://t3://page?uid=19' (23 chars)
Whats to correct way to show the Link in my extension template?
Please use the f:link.typolink viewhelper for this.
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 have Typo3 7.6.2 and RealURL 1.13.15, whis is for Typo3 4.5.40-7.9.999
In Typo3 < 7 there was option "Override the whole page path "
In Typo3 7.6.2 seems this option is not present.
In the language file of RealUrl is:
<label index="pages.tx_realurl_path_override">Override the whole page path</label>
But in BE of Typo3 i can't find this option
My config is:
'realurl' => 'a:5:{s:10:"configFile";s:26:"typo3conf/realurl_conf.php";s:14:"enableAutoConf";s:1:"1";s:14:"autoConfFormat";s:1:"0";s:12:"enableDevLog";s:1:"0";s:19:"enableChashUrlDebug";s:1:"0";}'
Any Idea?
Take a look into typo3conf/ext/realurl/ext_tables.php:78 there are these lines which according to #deprecated comment in typo3/sysext/core/Classes/Utility/ExtensionManagementUtility.php:318 in version 7.x+ as I hardly believe should be replaced:
$extensionMamagementUtility::addToAllTCAtypes('pages', 'tx_realurl_pathsegment;;137;;,tx_realurl_exclude', '1', 'after:nav_title');
$extensionMamagementUtility::addToAllTCAtypes('pages', 'tx_realurl_pathsegment;;137;;,tx_realurl_exclude', '4,199,254', 'after:title');
with:
$extensionMamagementUtility::addToAllTCAtypes('pages', 'tx_realurl_pathsegment, --palette--;;137, tx_realurl_exclude', '1', 'after:nav_title');
$extensionMamagementUtility::addToAllTCAtypes('pages', 'tx_realurl_pathsegment, --palette--;;137, tx_realurl_exclude', '4,199,254', 'after:title');
You can probably override the TCA within your own ext, or just hack the RealURL source (dirty solution) anyway must accent that I have no idea what is Dmitry's intension. (In other words I don't know if it's bug, or a feature ;))