I have TYPO3 7.6.18 and I have next problem: when I choose in browser console mobile mode - it logout FE user on my typo3 site. Why it happens ?
The problem is not the resizing but switching the user agent which is done if you e.g. select an Iphone. Until 8.7 (see https://docs.typo3.org/typo3cms/extensions/core/8.7/Changelog/8.6/Breaking-79513-RemovedSessionLockingBasedOnUseragent.html) the useragent was checked as well for a valid login.
Possible solutions:
Remove the keyword "useragent" from the configuration in the Install Tool
Update to 8.7
Related
Need a Login System on my Page but with integrated security Features ( like bruteforce login restriction)
downloaded this https://extensions.typo3.org/extension/flogin/
via composer on a freshly empty typo3 10.4.12 installation.
It appears in the Backend
I followed the documentation ->
https://docs.typo3.org/p/lms/login/9.0/en-us/Introduction/About/Index.html
Included the Static Typoscript in my Home / Root template
There lies the problem. The tutorial states add login form on expected page
->Tutorial Screenshot
But i checked everywhere but cant find that Login Form Element
Any Idea what iam missing?
Here is the answer directly from the Developer of this Extension
Thanks again very much!
In TYPO3 versions before v9, when using the native form, I always disabled the cache of that specific "contact" page (where the form was placed). If I didn't disable the cace, the form wouldn't redirect to my "confirmation" (v6/v7) or "redirect" page (v8), but instead it would simply reload the (filled-out) form (on the same page).
So, to bypass this and to make sure that the form actually got submitted and forwarded to the correct confirmation page, I always disabled the cache (Page Properties -> Page -> Behaviour -> Disable cache).
In TYPO3 v9 however, this option has been removed, and adding config.no_cache = 1 into that specific page (in a TS template), doesn't seem to do the (same) trick.
I would expect that the form, after clicking the submit button, would forward to the confirmation (redirect) page which I configured insde the form itself. That confirmation page isn't usergroup-protected or anything, it's simply a sub-page of the "contact" page (containing the form) itself.
The actual issue in this case is that you are most likely using some kind of autofill for your fields, e.g. from Chrome or using a form filler extension.
This will also fill the honeypot field of your form which then prevents submitting the form.
Right now there is nothing you can do about this except voting for the bug in the Chromium issue tracker.
As Mathias Brodola righfully points out, this seems to be a problem in Chrome only. I found this following plugin - that completely disables autocomplete support for a form - to be helpful in this matter. It solved my issue (however, it does completely disable auto-complete support for the form):
https://github.com/terrylinooo/jquery.disableAutoFill
I use tx_news 4.3.0 with TYPO3 7.6.12 and realurl 2.0.15
From time to time i get detail links which show to a wrong detail page.
e.g.
veranstaltungen/talks/detail/xy-talks/
shows to another detail page:
veranstaltungen/talks/detail/z-talks/
after clearing the fe cache the link ist ok.
how to avoid this?
I got the same problem some time ago.
I use for many TYPO3 system a single page for news list and detail.
I wanted to have URLs like example.com/news/ für list view and example.com/news/this-is-a-news/ as detail URL.
To archive this, I configured realurl to skip controller and action for news links. But in the link configuration inside the news template, they were used to build the link.
Since realurl does not create a new cHash for a link (since Version 2.0.12 I think), the link generated by realurl does not match the cHash that was generated in TYPO3 and cached by realurl. So TYPO3 provides a wrong cached version of this page. I my case, it was the first news entry, that were called and cached. This news entry got displayed every time I clicked on a news.
To avoid this, I removed the controller and action skipping from realurl and add some TypoScript (link.skipControllerAndAction = 1) to my news configuration.
I think you might have a similar issue. Try to disable realurl in a dev environment and try if this happens again. When this fixes your problem, check your realurl configuration for news.
I have a Plone 4.3.3 site. My logged in URL is different than the non-logged in URL. For example, the anonymous URL would be http://mysite.somewhere.com. When logged in, the URL is https://loggedin.mysite.somewhere.com.
When I create a link on a page and click save, if I view the page anonymously, the link is incorrect, displaying as the https version. However, if I go back and just open the page and click save, the link will be fixed and when view anonymously, it is fine.
These are internal links within the site and the site is not set to use UID's.
Any thoughts?
there is a bug report for this issue and it should have been fixed recently according to the comments there
https://dev.plone.org/ticket/13721
afaics 1.3.7 already contains this changes, so try to pin that version in your buildout
https://github.com/plone/Products.TinyMCE/commits/1.3.x
I am using the XFBML Facebook like button on my german website.
The locales were changed to de_DE to display "Gefällt mir" and it worked for some days.
But now it is ignoring the locales and everybody sees "Like".
I can not figure out why it has changed.
The used code is the same as before.
The used web server is located in germany.
My facebook account is set to german language.
What else could have an effect?
I have found my mistake...
My CMS also uses the possibility to login using a FB account.
For that it loads the javascript sdk again in the footer of the page.
This version was set to en_US!
which version of the javascript sdk u are loading in your page that contains the like button?
make sure you are loading the de_DE version