This page lists all official releases of Moodle, grouped by branch in reverse chronological order. From Moodle 2. The most recent long-term support release LTS version is Moodle 3.
These are the target dates for releases. These dates may vary slightly due to unforeseen circumstances. All releases are preceded by a one week warning. Upcoming release dates can be found in the Moodle development calendar Note, this is an iCAL link that will try to add the dates to your personal calendar. Kuma 1. Read on for more release information. By continuing to use our website, you agree to the use of cookies as described in our Cookie Policy Agree. Notable Improvements in 1.
Fixed charts in the GUI in multi-zone. CNI and VM improvements. Content loading…. Patch 1. Stay Connected. Diablo III Patch 1. English US. Contact Us. For details, see this document. Known Issues This list covers some of the known problems with Firefox 1. All Systems Prior to installing Firefox 1. If you install Firefox on a multi-user system in an area in which there is restricted access privileges, you must run Firefox as a user with access to that location upon installation so that all initial startup files are generated.
If this is not done, when a user without write access to the install location attempts to start Firefox, they will not have sufficient privileges to allow Firefox to generate the initial startup files it needs to.
When upgrading, all your Extensions and Themes will be disabled. This is not an issue, but it may appear to be one hence its listing here. For rationale, see "Extension and Themes" above. Software Update does not request proxy authentication and will fail if you are behind a proxy server.
Software Update will not work if Firefox is installed to a location that you do not have write access to, since Software Update needs to replace or create files in this location. To re-enable the Single Window Mode options at your own risk - there may be crashes , use the Configuration Console accessed by entering "about:config" in the Location bar and pressing Enter to set browser.
Windows On Windows systems, some users may experience a crash on exit of the browser after viewing a page that calls the Windows Media Player 9 plug-in. If you experience this, make sure you are using the newest version of the Java plug-in , greater than Java 1.
The browser should still function however. If you experience this, make sure you are using the newest version of the plug in.
We recommend you use Firefox 1. To break Firefox out of this loop, open a Terminal and type "killall firefox-bin" and press enter.
Install Firefox to a location you have write access to and try again. When installing on a multi- user limited access system, install it into a shared location as administrator, run it once and then all users should be able to access it.
Restart Firefox. Any toolbar customizations you have made or window placement will be lost Linux and Unix systems If Firefox is installed to a location with spaces in the path, Firefox may not be able to set itself as Default browser and may keep prompting at startup.
The work around is to install into a path without spaces. Users of Fedora Core 3 will need to download and install linc After installing the RPM, perform the following command in the directory you installed Firefox into you will need write permission : touch.
If you encounter a problem with a website that does not correctly display then it is usually a problem with Gecko, not Firefox itself. Such problems should be reported in the Core product not the Firefox product in Bugzilla. If you are technically minded, try and create a reduced test case and this will help get your bug more attention.
Troubleshooting Poorly designed or incompatible Extensions can cause problems with your browser, including make it crash, slow down page display, etc.
0コメント