XML-RPC Error (404)

Hello!

I know there are many posts on this topic, but as I am experiencing the above error on three separate occasions, I thought it best to open a new thread:

- When trying to save changed user properties in the Joomla backend (Joomla user manager)
- When trying to edit certain users in the jomsocial backend
- When attempting to use the random quiz question module
- When attempting to sync Moodle profiles through Joomdle.

Do you think these three are related?

Thanks!

EDIT: Just to complete the information: System check is passing, only Moodle to Joomla HTTP connectivity has an X. According to Joomdle documentation this can happen and should not impact performance.

We are running Joomla 2.5.9, Joomdle 0.91, Moodle 2.5 and JomSocial 2.8.4

Enable debugging in Moodle so you can get more info about the errors.

Hello Antonio,

I think we have narrowed down the cause of some of the problems.


- When attempting to sync Moodle profiles through Joomdle
- When trying to save changed user properties in the Joomla backend (Joomla user manager)

The first two yielded the following error message

XML-RPC Error (84677281): Error writing to database | DEBUG INFO: Data too long for column 'institution' at row 1 UPDATE mdl_user SET institution = ? WHERE id = ? [array ( 0 => 'Afghan-Horizon, Center for Nonproliferation and Terrorism Studies', 1 => '115', )] | ERRORCODE: dmlwriteexception

I know some field lengths cannot be changed in moodle at this time. Is there a way for Joomdle to truncate these field values at 40 characters?


- When attempting to use the random quiz question module
I was not able to reproduce the error today. However, the attached screenshot displays how the quiz question is shown. There are no other error messages visible.


- When trying to edit certain users in the jomsocial backend
I was not able to reproduce this today.

Well, you would need to modify the code to truncate the data.

If you are collecting this data in Joomla, you are using some application such as CB, jomsocial, etc. The logical place to truncate this information is to ensure that only the appropriate length is entered from the start and thus place validation checks on your data entry. This saves you hacking code and ensures data in matches data out.