Another XML-RPC Error (28260048) error:

XML-RPC Error (28260048): Invalid response value detected | DEBUG INFO: Only arrays accepted. The bad value is: '' | ERRORCODE: invalidresponse

What do I have?
Moodle 3.4+ installed tonight.
Joomdle 1.1.4 installed tonight.
PHP 7.2.0
Joomla up to date version

When I click on enrol into course in this page (yes, I'm logged in as superuser).
www.dunamisinstitute.org/video-courses/d...n-the-spirit-s-power
i get this error:
XML-RPC Error (28260048): Invalid response value detected | DEBUG INFO: Only arrays accepted. The bad value is: '' | ERRORCODE: invalidresponse

Joomdle System check is all green.

If I try to log out ( www.dunamisinstitute.org/index.php?optio...enulogout&Itemid=644 )
I get this error:
0
Error: 0

Call to a member function get() on null

I'm not sure the logout error is related, but sometimes when I try to enrol i get that xmlr error.

Thanks for attending to this when you can.

Hi Chris.

Is this a new installation, or was it working before Moodle upgrade?

I have tested at your site, and could replicate the enrol problem, although I don't know yet what's happening. I will try doing some debugging and get back to you as soon as possible.

As for logout error: this is not related to Joomdle, as error still happens when you disable joomdlehooks plugin.

It wasn't working before moodle upgrade (I was at 3.1+). As users started reporting course not found errors and xml errors, I started looking into it and started with the upgrade process of moodle and joomdle plugins. The system check was reporting all green beforehand. I can't remember the text that appeared on "course not found" page when the enroll button was hit.

My first step was to update moodle and joomdle to most recent versions. I can't remember what joomdle version I was on. Sorry.

Thanks for the info.

I could not replicate the problem in my test installation.
I did some debugging at your site, and it seems I have found a way to make it work, and it also works in my site, so it all seems ok.
Please test and let me know if you still notice any issues.

Hmmmmm. . .

I was able to enroll in to the course successfully. Was there a setting I had somewhere that I didn't know about? You mentioned debugging at my site so my curiosity is high .

Thanks for whatever you did that accomplished. the goal.

Hi. Thanks for the feedback.

No setting, I did a code modification, that will also be included in next release.
The change involves using the root URI to call enrol task. Right now it was calling it on the current page, and it seems that could cause problems in setups like yours.

Thanks.
I can't tell if this is a new error, or a new setting in moodle I have to adjust.

When I am logged in and go my course list and choose it:
www.dunamisinstitute.org/my-courses/deta...n-the-spirit-s-power
The course image is there.
When I "go to course", the course image is no longer there.
www.dunamisinstitute.org/component/joomdle/course/32?Itemid=

that is true of all my courses now. . . I don't know if that is a moodle change, joomla change, or joomdle variable

You've are such a great help and thanks for supporting your own plugin.

Interestingly, when I went to login to moodle, this screen popped up instantlly after login:
www.dunamisinstitute.org/courses//auth/j...amisVideoCourse2.jpg

that's the image. . I see an extra // before auth.

Hi.

I don't think I am seeing the same issue when I try to replicate it at your site with my user.
Trying both ways I can see the image just fine.
As for the double slash: I don't understand exactly what you are doing, and I don't know why it is showing.

Are you using a normal non-admin user for your testing?
If you can replicate the issues with that user, you can email me the credentials to see if I get the same results.

Thanksgiving holiday here in the US, so no work for me most of this week

This is the behavior in my super-user account.

I logged in with my test non-super user account, and the graphic appears correctly.

This narrrows down to a super-user account type.

With admins things can get weird, and Joomdle does not really recommend setting admin users as Joomdle users, as this can cause access problems if there is any problem with Joomdle.