TYPO3 Environment
TYPO3 v9.5.3
EXT:news (7.0.8)
EXT:indexed_search (9.5.3)
Use Composer: No
The Problem
On EXT:indexed_search result listing page, Custom extension record's slug URL are not generating. The slug only contains TYPO3 page URL.
Example; The URL should be http://thedomain.com/news/detail/announce-first-news/, but it currently only generates http://thedomain.com/news/
As per our analysis, it seems TYPO3 v9 site management's slug feature cause issue, and there could be following possible issues.
Issue #1
The major issue is, After enabling site management's slug setup, No more indexing happening for a custom extension.
Issue #2
Indexing result will lose after the page will refresh or move to another page (After clear cache data will show again).
Issue #3
If we create new records for a custom extension, then the created new records will not be indexing.
Issue #4
If anyhow, we have done the indexing and search works well, then at search result listing page, The link redirect to the main action like Listing. Because cHash is missing to each record, That's a bit strange!
Does anyone have any idea/solution? Highly appreciate your any thoughts, Thanks a lot!
Cheers,
Team NITSAN
This has been fixed with release of 9.5.5, released 4.3.2019. Check out the release notes which you can find here: https://get.typo3.org/release-notes/9.5.5
The issue for the bug is https://forge.typo3.org/issues/86994
However there has been also a regression detected which is described at https://forge.typo3.org/issues/87855 but it has already been fixed as well. The bug occurs if MYSQL strict mode is used
Related
yes, it's me with a further, maybe stupid question. I'm very new in TYPO3, I just started working with it. I know some programming languages but no typoscript. Therefore I'm working with the bootstrap package first.
I made some forms with TYPO3 core and so far everything was fine but there wasn't any possibility to customize the email (to sender). Therefore I first installed "Form: Mailtexts via plugin" but afterwards the form was not working anymore and I deleted it and everything was fine again.
After some research I have found powermail for creating forms with loads of cool functions.
So, I read four different tutorials about making forms in powermail and it's not working at all.
As far as I can evaluate the problem, I would guess that the last step is the problem, placing the content on the page.
After loading the page with the powermail elements an error message is shown
"TypoScript settings are missing. Did you include the related static templates? No form to show"
Of course I googled this error message and found this post https://github.com/derhansen/sf_event_mgt/issues/432.
In this post they include "fluid content elements" and "Event management and registration" extension and so did I. A new icon in the backend popped up "Events". Selecting this icon a further error message is shown:
"TypoScript settings missing Unable to find TypoScript settings for module. Please make sure, you have included the static TypoScript for the extension."
The page with the powermail elements is empty now, i.e. no more error message but it's also not working at all.
Please, does anyone understand what's going on here? I'm devastated :-(
Many thanks in advance for your kind help!
Best,
expikx
I tried to solve the problem by internet research and experiments
The plugin of powermail just informed you, that basic configuration is missing. The configuration is given via TypoScript and of course powermail brings some default configuration with it.
You now have to include them. You can do it by opening your default TypoScript template, change to the tab "Includes" and select "Main Template (powermail)". Save your template and reload your frontend.
I have followed every tutorial on Form. In every tutorial after I finish their steps the form appears in front-end. My form displays this error:
Oops, an error occurred! Code: 20220818062042eaedc27c
I have installed a sitepackage in my page and created some custom masked element but nothing I think to interfere with the Form module. What could be causing this?
Since I am new to TYPO3 I have made a noob mistake. Anyway I am leaving the answer here for anyone to see. Also this does not apply only to this case, just be careful to not forget to include this for other extensions as well:
This should work after that, if not just give a flush cache and you should be good.
I have saved TYPO3 text (bodytext) in database. It contains different links saved in t3 format:
<p>Link more text.</p>
The idea is create some script as CommandController, get this saved text and send it via email by cron. The problem is links will not be converted in proper html without frontend environment (it works fine, if I do the same inside frontend plugin).
I tried to render this text with fluid html view helper:
<f:format.html>{item.bodytext}</f:format.html>
Also tried to parse text with $contentObject->parseFunc directly inside my CommandController. But it will just cut off link.
Is any simple TYPO3 function to convert bodytext in real html?
Note: typo3 version 8.7.16
Okay, It seems links are not being parsed and I don't think it's an issue with CommandController. I had same issue and found several ways to fix this issue.
Issue with EXT: frontend_editing
After uninstalling every non-vital extension and clearing every
possible cache and a few hours of debugging we have found the problem:
the "frontend_editing" extension - only if the user is logged in into
the backend!
Issue at GitHub
Same issue discussed on Github, you can check it out here
#csba described detailed answer here!
Issue with EXR:fluid_styled_content
Another issue is with format viewhelper, #georg-ringer has explained solution for fixing issue and it works for me. Check it out here for more detail.
As per #georg-ringer answer, you can just change <f:format.html>{item.bodytext}</f:format.html> to <f:format.raw>{item.bodytext}</f:format.raw>. Probably this will fix your problem.
Extbase parse with link service.
// use TYPO3\CMS\Core\LinkHandling\LinkService;
$linkService = GeneralUtility::makeInstance(LinkService::class);
$linkDetails = $linkService->resolve($firstparameter);
You can parse link as shown above, you can find the reference below:
API documentation
Stackoverflow answer
I am working with the extension news on TYPO3 9.5. I have a project with few microsites and I want to use the news there. In the microsite homesite news(list) works but when I click the link which points to a detailed view of news, this leads to 404 and it does not work.
Detailed view does not work on Microsite.
I tried configuring Starting Point without success. Do i have to configure categories?
Any idea where I can also check?
The Solution was to change TCA to "unique" (TYPO3 Core Routing) due to URL resolving.
More can you find here:
https://forge.typo3.org/issues/91397#note-12
I'm using TYPO3 7.6 with the latest tx_news release from TER.
I want to show two news plugins at one page: one is configured to show all news from storage folder "A"; the other one is configured to show only the latest record from storage folder "B".
Now, once the first plugin paginates, the second one renders empty content since it tries to paginate as well (which doesn't make sense since it should display only the latest record).
So, my question is: How can I separate the pagination between both plugins?
In TYPO3 7.6 there is no solution to your issue, sorry. Workarounds include adding manual pagination for the second plugin or overriding the second widget with one that forces a different ID.
In TYPO3 8.6+ you can override the ID of each widget which causes the URL scope to change so you can isolate parameters for each widget. More information can be found on https://docs.typo3.org/typo3cms/extensions/core/8.7/Changelog/8.6/Feature-47006-ExtendTheWidgetIdentifierWithCustomString.html
I tweaked the fluid template to totally avoid the pagination in this case (based on "settings.templateLayout"
In the meantime (I don't know whether it was in place three years ago) there is an option Hide the pagination in the news plugin. You will find it in the tab Additional.
So if you place more than one list view on one page, you can disable pagination for all lists, which should not get paginated.