Differences

This shows you the differences between two versions of the page.

--- en:release:3.10_release_notes [2021/09/30 02:58] – anupama
+++ en:release:3.10_release_notes [2023/07/06 03:05] (current) – anupama
@@ Line 14: / Line 14: @@
 ** Release Candidate History **
-  * Greenstone 3.10 rc1: Release Candidate 1. Released 6 Dec 2020.\\ Binaries for Windows, GNU/Linux 64 bit, Mac Mojave/Catalina. Mac version generated on MacOS Mojave/10.14 and tested predominantly on Catalina/10.15. See notes immediatebly below.\\ Download from the [[http://www.greenstone.org/snapshots|snapshots]] page\\ [[https://svn.greenstone.org/main/tags/3.10rc1/|svn tag page]] [[https://trac.greenstone.org/browser/main/tags/3.10rc1|trac tag page]]. Code revision up to 34587. Tag revision:34590.
+  * Greenstone 3.10 rc1: Release Candidate 1. Released 6 Dec 2020.\\ Binaries for Windows, GNU/Linux 64 bit, Mac Mojave/Catalina. Mac version generated on MacOS Mojave/10.14 and tested predominantly on Catalina/10.15. See notes immediately below.\\ Download from the [[http://www.greenstone.org/snapshots|snapshots]] page\\ [[https://svn.greenstone.org/main/tags/3.10rc1/|svn tag page]] [[https://trac.greenstone.org/browser/main/tags/3.10rc1|trac tag page]]. Code revision up to 34587. Tag revision:34590.
 **GS3.10rc1 issues and unknowns on Catalina Mac:**
@@ Line 111: / Line 111: @@
 ==== Setting up your Greenstone to run over https ====
-//**Note:** This section is untested for this release, as the prevalent method of supporting https for tomcat based servers appears to be to have a main apache httpd web server that works with https, then set up a ''reverse proxy'' to let apacha httpd redirect requests for GS3's tomcat server internally to Greenstone.//
+//**Note:** This section is untested for this release, as the prevalent method of supporting https for tomcat based servers appears to be to have a main apache httpd web server that works with https, then set up a ''reverse proxy'' to let apache httpd redirect requests for GS3's tomcat server internally to Greenstone.//
 The more secure https protocol is increasingly required by browsers and gradually superseding http. Given that you meet the following requirements and configure your GS3 as below, Greenstone 3 has now been automated to obtain an https certificate for you from the free Certification Authority "Let's Encrypt".
@@ Line 285: / Line 285: @@
   * consult the more detailed instructions on the [[en:user_advanced:remote_greenstone|Remote Greenstone page]] for further steps that may be necessary to carry out.
+If you are using perl 5.22 or later, these no longer come with the perl CGI module. Please download https://trac.greenstone.org/export/36059/main/trunk/greenstone2/common-src/cgi-bin/CGIModule.tar.gz into web/WEB-INF/cgi, untar it, and copy the contents of the resulting CGIModule folder up one level (i.e. outside of that folder).
 **Client-GLI**
@@ Line 377: / Line 378: @@
 === Some perl scripts don't run properly or to completion ===
 //**If you're running Greenstone 3 on a non-English locale**// and certain perl scripts don't run properly or completely, such as when you run ''perl -S pluginfol.pl -describeall'', then the problem may be locale/encoding related. To resolve this issue, refer to [[en:supporting_other_locales|Supporting running Greenstone in other locales on Windows 10]].
 === Content Encoding Error when visiting the local solr servlet page ===
 If you see a Content Encoding Error when opening your GS3's solr servlet page at ''http://127.0.0.1:8383/solr'' or ''http://localhost:8383/solr'' in your browser, then this may have to do with the version of Java you have installed on your machine. From GS3.09 onward, if your machine has its own Java installed, then assuming that its version is sufficient and its bit-architecture (32 or 64 bit) matches, Greenstone will use your Java in preference to the bundled Java Runtime (JRE) that Greenstone ships with. We found that a recent version of Java (version 1.8.0_161 was problematic for us), caused the Content Encoding Error when visiting the solr servlet, whereas the bundled JRE and slightly earlier and much newer versions of Java such as 1.8.0_144 and 1.8.0_191 did not have these issues.
@@ Line 383: / Line 385: @@
 - either unset JAVA_HOME and remove this Java's ''bin'' folder from the PATH environment variable too, thus helping Greenstone 3 use its bundled JRE instead
 - install a newer version of Java on your system. We found that the current latest one, 1.8.0_191 worked successfully for this purpose.
 === SIGPIPE errors when building a collection ===
@@ Line 388: / Line 391: @@
   * change the database type from ''jdbm'' to ''gdbm''
   * or leave the database type at ''jdbm'' and move your GS3's bundled JRE (the GS3's ''packages/jre'' subfolder) outside your GS3 installation. Next install a newer Java on your system so that GS3.09 can find that. If on Linux, ensure you open a new terminal before running GLI or command line building your collection.
 === Your browser doesn't remember you being logged into greenstone ===
 **The issue:**
@@ Line 467: / Line 472: @@
 Compilation failed in require at (eval 1) line 1.
 </code>
+CGI.pm is not included with versions of [[https://stackoverflow.com/questions/45434990/why-does-this-code-have-issues-with-the-cgi-module|perl from 5.22 and onwards]], which is when this issue can result.
 If you get this error, then please install the CGI module for your system perl.