Custom Query (424 matches)
Results (88 - 90 of 424)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#607 | fixed | finish oran skin | ||
Description |
Need to finish the oran skin that make it the default - get rid of the old default skin.
lots of things to be done for this, including but not necessarily limited to:
|
|||
#625 | fixed | Local Library Apache Web Server for windows | ||
Description |
There was already the server.exe local library server on Windows. But to bring the Windows version of GS2 to the same state as the Linux/Mac versions, there is now an Apache web server included in the GS2 Windows. To compile, use makegs2.bat and choose compilation option 4. This essentially runs: nmake /f win32.mak APACHE_HTTPD=1 (see also the makegs2.bat note further below) The Apache web server is compiled up into the apache-httpd folder, just on Linux. The server can be run in two ways:
NOTE: The configure-admin command uses the now-precompiled getpw.exe executable in the bin\windows folder. It has been pre-compiled since adding compilation lines for it in the makefiles causes errors when Greenstone2 is compiled with Visual Studio Express (as is required when compiling with the DEBUG=1 flag on).
Files that were changed or newly added:
runtime-src\packages\apache-httpd\httpd-2.2.11-gs.tar.gz It is the same source code as for the *Linux* version, but with the Windows make files--from apache's windows source code release--added into it. This means that now the same source release tar file can be compiled up on Windows and Linux.
This code simulates the operation of the Linux apachectl binary. This is necessary because in general, on Windows, unless the Apache web server is installed as a windows service, starting and stopping the apache server requires a Ctrl-C command to be sent to the DOS console running the server. But we cannot ensure administration rights on every machine where GS2 will be installed, so we have to run the apache server (httpd) as a normal executable and hence have to stop it by sending it a Ctrl-C signal. The matter is complicated by the fact that there are two instances of httpd.exe launched each time the apache web server is run. Manually terminating one instance always replicates itself (re-spawning another httpd); while manually terminating the other instance of httpd.exe will terminate both instances. Therefore the solution is to simulate the termination behaviour when Ctrl-C is sent to the DOS console running the apache web server. This is done by sending the termination signal (Ctrl-C) via the stophttpd.exe C++ program to the Apache web server running in its own cmd console (launched via a START command). It works as follows:
The way to invoke the starthttpd.exe and stophttpd.exe can be seen in top-level gsicontrol.bat which invokes both to start and stop the apache web server, respectively. |
|||
#665 | fixed | datestamp in OAI records | ||
Description |
As reported by Mariana Pichinini, 18-12-09. I explain: where among the metadata reported is a DC.date tag, the OAI server treats this as a datestamp for the register. In common practice, this DC.date metadata means the publishing date for a resource, and since this is a internal resource, it usually is not formatted ISO 8601 compliant; in consequence, when OAI server try to read it, it reports a validation fail (I.e. with Open Archives or validators alike) I don't know the reason for the OAI server to take this DC.date as a datestamp; AFAIK, the most reliable date to take in such a way is the modified date for a source document, which you can take from the 'lastmodified' metadate, present in doc.xml. This is the date that's got everywhere there is no DC.date tag, and I think this is the only one tag that that date should be read from. When the collection do not implement Dublin Core in their metadata, there is no such trouble. So this mislead is not always raising... |