we'd like to implement an obligatory update of given passwords by frontend user.
Our setting is the follow: TYPO3 8.7 / femanager 3.3.0
Any ideas or do we just miss a feature?
Many greetings
Daniel
There is another TYPO3 extension dealing with this issue: https://extensions.typo3.org/extension/feloginforceupdate/
It depends on ext:femanager and is compatible with TYPO3 7.x but I got it running with TYPO3 8.7 without hassle.
There is an old extension (up to 6.2) which handles password expiration: ext:lwpasswordexpire.
Either you motivate the author to do an update
or you give the author a pullrequest
or you get the idea to implement it anew in your installation
or you extend ext:femanager with password expiration handling
Related
In an extension we build for TYPO3 8 we check if a URL entered by a user is a local URL by checking the domain against records in the sys_domain table. We're now updating that extension for TYPO3 9 and 10. sys_domain has been deprecated in TYPO3 9 and removed in 10. It has been replaced with settings in the site configuration.
Is there an easy way to fetch all known base URLs (including variants and languages) from the site configuration without parsing and looping through the site configuration myself?
Yes it is possible. You need to use the PHP API: Accessing Site Configuration
here is an example:
$siteFinder = GeneralUtility::makeInstance(SiteFinder::class);
$allsites = $siteFinder->getAllSites();
This is the results
Best regards
What is the best way to handle OOTB model's removed attribute?
In hybris version 6.6, there is bundleNo attribute in AbstractOrderEntryModel, then we're upgrading our hybris version, and we found out that on 1905, bundleNo attribute is no longer there. So do we have to re-add bundleNo attribute to AbstractOrderEntryModel or should we use another OOTB attribute that's available, considering in 6.6 we have some data using that attribute?
Thanks
Indeed bundleNo attribute is deprecated since the 6.4 version, entryGroupNumbers should be used instead for the recent versions, it supports a set of ids now :
https://help.sap.com/doc/a4265d5ea8314eb2929e6cf6fb8e35a5/1811/en-US/de/hybris/platform/core/model/order/AbstractOrderEntryModel.html
so i was on vacation for 5 Days and when i came back our Website (Typo 3 - 7.6.25) was "broke".
If i try to go on the page i get the following Error:
#1205414233: No suitable request handler found.
TYPO3\CMS\Extbase\Mvc\Exception thrown in file
/html/typo3/typo3_src-7.6.25/typo3/sysext/extbase/Classes/Mvc/RequestHandlerResolver.php in line 83.
Neither me nor anyone else in my company changed something on the Typo3 Website in the past 5 Days.
I've tried to search for Solutions but neither of them helped.
Sadly we have no Backups (This will be Priority 1 after this).
I've also found a Typo3 Website talking about that problem here: https://wiki.typo3.org/Exception/CMS/1205414233
but i dont know where to include the code given by this Site.
Does anyone know what I can do with this Error?
Thanks.
first of all TYPO3 7.6.25 is from 13.03.2018. The last free release is 7.6.32 from 11.12.2018. There are many security updates since your version. If you buy ELTS you can download and install 7.6.41 ELTS (28.01.2020) Maybe this will help with your problem.
Other things you can check: Hosting Provider changes php version or mysql? I really think you should try update to TYPO3 8.7 and test again. Backup your site befor update.
It seems this can have different reasons. In my case (in TYPO3 8.7) the problem was triggered from comments in TypoScript. I've used a (valid!) multi line comment:
plugin.tx_myplugin {
settings {
firstsetting = 1
/*secondsetting = 2
thirdsetting = 3*/
}
}
In the "TypoScript Object Browser" there was a warning, it seems TYPO3 had problems parsing TypoScript due to this comment.
I'm trying to setup the REST-Extension v2 in TYPO3 8.7 following this tutorial. I included the 2 templates called Virtual-Object-Page and Virtual-Object-Content in my template. I made a new extension using Extension Builder 8.7 from Github with a simple model. I installed the new extension and made some Instances of my model in the List View on my start page. In the Typoscript of my template I added:
plugin.tx_rest.settings.paths {
1 {
path = me-kinder-child
read = allow
write = allow
}
}
Me is the Vendor, kinder my extension key and child is my model.
When I'm calling http://localhost/rest/ I get The requested URL /rest/ was not found on this server.
What am I missing?
The path in the setup is explained being possible with several options, so perhaps try different configuration, possible is also all.
I don't see a fault in your setup, so the fault might be related to the server-file .htaccess or the extension realurl respectively the combination of both perhaps.
If you try it already with realurl or cooluri then disable that to get it running without first.
The htaccess file you can disable first too and enable it later again to adjust all requirements to each other.
The problem was not about RealURL was missing in any way. I just did not clear a cache that got cleared while installing RealURL. I guess that the "Clear all caches"-button in the Install-Tool would do it too.
we are using Typo3 7.6.6 for our new homepage. To simplify the process of writing new articles, we introduced the extension TinyMCE4 as TYPO3 RTE. On our test-system tinyMCE works fine, the editors are satisfied.
To prepare for production environment we introduced SSL. Hence the homepage is referenced over https://....
Since this change tinyMCE no longer appeared. After some research we found out, that the tinyMCE extension tries to load a specific dynamically generated js-file tinymceConfiguration....js over HTTP (not over SSL as preferred).
Since we have a strict policy, the server doesn't allow the client to catch the script without using SSL. Unfortunately we cannot change that policy.
The question is: where does the extension get the URL from. Can I overwrite it to reference the https://.. path?
I already tried changing
config.baseURL
tinyMCE.init({
...
document_base_url : "https://.."
});
But it didn't work.
Does anybody have an idea?
Regards,
Thomas
you could try to tell your browser to use "Content-Security-Policy" in that way all http links are rewriten by the browser itself. Maybe the lazy way.
https://developers.google.com/web/fundamentals/security/encrypt-in-transit/why-https?hl=en
http://www.html5rocks.com/en/tutorials/security/content-security-policy/
Regards
Pete