Differences

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

--- en:release:3.09_release_notes [2018/03/05 05:33] – anupama
+++ en:release:3.09_release_notes [2018/09/13 02:59] – anupama
@@ Line 14: / Line 14: @@
   * **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.08-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)
     * The installer initially unpacks into a temporary directory (/tmp on linux). If you wish to change this, set the TMPDIR environment variable.
 Note that in some cases, the following **doesn't** work
 <code> export TMPDIR=/something/else
- ./Greenstone-3.08-linux</code>
+ ./Greenstone-3.09-linux</code>
 Use the following instead
-<code> TMPDIR=/something/else ./Greenstone-3.08-linux</code>
+<code> TMPDIR=/something/else ./Greenstone-3.09-linux</code>
 During the installation process you will be presented with several options. For many, the default settings will be sufficient. Some important options are
@@ Line 38: / Line 38: @@
 <!--
 === Installing and running GS3.09 on Mac Maverick and Yosemite machines ===
-From GS3.07rc**2** onwards, we're including a JRE with Mac Mountain Lion binaries, so that the **3.08 Mountain Lion binaries should work on Maverick and Yosemite machines out of the box.** (At present the source code still does not compile up on these newer Mac Operating Systems.)
+From GS3.07rc**2** onwards, we're including a JRE with Mac Mountain Lion binaries, so that the **3.09 Mountain Lion binaries should work on Maverick and Yosemite machines out of the box.** (At present the source code still does not compile up on these newer Mac Operating Systems.)
 -->
@@ Line 187: / Line 187: @@
   - Next, generate the SignedGatherer.jar:
       * Use a terminal to go into the Greenstone "gli" directory, then run <code>    keytool -genkey -alias privateKey -keystore appletstore -storepass greenstone</code> Enter the appropriate details for your organization. When it asks to enter the key password for <privateKey>, choose your own password or hit Enter to use "greenstone".
-      * Next, run
+      * Next, run <code>    jarsigner -keystore appletstore -signedjar SignedGatherer.jar GLI.jar privateKey</code>
-<code>    jarsigner -keystore appletstore -signedjar SignedGatherer.jar GLI.jar privateKey</code>
 When it prompts, enter the password you used above.
   - Move the created ''SignedGatherer.jar'' file from the ''gli'' directory into GS3's ''web/applet'' subdirectory.
@@ Line 208: / Line 207: @@
 MimeType=application/x-java-jnlp-file;
 </code>
-  - Launch the Java Control Panel by running ''jre/bin/javacpl.exe'' on Windows or ''jre/bin/ControlPanel'' on Linux. (GS3 binaries now include a JRE in the ''packages'' folder if you want to use the bundled JRE.) In the Java Control Panel, go to the ''Security'' tab, set Security level to ''High'' if not already set. Click ''Edit Site List'', and then press ''Add'' to add the <i>host:port</i> that the GS3 will run on. Remember, to be accessible to the outside world, the host can't be "localhost" but would be the hostname of your machine or public IP.
+  - Launch the Java Control Panel by running ''jre/bin/javacpl.exe'' on Windows or ''jre/bin/ControlPanel'' on Linux. (GS3 binaries now include a JRE in the ''packages'' folder if you want to use the bundled JRE.) In the Java Control Panel, go to the ''Security'' tab, set Security level to ''High'' if not already set. Click ''Edit Site List'', and then press ''Add'' to add the //host:port// that the GS3 will run on. Remember, to be accessible to the outside world, the host can't be "localhost", but would be the hostname of your machine or public IP.
   - Once the GS3 code is compiled up, start up the GS3 web server and visit your DL library home page, ''http://[hostname]:8383/greenstone3/library''.
   - Since you have set up the JNLP file association in a previous step, you can now click on the "The Librarian Interface" link and your browser should offer to save or launch a file called ''GLIapplet.jnlp''. If the browser is able to successfully launch it, Java Web Start will be used to run the GLI application indicated by the JNLP file. If launching through the browser is not possible, then choose to save the JNLP file. It will download the file to a temporary user area (like C:\Users\<user>\AppData\Local\Temp on windows). And then you can rightclick on the downloaded GLIappWebStart.jnlp file, to launch it with the Java Web Start program you already associated with this file type.
@@ Line 227: / Line 226: @@
 ==== Troubleshooting ====
+=== Firefox browser doesn't remember you being logged into greenstone ===
+If you're on firefox and you just logged in to to a running Greenstone 3 digital library (DL), but visiting subsequent pages in the DL shows you that it has forgotten you're logged in, then you're probably encountering a restriction that your firefox browser has.
+**NOTE:** We've encountered this problem on Firefox and only for http URLs that use the domain/machine host name for the tomcat.server property, whereas https URLs worked fine in remembering Greenstone logins, as did http URLs using localhost/127.0.0.1.
+To confirm that it only happens on firefox, try another browser first. For instance, Chrome. If your being logged in is being remembered on Chrome, then you've confirmed that the phenomenon is firefox-specific.
+Things to try:
+* Close all tabs in firefox and restart firefox in the usual way. Try logging in and visiting other pages to see if it remembers your login now.
+* If that made no difference, try launching a Private Window (Ctrl + Shift + P on firefox), visit your GS3 digital library and login again, then check whether it's being remembered across Greenstone pages now.
+* If that also made no difference then the most likely cause is Firefox plugins or extensions or addons, or maybe its hardware acceleration feature needs to be switched off. To find out if any of this is the case, quit firefox once more by first close all tabs in firefox and quit it. Then try re-launching Firefox in Safe Mode as explained at https://support.mozilla.org/en-US/questions/1213229
+> [[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode|Start Firefox in Safe Mode]] by holding down the <Shift> (Mac=Options) key, and then starting Firefox.
+> A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?
+(If that doesn't work on Linux, firefox can be launched in safe mode from a terminal by typing ''firefox -safe-mode''.)
+After relaunching Firefox in Safe Mode, test whether your login details are being remembered this time. If it works now, it could indeed be an addon/extension/plugin or the hardware acceleration feature. Follow the suggestions and instructions at https://support.mozilla.org/en-US/questions/1213229 and https://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration to narrow down which of these it is.
 === Mac Installer fails ===