How to disable TYPO3 backend logout screen - typo3

I want to disable the logout feature. I want stay logged in lifetime.
I tried to :
set [FE][lifetime] = 86400 (at least one day)
set [FE][permalogin] = 2
set [BE][lockIP]=0
set [BE][sessionTimeout] = 3600
But the system quicks me out in few min.

Try to use below typoscript.
['BE']['sessionTimout'] to 3600*24*7

Related

How do I reset a variable at the start of each day?

I have a variable that keeps track of user statistic I want to reset at the beginning of each day. How can I do that?
Since the application is not allowed to run in the background, it seems I will have to do the check every time the application is active but I don't know how to reset the variable I have only once. This is the function I wanted to use:
let beginingOfDay = NSCalendar.currentCalendar().startOfDayForDate(NSDate())
func resetCurrentTime(){
// Date comparision to compare current date and begining of the day.
let dateComparisionResult:NSComparisonResult = NSDate().compare(beginingOfDay)
if dateComparisionResult == NSComparisonResult.OrderedDescending || dateComparisionResult == NSComparisonResult.OrderedSame {
// Current date is greater or equal to end date.
currentTime = 0 //reset the time tracker
}
}
I wanted to use this function to check when the application is launched but the problem is that the application could be launched many time a day. How I can reset my variable only once at the beginning of a day if the user is using the application or when the application becomes active or is launched for the first time that day?
Thanks
You can store in the user defaults this value.
So the flow is the following:
When the app is launched or became active you check whether the value of the variable in the user defaults is the same as the current day (e.g. 25/07/2016), then do nothing.
If the value is different, then you update the value in the user defaults with the current day.
If the app is running and the date is changed, you can update the value of your variable by subscribing to this notification:
UIApplicationSignificantTimeChangeNotification

How can I update a dashing widget's refresh frequency?

I'm current using Dashing for displaying dashboards on our office TVs. By default each of our widgets gets refreshed every 60 seconds.
I actually would like to change this to 30 seconds. Does anyone know how to do this?
Take a look at each widgets associated .rb file, you should find something similar to this (taken from my news.rb). note '60m' is 1-hr. In your file change it to '30s'
SCHEDULER.every '60m', :first_in => 0 do |job|
#News.each do |news|
headlines = news.latest_headlines()
send_event(news.widget_id, { :headlines => headlines })

How can I set specific duration for each dashboard using gem SinatraCyclist?

Is there a way to set specific time/duration for specific dashboard using
gem 'sinatra_cyclist' link here.
Documentation says,
Usage
require "sinatra/base"
require "sinatra/cyclist"
class MyApp < Sinatra::Base
register Sinatra::Cyclist
set :routes_to_cycle_through, [:dashboard_1, :dashboard_2]
end
You can also specify a duration (in seconds) in the params to the cycle action
http://sinatra_app.com/_cycle?duration=10
Yes, it will cycle the 2 dashboards.
Is it possible (or not) to set for example 60 seconds for the 1st dashboard and 30 seconds for the 2nd?

EzPublish AcitivityTimeOut Setting

Good Day Guys,
I'm wondering if it's possible to set the ActivityTimeOut Setting for 30 days?
I actually tried putting it on 30 days... 2592000 secs = 30days..
however after several hours of inactivity EzPublish logout my account.
As per the eZ Publish documentation :
# Number of seconds before a session is considered inactive/logged out, 1 hour is standard
ActivityTimeout=3600
Looking at the kernel code, where this setting is used, it looks like that it does not have any effect on really disconnecting a user, it's just about considering a user as inactive (via the fetchLoggedInList function for instance) which is used in the Admin > Sessions section of the admin interface (if you're using sql stored session, which is not the default behavior in the last 4.x versions of eZ Publish).
Have you tried and checked these parameters ?
[Session]
# "Remember me" feature of the login.
# Number of seconds a session cookie will last,
# if an user wants to store current session to the cookie
# should click on "Remember me" checkbox on login page.
# Empty or 0 means this ability will be disabled and CookieTimeout will be used.
RememberMeTimeout=
# Number of seconds a session will last, 3 days is standard
SessionTimeout=259200
# Number of seconds a session cookie will last,
# 0 means until browser is closed
# Leaving the field empty means to use the default PHP settings (session.cookie_lifetime)
CookieTimeout=
As you can see, cookies are by default controller by your PHP server configuration, so you should have a look here too.

UIAutomation timeouts usage

Guys help me to understand the timeouts usage. The documentation gives quite a couple of words about them:
popTimeout- Retrieves the previous timeout value from a stack, restores it as the current timeout value, and returns it.
pushTimeout - Stores the current timeout value on a stack and sets a new timeout value.
They also provide some code:
target = UIATarget.localTarget();
target.pushTimeout(2);
// attempt element access
target.popTimeout();
But I don't exactly understand how and when to use them. Can anybode give an example?
During automation testing, some elements might not become visible right away. so instruments uses a timeout (default 5 seconds) to wait for requested elements. They call this the grace period.
Sometimes the default grace period might not be what you need, so you can change the timeout to a shorter or longer value.
Using the pushTimeout and popTimeout makes sure that the previous grace period is restored after calling popTimeout, without the need to remember the previous grace period.
For example: in one of my tests, I don't want to wait for a popover to become active, but I just want to know if there is a popover active, and dismiss it if there is:
target.pushTimeout(0.0);
if ( target.isDeviceiPad() && ! isNull( popOver= app.mainWindow().popover() ) )
{
UIALogger.logDebug(" dismiss popup by tapping somewhere");
popOver.dismiss();
target.delay(0.2);
}
target.popTimeout();
BTW, the isNull() is a custom function I made, but you probably understand what is going on.