EzPublish AcitivityTimeOut Setting - content-management-system

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.

Related

Word add-in: The add-in could not be started with displayDialogAsync

I'm calling Office.context.ui.displayDialogAsync() in a word add-in. The dialog displays the message "ADD-IN ERROR The add-in could not be started. Please restart all Office applications and try again." But the displayDialogAsync() callback gives the succeeded status.
The page is a https URL with the same domain. (I'm testing on localhost.)
I can open the same URL with window.open() so I know the page exist.
Anyone knows what could be the reason for the error message, or how to get better diagnostics?
If you specified callback when calling the displayDialogAsync method, you may check result.error.code and result.error.message. As soon as you know what the actual error is, you can start troubleshooting, for example:
var dialog;
Office.context.ui.displayDialogAsync('https://myDomain/myDialog.html',
function (asyncResult) {
if (asyncResult.status === Office.AsyncResultStatus.Failed) {
showNotification(asyncResult.error.code = ": " + asyncResult.error.message);
} else {
dialog = asyncResult.value;
dialog.addEventHandler(Office.EventType.DialogMessageReceived, processMessage);
}
});
Check out the Handle errors and events in the Office dialog box for well-known errors.
Also you may find the Troubleshoot development errors with Office Add-ins page helpful.
Also make sure that the Protected mode is turned off in Windows.
In Windows 11, Protected Mode settings are missing in Internet Options, but you still can modify them via registry editor. These settings are stored in HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones. Under Zones is a subkey for each zone, named numerically:
0 is the Local Machine zone
1 is the Intranet zone
2 is the Trusted Sites zone
3 is the Internet zone
4 is the Restricted Sites zone
Under each numerically-named key, you can create or set a REG_DWORD value named 2500 to control whether Protected Mode is enabled for the zone. Setting that value to 0 enables Protected Mode; a setting of 3 disables it.
So, to disable Protected Mode for the Internet zone, set this entry to 3:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3\2500

How to disable TYPO3 backend logout screen

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

Quickfix reset sequence number at start time but not set ResetSeqNum in Logon message

When the quickfix initiator reconnects at startTime (defined in config) it deletes the files with sequence number, but does not set ResetSeqNumFlag to Y, and the server replies with a Logout message with text "seq msg number to low ..."
Is there a way to set ResetSeqNumFlag = Y only for this behavior? I don`t want to reset the sequence on every log-on.
This appears to be a QuickFIX/J quirk (some might consider it a bug). If ResetOnLogon=N then no ResetSeqNumFlag=Y is sent when the session start time triggers a logon. If ResetOnLogon=Y, the ResetSeqNumFlag=Y is sent on every logon. I believe this is not a big problem in practice because participants in a FIX session typically reset their sequence numbers locally after a session ends (logically ends at the end time, not a connection disconnect).
If you want to slightly modify the source code to implement this behavior, you'd modify the quickfix.Session next() method. You could add a local flag that indicates a session has restarted (per the schedule as determined by checkSessionTime()). Pass that flag to generateLogon() and that method would use it to determine when to send ResetSeqNumFlag=Y regardless of the ResetOnLogon configuration.
I don`t want to reset the sequence on every log-on.
Then don't do it! Set ResetOnLogon=N.
At StartTime, the session will reset sequence numbers always. If ResetOnLogon=N, then they won't reset again until the next StartTime.
The initiator and acceptor should always have matching ResetOnXXX settings.
What you are asking cannot, should not be done. You start you engine with some config and then you change the config while running. If something goes wrong it will be very difficult to pinpoint what started the issue.
Instead of doing ResetSeqNumFlag = Y try adding ResetOnLogon=Y in your config for the acceptor side(that is if you have control over it) or ResetOnLogout=Y / ResetOnDisconnect=Y in your initiator config file. That would be much easier and changing config while running, is possibly not the best solution.
Your logout(disconnect can happen anytime) will happen anyways at EndTime anyways and should be easier for your application.

WWW::Mechanize in Perl, Script Gets Killed

I have written a Perl Script which uses WWW::Mechanize to connect to a site, login and then visit a few pages inside the site. It all works good, however, when I try to visit a large number of pages, the script gets killed. I am sure this has got nothing to with the HTTP Server's Configuration and the connection limits configured. This is because, the script is running on my own site.
Here's a high level overview of my script:
$url="http://example.com";
$mech=WWW::Mechanize->new();
$mech->cookie_jar(HTTP::Cookies->new());
$mech->get($url);
login to the site using the form fields.
Now, once I am logged in, I connect to URLs within the site as follows:
$i is the iteration counter in a for loop
$internal_url="http://example.com/index.php?page=$i";
$mech->get($internal_url);
perform some operations on the page returned ($mech->content using HTML::TreeBuilder::XPath)
now, I iterate over the for loop connecting to a different internal_url, since the value of $i is incremented in every iteration.
As I said, it all works good. However, after about 180 pages, the script gets killed.
What could be the reason? I have tried multiple times.
I even added a $mech->delete; right before the end of the FOR loop to prevent any memory leak.
However, the only issue is that the login session which was maintained by $mech would be destroyed as a result of this.
I have tried multiple times and this script always gets killed after visiting the same number of pages.
Thanks.
Try this code:
$mech=WWW::Mechanize->new();
$mech->stack_depth(0);
OR
$mech=WWW::Mechanize->new(stack_depth=>0);
According to the docs: Get or set the page stack depth. Use this if
you're doing a lot of page scraping and running out of memory.
A value of 0 means "no history at all." By default, the max stack
depth is humongously large, effectively keeping all history.

the cmi.total_time parameter does not return anything

I am programming a SCORM 2004 product.
I can update the session_time, it works.
I can set the status (passed, failed, etc...)
I also can get the cmi.location time. No problems !
But I don't succeed to get the total time ! (cmi.total_time).
I have tested on 2 LMS :
On Ganesha the API.GetValue('cmi.total_time') is an empty string.
On Moodle the API.GetValue('cmi.total_time') is just a "P".
However i do have the correct logs with correct session times.
Anybody have an idea ?
Thank you !
EDIT.
I also try on cloud.scorm.com and cmi.total_time returns each time PT0H0M0S.
EDIT2. Ooops I deleted Donal's edit.
Based upon the information you've provided, I'm guessing that you're trying to set cmi.session_time and get cmi.total_time in the same learner session, which wouldn't give the response you're expecting.
cmi.total_time contains the total duration of all learner sessions prior to the current one, meaning that it won't contain the value you'd expect it to have until the second learner session.
Once you've set cmi.session_time, close the current learner session by leaving the SCO you're on, and then coming back to it. You should then see that cmi.total_time is now populated with a valid value.
Good Luck!
When you resume the second session and try to retrieve total time, are you able to retrieve the value you stored for cmi.location in the first session? If not, then you are probably not suspending the session. In order for data to be available in the next launch, you need to set cmi.exit to suspend before terminating the first session.
Mike