Difference between revisions of "EPrints 3.4.6"

From EPrints Documentation
Jump to: navigation, search
(Release Notes: Added known issue about generate_apacheconf not working without archive cfg/static/javascript/auto/ directory)
m (Running generate_apacheconf with an archive without a cfg/static/javascript/auto/ directory)
Line 119: Line 119:
 
== Known Issues ==
 
== Known Issues ==
 
=== Running generate_apacheconf with an archive without a cfg/static/javascript/auto/ directory ===
 
=== Running generate_apacheconf with an archive without a cfg/static/javascript/auto/ directory ===
If you are upgrading an EPrints repository and your archive(s) do not have a <code>cfg/static/javascript/auto/</code> directory then <code>bin/generate_apacheconf</code> will fail.  This is because 3.4.6 [https://github.com/eprints/eprints3.4/issues/369 introduces] code that makes sure that the maximum upload limit is configured to be the same in the Apache configuration and in EPrints' JavaScript, which prevents you from trying to upload files larger than certain size.  This is useful because if you just updated the JavaScript, EPrints would allow the upload to start but would then fail when the Apache limit was reached.  So not only would you not be able to upload the file but you would waste a lot of time before and possibly not understand why the upload failed.
+
If you are upgrading an EPrints repository and your archive(s) do not have a <code>cfg/static/javascript/auto/</code> directory then <code>bin/generate_apacheconf</code> will fail.  This is because 3.4.6 [https://github.com/eprints/eprints3.4/issues/369 introduces] code that makes sure that the maximum upload limit is configured to be the same in the Apache configuration and in EPrints' JavaScript, which prevents you from trying to upload files larger than a certain size.  This is useful because if you just updated the JavaScript, EPrints would allow the upload to start but would then fail when the Apache limit was reached.  So not only would you not be able to upload the file but you would waste a load of time and possibly not understand why the upload failed.
  
To fix this issue for now, just make sure your archive (or archives) all have a <code>cfg/static/javascript/auto/</code> before running <code>bin/generate_apacheconf</code>.  Future versions of EPrints will automatically create this directory if it does not exist.
+
To fix this issue for this version of EPrints, just make sure your archive (or archives) all have a <code>cfg/static/javascript/auto/</code> before running <code>bin/generate_apacheconf</code>.  Future versions of EPrints will automatically create this directory if it does not already exist.
  
 
== Further Planned Features and Improvements ==
 
== Further Planned Features and Improvements ==

Revision as of 15:10, 29 August 2024

Release Notes

3.4 | 3.4.1 | 3.4.2 | 3.4.3 | 3.4.4 | 3.4.5 | 3.4.6


3.3 | 3.3.5 | 3.3.6 | 3.3.7 | 3.3.8 | 3.3.9 | 3.3.10 | 3.3.11 | 3.3.13 | 3.3.14 | 3.3.15 | 3.3.16


3.2.0 | 3.2.1 | 3.2.2 | 3.2.3 | 3.2.4 | 3.2.5 | 3.2.6 | 3.2.7 | 3.2.8 | 3.2.9


3.1.0

This page contains information about the provisional EPrints v3.4.6 tag and release on GitHub.

Release Notes

EPrints 3.4.6 is now available on GitHub.

  • Zero codename: Creme Brulee Cryoseism
  • Publications flavour codename: Affogato Snowmelt

New Dependencies

Check earlier dependencies for EPrints 3.4.5 and before.

Changes Since 3.4.5

New Functionality

Security and Privacy Improvements

General Improvements

Bug Fixes

Known Issues

Running generate_apacheconf with an archive without a cfg/static/javascript/auto/ directory

If you are upgrading an EPrints repository and your archive(s) do not have a cfg/static/javascript/auto/ directory then bin/generate_apacheconf will fail. This is because 3.4.6 introduces code that makes sure that the maximum upload limit is configured to be the same in the Apache configuration and in EPrints' JavaScript, which prevents you from trying to upload files larger than a certain size. This is useful because if you just updated the JavaScript, EPrints would allow the upload to start but would then fail when the Apache limit was reached. So not only would you not be able to upload the file but you would waste a load of time and possibly not understand why the upload failed.

To fix this issue for this version of EPrints, just make sure your archive (or archives) all have a cfg/static/javascript/auto/ before running bin/generate_apacheconf. Future versions of EPrints will automatically create this directory if it does not already exist.

Further Planned Features and Improvements

See 3.4.7 milestone on GitHub for more details.