Thanks for the direction, I'll make sure to report to the web team if I find any more.
I'd be happy to start the process of requesting access to make those kinds of changes, if you need someone to make the stupid-quick fixes periodically. Thanks! Elliot J. Voris -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Lazar, Alexey Vladimirovich Sent: 10 October, 2013 10:26 To: Evergreen Community Web Team Email List Cc: Documentation discussion for Evergreen software Subject: Re: [Evergreen-web-team] [OPEN-ILS-DOCUMENTATION] A couple patches for Server Installation Instructions Ben, Besides yourself and Anoop, is there anyone else who actually access to make these changes? I remember quite a while back when I joined what I thought was the Evergreen webteam, my request to get access was denied. And no-one else on that team had access to the site either. Aleksey On 2013-10-10, at 10:09 , Ben Shum <[email protected]> wrote: > I noticed that there were some missing page warnings and have been trying to > deal with them as they occur. > > The trick here I think is to add 301 redirects straight in the apache config > to go from older php pages to newer wordpress ones. > > I'm literally just getting on a plane to my next destination, but if Anoop or > someone else on the web team can poke at it, cool. If not, I'll try taking a > look when I can. > > Thanks for bringing these issues to our attention. > > -- Ben > > Sent from my Samsung Galaxy S3 > > On Oct 10, 2013 10:24 AM, "Dan Scott" <[email protected]> wrote: > Problems with broken links should also be reported to the Web Team (CCed) so > that they can set up aliases for these URLs -- given that they are likely to > have been bookmarked & indexed & linked to from lots of other locations (like > third party "About Evergreen" pages, etc). Nothing wrong with changing the > docs to point at the new URLs, but let's tackle the problem from multiple > fronts. > > Does Piwik provide info about 404 pages so that we can correct URLs > accordingly? I took a quick peek at http://webstats.evergreen-ils.org but > didn't see anything relevant. Otherwise, combing through the Apache logs > might be worthwhile. > > > On Thu, Oct 10, 2013 at 3:59 AM, Elliot Voris <[email protected]> wrote: > I corrected a few links in the server installation instructions, after > opening a couple LP bugs: > > https://bugs.launchpad.net/evergreen/+bug/1237781 > https://bugs.launchpad.net/evergreen/+bug/1237785 > > I think I'm starting to get the hang of the EG git workflow. For DIG > purposes, do people tend to push to working/<username> repos, or mostly work > through patches? > > Thanks! > > > Elliot J. Voris > > IT Director > > St. Louis Christian College > > > [email protected] > > 314.837.6777 x1250 > > > _______________________________________________ > OPEN-ILS-DOCUMENTATION mailing list > [email protected] > http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation > > > > _______________________________________________ > Evergreen-web-team mailing list > [email protected] > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team > > _______________________________________________ > Evergreen-web-team mailing list > [email protected] > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team Aleksey Lazar IS Developer and Integrator - PALS http://www.mnpals.org/ _______________________________________________ Evergreen-web-team mailing list [email protected] http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team _______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
