Quantcast
Channel: Installing and upgrading help
Viewing all 47143 articles
Browse latest View live

Profile dropdown not working after 3.10.4 upgrade

$
0
0
by Christe McMenomy.  

SERVER configuration: LINUX 5.10.27-gentoo PHP 7.4.19 DB MariaDB 10.5.9 

I upgraded my test system from Moodle Version 3.10.3 to 3.10.4 on this server, and it worked without issue.

Then I upgraded the production system. Not everything is working. I have purged all caches several times and have killed my browser and cleared its caches. Neither action has helped.

The website log lists no errors.

Issues:

1. Top line menu options (Course menu, alarms, messages, user dropdown menu) do  not work. The icons exist and display properly, but nothing happens when they are clicked, other than a blue box appears. Clicking on the username creates a link "https://SITE-URL/moodle/?redirect=0#" but no dropdown occurs.

2. As administrator logged into the home page, the navigation menu is not expanding dropdown for Site Pages, but works to expand Site administration in the Administration box. However, submenus under site administration do not work.

3. The Site Administration page lists all tabs, but clicking on a tab has no effect.  Using Search works to navigate to a particular page (i.e., purge cache), at which point the dropdown menu displays in the navigation bar.

4. Putting the system in full debug mode with html display turned produces no error messages when clicking on the user name and encountering the drop-down failure.

5.  We are using the Boost theme as default for desktop.  Changing to Classic did not solve the issue.  Changing back to Boost did not solve the issue.

6. Editor icons to edit text entry fields are not working (there are blank boxes).  Clicking on the boxes executes the code (e.g., I can toggle to HTML mode and back) but the icons are not showing up.

As far as I can tell, there are no differences in code between the test site (working) and the production site (broken), other than the configuration file. They are using different databases in the same database instance.

Any suggestions are welcome, as we are pretty much stuck right now.





Re: Profile dropdown not working after 3.10.4 upgrade

$
0
0
by Leon Stringer.  

If I've determined your Moodle site correctly then there are errors when the page loads in the browser console (for example: Web Console in Firefox), the first error being in the file first.js. Clicking on this file in the console shows it in the browser. It should contain just source code text but the file contains binary including lines like:

...Mac OS X ... ATTR ... com.apple.quarantine ... q/0081;60a00559;Chrome;91AD64F3-5B0E-4829-98E0-82BBD8D7A8A3

So maybe macOS has modified – and broken – some of the Moodle source code files?

If this is the case, try uploading the Moodle source code to the production site again, either from the working test site or from Moodle.org. Keep a copy of the current source code on the production site so you can copy config.php across.

Re: Profile dropdown not working after 3.10.4 upgrade

$
0
0
by Christe McMenomy.  

I thought I had checked for the odd characters, since I have seen Mac OS copies create problems before. Apparently I didn't check well enough, because when I completely rebuilt the moodle directory, including my additional modules, from raw Moodle zip files, everything worked.
Thank you very much for your help!

Re: Profile dropdown not working after 3.10.4 upgrade

$
0
0
by Christe McMenomy.  

Well...now I am really stuck.
I cannot log into either the test or the production Moodle instances as the administrator or as a normal user.

Everything appeared to be okay after we reloaded the moodle subdirectory with a clean copy of the code. I logged out and back in several times both as administrator and my teacher identity.

About two hours later, I started seeing invalid token errors in the webserver log. I can get to the Moodle login page, but when I enter my userid and password, the system simply hangs. Since I can no longer ​log in as the administrator, I can't review any log information as I normally would. In the last hour, I have tried numerous times to log in as my teacher account and as administrator, but I am not even generating error messages now. The login simply hangs: it never generates any error or any other response.

I do have access to the database through PHPmyAdmin. Any ideas what I might check now?

Re: Profile dropdown not working after 3.10.4 upgrade

$
0
0
by Christe McMenomy.  

Note: I am seeing a "TLS handshake" message, which appears to be new.
I have verified the configuration files,

The system is working correctly on my Mac.

Re: Profile dropdown not working after 3.10.4 upgrade

$
0
0
by Leon Stringer.  

Can you share these invalid token errors as they appear in the logs? If these errors contain any information that you don't want to share on the Internet then remove or obscure that part.

I don't think the TLS handshake message is part of a problem, you may be seeing this because your site is slow which is probably because you have Theme Designer Mode on.

The system is working correctly on my Mac – Which system does this refer to? Do you mean Moodle logins are working from a specific computer?

Are the users you're trying to log in as authenticated by Moodle – "manual" authentication in Moodle's terminology – as opposed to using an external service like LDAP or OAuth 2.

Re: Profile dropdown not working after 3.10.4 upgrade

$
0
0
by Ken Task.  

Pardon intrusion ...

your reporting TLS handshake errors

Might check config of SSL/certificates for your server with
SSLLabs.   While cert if valid via LetsEncrypt and a bot to renew, that doesn't config protocols and ciphers.

There are protocols which should no longer be supported.
Example: TLS 1.0 and 1.1 should be dropped, leaving only TLS 1.2 and 1.3.
TLS 1.3 should be first.
and ciphers should also be checked.

Various Browser clients have provided approximate deadlines for disabling TLS 1.0 and TLS 1.1 protocol:
Browser Name         Date
Microsoft IE and Edge         First half of 2020
Mozilla Firefox        March 2020
Safari/Webkit         March 2020
Google Chrome         January 2020

Also, you have other php applications at the same level as your moodle code in /moodle/ of your site and above.   Any using .htaccess rules above /moodle/?

'SoS', Ken

Re: 3.5.4 upgrade to 3.5.11+

$
0
0
by Ray Havlin.  

Thanks for this!

It fixed the same issue I had with Bluehost Shared environment.

(fatal: unable to create threaded lstat: Resource temporarily unavailable)

Ray

upgrading from 3.9 to 3.10 via git

$
0
0
by Alexander Urban.  

Hello,

i have a installation with moodle 3.9 and want to upgrade it. I could do this via cli script but i have some concerns:

- i am using git. currently my moodle installation is 3_9_stable branch (or similar)

- i installed a lot of plugins

What do I need to to, the instructions are unclear (to me!). I am not sure how to upgrade. To me there are some possibilities:

- checkout the 3_10_stable branch

- run the upgrade script in /admin/cli

What are the recommendations?

Re: upgrading from 3.9 to 3.10 via git

Re: upgrading from 3.9 to 3.10 via git

$
0
0
by Alexander Urban.  

Yes, but I just want to be sure. If I checkout another branch I can just run the upgradescript? Until now i just stayed with the same branch where i just had to pull the latest version.

So I should do:
a backup (of course!),
enable maintenance mode,
create a new local branch that tracks 3_10_stable and checkout this very branch
and then i can run the upgrade script?

I am fairly new to administrating moodle, usually I am a developer. I am familiar with git and linux but not when it comes to upgrading web software. Sorry if my question is ridiculous to a experienced admin, i just want to make sure i get things right smile

Re: upgrading from 3.9 to 3.10 via git

$
0
0
by Visvanath Ratnaweera.  

I understand. Here are more details:

> a backup (of course!),
As described in https://docs.moodle.org/39/en/Site_backup.

> enable maintenance mode,
Correct.

> create a new local branch that tracks 3_10_stable and checkout this very branch
> and then i can run the upgrade script?

$ git branch --track MOODLE_310_STABLE origin/MOODLE_310_STABLE
$ git checkout MOODLE_310_STABLE

Further:
- Check the suitabilitiy of your server with the https://docs.moodle.org/39/en/Environment. Watch the Moodle version drop-down box at the top.

- Additional plug-ins are more involved. An incompatible additional plug-in can hold up the upgrade. Go through Moodle plug-in database and be certain that all are supported in 3.10.

- If all the above sound too risky, you can do a trial upgrade in a staging server, could be even your local PC/laptop. Ref. https://docs.moodle.org/39/en/Moodle_migration.

Bigbluebuttonbn broke after updating to 3.11

$
0
0
by Igor Neumann.  

Hello all,

We are facing a problem of the courses being blank after installing the bigbluebuttonBN with the v3.11
Could anyone manage to make them work together?

Best Regards,

Igor

Re: Profile dropdown not working after 3.10.4 upgrade

$
0
0
by Christe McMenomy.  

You were right about the system slowing down. I had set theme designer on when I was trying to debug the failure of icons for text field editing to display. (It didn't help, since that issue was bad Mac upload end-of-line characters, but I forgot to turn it off). However, I apparently managed to work during an assault on the server, which overloaded the database. The token errors where caused by queries timing out; a few minutes after I sent the message, the Moodle started reporting that the database was either overloaded or down. About two hours later, everything cleared out without any other intervention, and now it all works.

So: initial issue caused by bad Mac upload; fixed by using the Moodle site zip file and manually updating all modules.
Secondary issue (some login failures) was due to using the wrong config.php file specifying the wrong DB; that was fixed by putting the right one in place.
Third issue (DB failure) caused by overtaxing the DB; that fixed itself. I must say I'm impressed by mariadb's hardyhood.

Thank you for your help. We've had no problems since Sat night (our time)..so nearly 40 hours working. I'd say we're good.

Moodle Error - Site is being upgraded, please retry later. - Moodle 3.10

$
0
0
by Dave Emsley.  

Hi All,

I've installed Moodle 3.10 on a Siteground server but everytime I update a block, mod, theme, or any plugins from either the respository or via ftp the plugin installs but hangs at
https://SiteURL/admin/index.php?cache=0&confirmrelease=1&confirmplugincheck=1 displaying the following on screen:



The theme is a bespoke child theme of Boost but works properly on testing server.

If I then try to go to any other page it stops with Site is being upgraded, please try later.

Any clues gratefully accepted.

Cheers

Dave


Re: Moodle Error - Site is being upgraded, please retry later. - Moodle 3.10

Re: Course internal ID - Can it start from a specific number?

$
0
0
by Matt T.  

Ah, ok, I see the reasoning. I'm not aware of any way to manually override the course ID number aside from tricky database manipulation.

Wouldn't you provide the LTI provider with the full course URL and not just a course ID?

Have to admit I'm not very clued into LTI.

Getting plugin update page when login to the admin panel

$
0
0
by Rageesh PK.  

Hi,

I am new to Moodle. When I am login to the Moodle I am getting a page where I can see the list of plugins that needs attention. I don't know what to do next to be frank. Can anyone help me to solve this issue. Please find the attached image for your reference.

Re: Bigbluebuttonbn broke after updating to 3.11

$
0
0
by Leon Stringer.  

This looks like CONTRIB-8551.

It looks like this is fixed in the version on GitHub so you could update to that version. Or you could just update the file mod/bigbluebuttonbn/classes/completion/custom_completion.php from GitHub. Or you could edit that file adding the following before the '}' on the last line:

    /** 
     * Returns an array of all completion rules, in the order they should be displayed to users.
     *
     * @return array
     */
    public function get_sort_order(): array {
        return [
            'completionengagementchats',
            'completionengagementtalks',
            'completionattendance',
        ];
    }

Update to 3.11: Dashboard not working

$
0
0
by Matthias Giger.  

After an update to Moodle 3.11 the course overview in the Dashboard is not loading and finally abolished with the following error message:

TypeError: Cannot create property 'stack' on string ''
    at https://yourdomain.com/moodle/lib/requirejs.php/1621274615/core/first.js:10:7678
    at tryCatch (https://yourdomain.com/moodle/lib/javascript.php/1621274615/lib/babel-polyfill/polyfill.min.js:1:93250)
    at Generator.invoke [as _invoke] (https://yourdomain.com/moodle/lib/javascript.php/1621274615/lib/babel-polyfill/polyfill.min.js:1:93024)
    at Generator.t.<computed> [as next] (https://yourdomain.com/moodle/lib/javascript.php/1621274615/lib/babel-polyfill/polyfill.min.js:1:93782)
    at o (https://yourdomain.com/moodle/lib/requirejs.php/1621274615/core/first.js:10:2166)
    at f (https://yourdomain.com/moodle/lib/requirejs.php/1621274615/core/first.js:10:2373)
    at https://yourdomain.com/moodle/lib/requirejs.php/1621274615/core/first.js:10:2432
    at new Promise (<anonymous>)
    at https://yourdomain.com/moodle/lib/requirejs.php/1621274615/core/first.js:10:2314
    at https://yourdomain.com/moodle/lib/requirejs.php/1621274615/core/first.js:10:8636

Course pages seem to load properly as long as Moodle is not busy trying to load the Dasboard (maybe also the calendar block).

I've already disabled all active filters.

I suspect a plugin might cause these problems because in a parallel installation on the same server with less plugins the update worked.

Has anybody run into the same problem?

All additional hints are appreciated.

Viewing all 47143 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>