Closed Himakar-PV closed 3 years ago
Himakar-PV
commented
3 years ago I fixed page rendering issue, I wonder why it is not explained in the docs which is very important.
Below content need to be added in the Setup of template
Still I see below error in log file:
[ERROR] request="c1aeaa4b136a4" component="TYPO3.CMS.Backend.Configuration.TypoScript.ConditionMatching.ConditionMatcher": Expression could not be parsed. - {"expression":"page | module = t3blog"}
fnagel
commented
3 years ago Hey! Mmhh, that looks like a couple of issues:
I fixed page rendering issue, I wonder why it is not explained in the docs which is very important.
The docs cover everything regarding the extension, not TYPO3 CMS basics. You need a working TYPO3 instance in order to work with extensions.
Expression could not be parsed
Looks like there is an outdated condition in place. Would you mind testing if changing the following line helps:
[page | module = t3blog]
to
[page["module"] == "t3blog"]
in https://github.com/fnagel/t3extblog/blob/master/Configuration/TSconfig/Page.tsconfig#L11
Himakar-PV
commented
3 years ago Thank you @fnagel , your suggestion in Page.tsconfig worked.
Your page structure looks odd. Why having multiple "Blog" pages and storages? What page type is the first "Blog" page?
In my first image, I was checking to use blog extension out of my custom extension and inside my custom extension. "Home" page is linked with custom extension.
fnagel
commented
3 years ago your suggestion in Page.tsconfig worked.
Nice! Thanks for the feedback. Will be included in the next release!
When I try to configure with v10.4.6 it throws page not configured error as shown below:
This is the configuration I made in template:
In log file I observed this: [ERROR] request="c1aeaa4b136a4" component="TYPO3.CMS.Backend.Configuration.TypoScript.ConditionMatching.ConditionMatcher": Expression could not be parsed. - {"expression":"page | module = t3blog"}