Bug #2527

Max execution time limit on sfLucenePlugin

Added by Peter Van Garderen over 13 years ago. Updated about 9 years ago.

Status:Won't fixStart date:
Priority:LowDue date:
Assignee:Jesús García Crespo% Done:

0%

Category:-
Target version:Release 1.4.0
Google Code Legacy ID:atom-576 Tested version:
Sponsored:No Requires documentation:

Description

Increase the max execution time somewhere in the project code so that each
installation doesn't have to tweak this in their own server settings

[g] Legacy categories: Installation

History

#1 Updated by Anonymous almost 12 years ago

  • Priority set to Low

[g] Labels added: Priority-Low

#2 Updated by Evelyn McLellan over 11 years ago

  • Target version set to Release 1.2

Moved to 1.2.

[g] Labels added: Milestone-Release-1.2

#3 Updated by David Juhasz over 10 years ago

  • Target version set to Release 1.3

Roll over to Release 1.3

[g] Labels added: Milestone-Release-1.3

#4 Updated by Anonymous about 10 years ago

Ideally make the timeout configurable by Admin, and add a session timeout warning.

[CCAD-46]

[g] New owner:

#5 Updated by Anonymous about 10 years ago

  • Target version changed from Release 1.3 to Release 2.1.0

[g] Labels added: Milestone-Release-2.0
[g] Labels removed: Milestone-Release-1.3

#6 Updated by Jessica Bushey almost 10 years ago

[g] New owner: Jessica Bushey

#7 Updated by Jesús García Crespo almost 10 years ago

[g] New owner: Jesús García Crespo

#8 Updated by Jesús García Crespo over 9 years ago

  • Subject changed from max execution time limit on sfLucenePlugin to Max execution time limit on sfLucenePlugin
  • Status changed from New to Won't fix
  • Sponsored set to No

sfLucenePlugin is being removed in favor of arElasticSearchPlugin.

#9 Updated by David Juhasz about 9 years ago

  • Target version changed from Release 2.1.0 to Release 1.4.0

Also available in: Atom PDF