Add KPAC configuration information to the community docs

Bug #1116387 reported by Kathy Lussier
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
2.6
Fix Released
Undecided
Unassigned
2.7
Fix Released
Undecided
Unassigned

Bug Description

Some useful KPAC configuration information was sitting in the TechRef directory of the Evergreen repository and, after some discussion in IRC today, we thought it would be useful to include in the community docs. This commit:

* Includes KidsOPAC.txt in the root.txt file so that it will be included in the community docs.
* Adds some information to KidsOPAC.txt on configuring kpac to use the alternate skin. This information is based on code that berick shared in IRC and could probably use some review.
* Removes a reference in the end-user kpac docs on where to find configuration information.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/kmlussier/kpac-doc-addition

Documentation will need to be added to master and to 2.3.

Revision history for this message
Ben Shum (bshum) wrote :

Hmm, some minor changes necessary to the alternate skin configuration steps so that they'll work better I think. Great start though!

Changed in evergreen:
importance: Undecided → Medium
milestone: none → 2.4.0-alpha
status: New → Triaged
Ben Shum (bshum)
Changed in evergreen:
milestone: 2.4.0-alpha1 → 2.4.0-beta
Ben Shum (bshum)
Changed in evergreen:
milestone: 2.4.0-beta → 2.4.0-rc
Ben Shum (bshum)
Changed in evergreen:
milestone: 2.4.0-rc → none
assignee: nobody → Ben Shum (bshum)
Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

I noticed that the default skin for the kpac on my 2.6 test system is the alternate skin according to what is listed at
http://docs.evergreen-ils.org/dev/_kids_opac.html#_choose_a_skin

So should the docs say "How to enable the monster skin"? kpac2 seems to be the monster skin.
http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=cf4875ecf60b8d907310f9881c39c6a96f6d8652

Should the Alternate Skin be called "The default Skin" or something other than alternate?

Josh

Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

The instructions for copying the files worked without any problems... although I already had an alternate template location setup for the opac, so I just copied the monster skin template files into that template folder, and I didn't need to touch apache for it to work correctly.

So maybe there should be a note saying something along those lines. The template redirection is so flexible it is hard to document every eventuality.

I will test out the listed apache setup next to see if there are problems with it.

Josh

Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

I found that the minimum required apache config change if you want a separate template dir for the kpac is

 <Location /eg/kpac>
         PerlAddVar OILSWebTemplatePath "/openils/var/templates_kpac2"
 </Location>

The other options are already loaded globally in the default install for 2.6. I would guess that is the case for 2.5 and 2.7 also. Maybe in 2.3 those were required, but I don't think they are any more.

Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

I made the changes that I mentioned, and got setup to use the EG git instead of github, Yeah. Ben if you could be more specific about what changes are needed that would help. I went though the docs and tried them out on my 2.6 test system and everything worked as described.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1116387_kpac_docs

Revision history for this message
Galen Charlton (gmc) wrote :

As part of pulling in the fix for 1083639, I've pushed these changes as well to master, rel_2_7, and rel_2_6. Thanks, Josh!

Changed in evergreen:
assignee: Ben Shum (bshum) → nobody
tags: added: pullrequest
no longer affects: evergreen/2.3
no longer affects: evergreen/2.4
Changed in evergreen:
milestone: none → 2.next
status: Triaged → Fix Committed
Revision history for this message
Ben Shum (bshum) wrote :

Removing 2.next top level milestone, since this was a bug fix that was repaired in an actual series maintenance release.

Changed in evergreen:
milestone: 2.next → none
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.