Admin Timeout Much TOO SHORT

[Guest]

Hi there... a simple & quick, but important question, after vainly searching the old Forum notes, please:

~>

The Admin TIMEOUT is much too short for us.

~

We have complex things to do in many languages...and oceans of code to manipulate.

Often when a task is finished and we save, we lose everything...as the system takes us back to the admin login and we LOSE EVERYTHING that was so painfully prepared...

It's insanely frustrating...hours and hours lost...gggrrrrrrrrrrr...

 

I know the short timeout was a normal security idea for an 'open desktop,' but we don't have that problem, thankfully.

We need tweaking time and lots&lots&lots of it!

~

HOW & WHERE can we make Admin Timeout much, Much, MUCH LONGER? ...please???

:rolleyes:

Many Many Thanks!!!!

[♥Vger]

Look in php.ini for the entry that controls the amount of time allowed to carry out PHP functions - which is usually set to 30 seconds.

 

Vger

[Guest]

Oooh; you are good!

Thank you!

Is there an upper limit before this becomes a giant furrball?

Thanks so much for your patience!

[♥Vger]

Any more than 60-90 seconds (max) and you could tie up the whole server.

 

Vger

[Guest]

HI Vger,

...thanks for the info, but ut oh, ...not such good news...

Does this mean please that the server is effectively 'frozen' while someone is using admin?

Are transactions happening? Is browing somehow restricted? Are transaction related emails/SMS notices going out?

In fact, what does this mean please? Please elaborate....thanks!

I assumed, apparently <very wrongly>, that the current and most recent "save" of data was LIVE, until a fresh set replaces it in the database...and then that is live. I assumed that what I was doing was separate until I send it back inside, but that the timeout was there to prevent unauthorized users from getting on an un-occupied/un-protected pc.

I appreciate that there is no db rollback function yet.

We have a lot of tweaking to do for langauges and my admittedly limited experience is that with lots of languages and oceans of invisible code behind them, layouts are more reliable/effective for me to work on in real time in one window and to inspect the results in another window, using the FCKeditor contribution.

:rolleyes:

Newbie here...You are the expert here....I am just a raw newbie, so Thanks for the follow-up guidance, in advance, here. Yes, just a dummy newbie here... I apologize.

[♥Vger]

The reason for limiting the amount of maximum execution time for any php script is to guard against scripts that are bugged - with a large execution time the script could go around in ever decreasing circles, tieing up your servers' processing power (preventing anyone else from accessing your site, because it's "busy") and really racking up your bandwidth usage.

 

The max execution time would only be used by a script that needed it, so wouldn't at other times tie up your website (apart from a bugged script).

 

Take a look at a thread in the Tips & Tricks forum called "A Store Speed Optimisation - work in progress" by an ex-member of these forums. It will show you how to cut out unnecessary database queries and reduce the load time of your website (and the load placed on the server).

 

Vger