In my TYPO3 8.7.31 I have an error:
No TypoScript found. Did you already setup module.tx_femanager.settings.configPID in your PageTS?
As the error message says, you need to configure module.tx_femanager.settings.configPID in your Page TSConfig (not to confuse with TypoScript). This is necessary to make the TypoScript setting available also in the TYPO3 backend which is not the case by default.
As mentioned in the documentation you need to specify the page id (pid), where your main TypoScript settings (frontend) are stored. Usually you will take the root page of your installation.
To set the Page TSConfig, edit the page properties of your root page and switch to the tab Resources. There you can find a field Page TSConfig. In this field you need to put above mentioned setting.
A hint for your next question: please put more effort into your question! Let us know what you tried so far. And please do a proper formatting of your question.
The Problem can also appear, if you have set the
module.tx_femanager.settings.configPID = 1
in your root page ts
but not included the main settings (femanager) in the template.
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 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 experimenting a bit with Forms in TYPO 3 version 8.7.13
I have created a form in the typo 3 backend, all good and it looks good, however when I add the form to a page and the load the front page I get the error
Sorry, the requested view was not found.
The technical reason is: No template was found. View could not be resolved
for action "render" in class "TYPO3\CMS\Form\Controller\FormFrontendController".
Is there anything that needs to be added to the Typoscript config in order for them to work ?
You need to include the static template in your TypoScript template.
You have a TYPO3 form plugin on your page. See the details of the form system extension in the TYPO3 backend page module.
**Form No form selected.**
Apply the necessary yaml file to your form. Or hide or delete the form plugin.
I have an TYPO3 installation with two domains. Each domain has its own provider extension and static template file.
Example:
domain1.com -> providerextension1
domain2.com -> providerextension2
Is it possible to hide the fluidcontent FCEs from providerextension1 in domain2.com?
Example from Bootstrappackage (https://github.com/Ecodev/bootstrap_package)
As soon as an extension has included fluidcontent FCEs (like the fluidcontent_bootstrap) it will add these to all domains, also when the TypoScript Configuration is not included.
If I understand the question completely, the answer is no: you cannot in TYPO3 make your TypoScript that is available in the backend, depend on the domain name being used. There is a way to make TypoScript conditions for the frontend output (for example a condition to only add template paths for your provider A when domain is X), but the same is not possible in the backend.
You are of course welcome to add a feature request on our issue tracker - I don't see any immediate problem with a feature to toggle on and off particular provider extensions based on for example a TypoScript setting. But you should keep in mind the limitation mentioned above since it implies that in order to achieve your desired goal you must place each domain record on a page tree of its own and closely manage the TypoScript that controls the available Provider Extensions on each page tree.
Put shortly: even if you get this feature request filled, it may not be the solution you want and you may have to restructure your pages and domains to get where you need to be.
The problem is, that the FCE are defined in the "ext_tables.php" and "ext_localconf.php" and these files are always loaded when the extension is enabled.
You can alter "ext_tables/ext_localconf" with a simple condition like
if($_SERVER['server_name'] == "www.yourdomain.com") {
//init FCEs here
}
You can try to override the template paths for one domain with an empty value or at least a path to an empty directory. Maybe flux is smart enough to ignore empty template paths.
I'm pretty new to TYPO3 and currently stuck with the following issue:
I copied the templates from another webpage that is currently in business.
When I'm on the startpage of my homepage (www.domain.com) and click on one of the links it contains I always get an error 404. The link that is generated looks like this.
http://www.domain.com/testpage.440.0.html
So I guess something like RealUrl was in use on the webpage that I copied from? Do I understand this right? I don't see that RealUrl is installed though.
However If i manually change this link to
http://www.domain.com/?id=440.0.html
the site is being created.
How does Typo3 know to generate a page when it receives the first version of these two links?
Does not really look like a standard out-of-the-box REAL URL url. That would rather have been /testpage-404.html . So maybe the problem is somewhere else, could be:
simulate static (check if that extension is running). A common mistake is to run real url an simulate static at the same time. If you do not need speaking urls for the moment, just uninstall simulate static.
make sure you add a domain to your shortcut. Use the the list modul and select the root shortcut. Then click create new record, select domain. and enter your domain there. Flush all the caches and try again.
If you'd post your TS Code (of the root shortcut page) here, I could probably tell what's going wrong.
real url configuration typically use .htaccess files.. maybe that file still contains information from the original destination.
check if the root ts contains some baseUrl statement
Which version of TYPO3 are you using?
HTH, but feel free to post more infos.
If your typoscript template is expecting to find realurl and its not installed as a plugin, that could be the cause. You'll need to either install it, or find the settings in the TS template and remove them.
Try the template object browser to look for it (use the template tool, click to the site root, then use the drop down menu in the r/h pane to choose the Template Obect Browser.)
How does Typo3 know to generate a page when
it receives the first version of these two links?
Any page request that it doesn't understand will give a 404 error.