On May 25, 2012, at 13:31 , Kathy Lussier wrote:
In addition to the link Ben provided, another resource that might help people
determine if tpac is stable enough is the list of submitted Launchpad bugs
that use a tpac tag.
https://bugs.launchpad.net/evergreen/+bugs?field.tag=tpac
I
On May 30, 2012, at 1:17 PM, Lazar, Alexey Vladimirovich
alexey.la...@mnsu.edu wrote:
So now, the questions is, where is the proper place for this to be added to
documentation?
Alexey Lazar
PALS
Information System Developer and Integrator
507-389-2907
http://www.mnpals.org/
On Thu, May 24, 2012 at 3:29 PM, Lazar, Alexey Vladimirovich
alexey.la...@mnsu.edu wrote:
I've got that line commented as well. If you have OILSRedirectTpac commented
it still goes to the JSpac.
I tried using
RedirectMatch 301 ^/$ /eg/opac/home
and also commenting that redirect line
I am a little confused on what your /etc/apache2/eg_vhost.conf ended
up looking like when you finally got TPAC as the default OPAC. Do you
(or anyone else) mind posting the relevant parts so I can see, for
example, which lines ended up being commented or commented out versus
edited?
Sure. I
We noted several of those missing features during our review but did not
consider them to be serious deal-breakers against adopting Tpac. As far as
stable and well tested though, my opinion is that it should definitely
fulfill the intended replacement for the simple catalog. But I think
Hi Alexey,
I'm a little late on this thread, but, maybe to help re-affirm your
decision, I wanted to mention that two of the MassLNC consortia are
planning to go live on Evergreen next week, and both have opted to set
tpac as the default catalog.
We went through a review similar to the one
In the Evergreen 2.2 RC1 I just installed, how do I enable TPAC by default?
Would that be a good idea at this point, or is it too early?
To clarify my own words, is TPAC stable and tested well enough for a production
environment?
Alexey Lazar
PALS
Information System Developer and Integrator
For 2.2, the goal was to replace the original slimpac (simple OPAC) with
Tpac and it is there now as the simple catalog. However, there is still
ongoing work to further enhance and refine various aspects and add
features to Tpac before it will fully replace the JSPac. The projected
time
Hi, Justin.
I uncommented this whole section, including the line you mentioned:
LocationMatch ^/$
SetHandler perl-script
PerlHandler OpenILS::WWW::Redirect
Options +ExecCGI
PerlSendHeader On
#PerlSetVar OILSRedirectSkin default
# OILSRedirectDepth defaults to the depth of
In the Evergreen 2.2 RC1 I just installed, how do I enable TPAC by default?
Would that be a good idea at this point, or is it too early?
When the final Evergreen 2.2 comes out, what will be the update path from 2.2
RC1 to 2.2 final?
Also, what will be the update path from OpenSRF 2.1 RC1 to
Hi Alexey,
To enable Tpac just uncomment the line:
PerlSetVar OILSRedirectTpac true
in /etc/apache2/eg_vhost.conf (assuming you're on debian) then restart apache.
Cheers,
Justin
On May 23, 2012, at 5:04 PM, Lazar, Alexey Vladimirovich wrote:
In the Evergreen 2.2 RC1 I just installed, how do
11 matches
Mail list logo
