User Tools

Site Tools


en:release:3.09_release_notes

Differences

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

Link to this comparison view

en:release:3.09_release_notes [2019/12/13 04:24] – [Troubleshooting] anupamaen:release:3.09_release_notes [2023/03/13 01:46] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +
 +
 +
 ====== Greenstone 3.09 Release Notes ====== ====== Greenstone 3.09 Release Notes ======
  
Line 7: Line 10:
 ** Released: ** ** Released: **
  
-   * Binaries for Windows, GNU/Linux 32 and 64 bit machines, a Mac binary for High Sierra/10.13 and Mac Mojave/10.(but may also work on Mac Sierra/10.12).\\ All the binaries have only been spot-tested, since the 3.09 release candidates, which came out a few weeks before, were tested more extensively on all the tutorials. Source distributions and source components compile on Windows 8. \\ [[http://svn.greenstone.org/main/tags/3.09/|svn tag page]] [[http://trac.greenstone.org/browser/main/tags/3.09|trac tag page]]. Code revision up to 33119. Tag revision: 33122.+   * Binaries for Windows, GNU/Linux 32 and 64 bit machines, a Mac binary for High Sierra/10.13 and Mac Mojave/10.14 (but may also work on Mac Sierra/10.12).\\ All the binaries have only been spot-tested, since the 3.09 release candidates, which came out a few weeks before, were tested more extensively on all the tutorials. Source distributions and source components compile on Windows 8. \\ [[http://svn.greenstone.org/main/tags/3.09/|svn tag page]] [[http://trac.greenstone.org/browser/main/tags/3.09|trac tag page]]. Code revision up to 33119. Tag revision: 33122.
       * The Mac binary is generated on High Sierra/10.13 and tested partially on that but mostly on Mojave/10.14.       * The Mac binary is generated on High Sierra/10.13 and tested partially on that but mostly on Mojave/10.14.
       * The Windows binary was largely tested on Windows 10, but partially on Windows 8.1       * The Windows binary was largely tested on Windows 10, but partially on Windows 8.1
Line 25: Line 28:
   * Download the appropriate binary release for your operating system and run it.    * Download the appropriate binary release for your operating system and run it. 
  
-  * **Note to Mac users:** The security settings in newer Mac OS versions have been altered to by default disallow users from casually opening and running .dmg executables that are not from Apple itself. When attempting to open the Greenstone binary .dmg file, if it pops up an error warning about security, you will need to set up the Security on your Mac to allow you to run .dmg files downloaded from the internet. Otherwise the Greenstone mac binary will not run. To do this, Go to your Mac's System Preferences. Under "Personal", select Security & Privacy. In the General tab, tick "Allow apps downloaded from Anywhere", then confirm that you want to "Allow From Anywhere". You'll need to be admin to do this, otherwise click on the padlock at the bottom left of the Security & Privacy tab and log in as admin.+  * **Note to Mac users:** The security settings in newer Mac OS versions have been altered to by default disallow users from casually opening and running .dmg executables that are not from Apple itself. When attempting to open the Greenstone binary .dmg file, if it pops up an error warning about security, you will need to set up the Security on your Mac to allow you to run .dmg files downloaded from the internet. Otherwise the Greenstone mac binary will not run. To do this, go to your Mac's System Preferences. Under "Personal", select Security & Privacy. In the General tab, tick "Allow apps downloaded from Anywhere", then confirm that you want to "Allow From Anywhere". You'll need to be admin to do this, otherwise click on the padlock at the bottom left of the Security & Privacy tab and log in as admin.
  
   * **For Linux**, you will need to set the file to be executable before running it. (e.g. chmod a+x Greenstone-3.09-linux)   * **For Linux**, you will need to set the file to be executable before running it. (e.g. chmod a+x Greenstone-3.09-linux)
Line 211: Line 214:
 Put these two together with a period mark to separate them and use this as the value for your tomcat.server property.) Put these two together with a period mark to separate them and use this as the value for your tomcat.server property.)
  
-4. Set up your Greenstone environment if you've not already done so by running ''gs3-setup.bat'' in your Greenstone 3 installation folder (''source ./gs3-setup.bash'' on Linux and Mac machines). And then start up your Greenstone 3 server with:+4. Set up your Greenstone environment if you've not already done so by running ''gs3-setup.bat'' in your Greenstone 3 installation folder (''source ./gs3-setup.sh'' on Linux and Mac machines). And then start up your Greenstone 3 server with:
 <code> <code>
 ant start ant start
Line 333: Line 336:
 ==== Troubleshooting ==== ==== Troubleshooting ====
  
-=== You see an empty page when visiting the Greenstone 3 library home page === +=== Some perl scripts don't run properly or to completion === 
-If you're running Greenstone 3 on a non-English locale, then your library home page may look entirely empty. To resolve these and other locale and encoding related issues, refer to [[http://wiki.greenstone.org/doku.php?id=en:supporting_other_locales|http://wiki.greenstone.org/doku.php?id=en:supporting_other_locales]].+//**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]]. 
 + 
 +=== You see an empty page when visiting the Greenstone 3 library home page on Windows === 
 +//**If you're running Greenstone 3 on a non-English locale on Windows**//, then your library home page may look entirely empty. To resolve these and other locale and encoding related issues, 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 ===  === Content Encoding Error when visiting the local solr servlet page === 
Line 425: Line 431:
 If you get this error, then please install the CGI module for your system perl. If you get this error, then please install the CGI module for your system perl.
 ====Work Arounds==== ====Work Arounds====
-===Filenames in collections should not contain &, < and >=== +===Filenames in collections should not contain < and >=== 
-In order to have better handling of different file and filename encodings, [[http://trac.greenstone.org/changeset/29793|sacrifice]] [[http://trac.greenstone.org/timeline?from=19.03.2015&daysback=30&ticket=on&changeset=on&milestone=on&wiki=on&update=Update|was made]] of being unable to support &, < and > characters in filenames. Filenames with such characters will make metadata.xml invalid, as a result of which, GLI won't be able to reload the metadata therein.+[**Note:** [[https://stackoverflow.com/questions/1976007/what-characters-are-forbidden-in-windows-and-linux-directory-names|Windows disallows < and >]] characters in filenames anyway, so it's best to avoid such filenames even on other Operating Systems in cases where you may tranfer a Greenstone collection with documents' filenames containing < or > from one operating system to a GS3 running on Windows at any point.] 
 + 
 +In order to have better handling of different file and filename encodings, an [[http://trac.greenstone.org/changeset/29793|sacrifice]] [[http://trac.greenstone.org/timeline?from=19.03.2015&daysback=30&ticket=on&changeset=on&milestone=on&wiki=on&update=Update|was made]] of being unable to support &, < and > characters in filenames. In Dec 2019, which is months after 3.09's release, Greenstone was modified so that GLI can now accept & in filenames. However, filenames containing < and > characters continue to make metadata.xml invalid, as a result of which, GLI won't be able to reload the metadata therein
 + 
 +A workaround is to use different characters for < and >, such as [ and ] or ( and ), or leave them out from filenames.
  
-A workaround is to use "and" in place of "&" in filenames. And either use different characters for < and >, such as [ and ] or ( and ), or leave them out from filenames. 
 ===Greenstone applets (Phind, Collage) crash Firefox=== ===Greenstone applets (Phind, Collage) crash Firefox===
 See [[https://bugzilla.redhat.com/show_bug.cgi?id=789959|bugzilla report]]. See [[https://bugzilla.redhat.com/show_bug.cgi?id=789959|bugzilla report]].
en/release/3.09_release_notes.1576211074.txt.gz · Last modified: 2019/12/13 04:24 by anupama