Upgrade to 3.11, fatal errors and more

Upgrade to 3.11, fatal errors and more

by Melissa Prior -
Number of replies: 8
Updated from 3.9 to 3.11.
Reverted to PHP version 7.4 as 8.0 caused fatal errors.
No longer able to use Joomla (via joomdle) as IDP.
Similar issues with Mini Orange.
Was able to use External database to authenticate accounts but this does not add them to Moodle, can not enrol in courses and does not allow for SSO.

Using validator.W3.org these results are returned:

  1. Error: Start tag seen without seeing a doctype first. Expected <!DOCTYPE html>.

    From line 1, column 1; to line 1, column 68

    <script src='../auth/mo_saml/includes/js/jquery.min.js'></scri

  2. Error: Stray doctype.

    From line 5, column 13; to line 5, column 27

    <!DOCTYPE html>↩↩<htm

  3. Error: Stray start tag html.

    From line 7, column 1; to line 7, column 41

    PE html>↩↩<html dir="ltr" lang="en" xml:lang="en">↩<head

  4. Fatal Error: Cannot recover after last error. Any further errors will be ignored.

    From line 7, column 1; to line 7, column 41

    PE html>↩↩<html dir="ltr" lang="en" xml:lang="en">↩<head


Please help.
Average of ratings: -
In reply to Melissa Prior

Re: Upgrade to 3.11, fatal errors and more

by Ken Task -
Picture of Particularly helpful Moodlers
Don't run jmoodle anymore so consider this response, some legwork ..

Moodle 3.11
General support ended: 14 November 2022
Security support ends: 11 December 2023

jmoodle plugin for moodle:

jmoodle

Hope you were trying this on a duplicate/dev system ...
Also hope you took a site backup - both moodle and joomla - prior to.

'SoS', Ken

Average of ratings: Useful (1)
In reply to Ken Task

Re: Upgrade to 3.11, fatal errors and more

by Melissa Prior -
Progress has been made!
Those errors were fixed after speaking with our hosting provider.

Updated successfully (hopefully) to PHP 8.0.

Going to test an update to Moodle 4.1.3 on a development site on the same server.

Still unable desperately trying to find a way to connect the two overnight.


Average of ratings: -
In reply to Melissa Prior

Re: Upgrade to 3.11, fatal errors and more

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
Hi

You wrote:
> Updated from 3.9 to 3.11.
> Reverted to PHP version 7.4 as 8.0 caused fatal errors.

Understand. PHP 7.4 is convenient because both version run on it. The complete answer is though: Moodle 3.9 is compatible with PHP 7.2-7.4. Moodle 3.11 is compatible with PHP 7.3 and 7.4 and since 3.11.8 also PHP 8.0 compatible. See http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases

> No longer able to use Joomla (via joomdle) as IDP.

Shouldn't be. The latest Joomdle, 2.1.0, is good for 3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 4.0 and 4.1. https://moodle.org/plugins/auth_joomdle/versions.

Get a full trace from Debugging set to maximum and post it to the relevant forum. (I don't know, which one. I don't use Joomdle.)

No idea about the other topics: the Mini Orange, the external authentication and the W3 validator results.
Average of ratings: Useful (1)
In reply to Visvanath Ratnaweera

Re: Upgrade to 3.11, fatal errors and more

by Melissa Prior -
Made the switch to 8.0 and resolved errors (with help of the hosting company) so sites are functioning.

It feels like a permissions thing in Moodle, but I am not sure where to look. Any suggestions of things to check within Moodle. I already made sure the token issuer has authorization for those protocols.

Results of the server check:
Joomla to Moodle HTTP connectivity passes
Moodle to Joomla HTTP connectivity Moodle cannot connect to Joomla
Joomdle Web Services Received empty response from Moodle
Average of ratings: -
In reply to Melissa Prior

Re: Upgrade to 3.11, fatal errors and more

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
Hi

You wrote:
> Made the switch to 8.0 and resolved errors (with help of the hosting company) so sites are functioning.

You mean you did the upgrade 3.9 > 3.11 staying with PHP 7.4, then upgraded PHP to 8.0?

> It feels like a permissions thing in Moodle, but I am not sure where to look.

What "feels like a permissions thing in Moodle"? Didn't you say that the "sites are functioning"?

> Any suggestions of things to check within Moodle.

The issues are not clear. And do you know that they are within Moodle, not in the Joomla/Joomdle connection nor in the hosting environment?

> I already made sure the token issuer has authorization for those protocols.
> > Results of the server check:
> Joomla to Moodle HTTP connectivity passes
> Moodle to Joomla HTTP connectivity Moodle cannot connect to Joomla
> Web Services Received empty response from Moodle

You must be talking of something Joomla/Joomdle. Never been there, sorry. Did you see Leon's reply?

As a general note, if you could copy and paste errors or upload screen-shots, rather than explaining, the reader might understand better.
Average of ratings: -
In reply to Melissa Prior

Re: Upgrade to 3.11, fatal errors and more

by Leon Stringer -
Picture of Core developers Picture of Particularly helpful Moodlers

The miniOrange plugin – auth_mo_saml – appears to be responsible for the four validator errors. This plugin was released for Moodle 2.7 and hasn't been updated since 2017. A listing in Moodle plugins was applied for but not granted due to concerns with the quality (CONTRIB-6867). If you need SAML authentication I'd recommended migrating to a different plugin, auth_saml2 is probably best, there's also auth_saml and auth_saml2sso.

For now simply disabling the miniOrange SAML 2.0 SSO plugin should resolve the validator errors.

Disabling this may fix the Joomdle problems too. If you're still having problems with that please tell us more detail about what happens when you try to use this. If there are error messages enable debugging to get further details for these.

Average of ratings: Useful (2)
In reply to Leon Stringer

Re: Upgrade to 3.11, fatal errors and more

by Melissa Prior -
Thanks Leon.
Removed miniOrange from both Moodle and Joomla. 
Looked into the options you suggested, but Joomla leans really heavily on miniOrange and I haven't seen a solution that allows Joomla to be the IDP. 

No errors in debugging, reached out to Joomdle for additional support. 

Average of ratings: -
In reply to Melissa Prior

Ri: Re: Upgrade to 3.11, fatal errors and more

by Sergio Rabellino -
Picture of Particularly helpful Moodlers Picture of Plugin developers
You should consider using tools like Keycloak (https://www.keycloak.org) to be inserted on top of Joomla and Moodle and connecting them to it by using OIDC or SAML (moodle has these client protocols embedded in core and you can use miniorange in joomla). No dependencies between the two webapp, a new "node" which manage the authentication/authorization.

Average of ratings: Useful (2)