Bobcares

Moodle JSON error – How we sort it out?

by | Oct 31, 2019

Have you just got a Moodle JSON error while trying to upload files?

Usually, this invalid JSON string indicates an upload error.

This can occur due to reasons like outdated browsers, larger file size, improper file format, etc.

At Bobcares, we often get requests to fix Moodle errors, as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix this JSON error.

 

How we debug JSON error in Moodle?

Moodle is one of the popular Learning Management Systems. This helps in managing courses and support learning.

It has features for easy upload and download of study materials. Also, it supports many file formats.

Fortunately, Moodle has a debug feature in its admin panel. So, whenever a Moodle error pops up, our Support Engineers turn the debug option ON.

Firstly, we login as an admin. Then navigate as, Administration >> Site administration >> Development >> Debugging. Also, the drop-down list shows various options regarding the Debug messages.

So, debugging gives a more clear picture of the error. After knowing this fixing the error is relatively easy.

 

Causes and fixes for the Moodle JSON error?

Moodle shows JSON error due to outdated browsers, file upload errors, etc. The typical error message when a user tries to upload a file in moodle appear as,

Moodle json error while uploading file.

Let’s have a deeper look at each reason.

 

1. Failed file upload in Moodle

In many situations, a failed file upload shows JSON error. Usually, this happens when Moodle doesn’t support that particular file format or improper file name.

If the error is with the file format, then we can add it in admin settings. For this our Support Engineers navigate as Site administration >> Server >> File types. Here we add a new file type and save the settings.

Similarly, special characters in the file name can result in a failed upload. Because Moodle fails to identify these characters. So, we check the file name and ask the user to change it if needed.

 

2. Server-side restrictions

Sometimes server settings can also restrict file upload. So, we check the server logs. If this is showing errors on any server settings, we try disabling it. For instance, mod_security may restrict file upload.

Or else, if the file size is larger, we check the maximum file upload size in the server. Later, we increase it if needed. We check all the settings that restrict file upload in the server, like PHP settings. This includes post_max size, upload_max_filesize, etc.

 

3. An outdated browser version

Moodle keeps on updating the software to include new features. As we access Moodle mostly via a browser, it’s important to have an updated browser.

Outdated browsers cannot identify some file formats. This can lead Moodle users to end up with the invalid JSON string error. So our Support Engineers always recommend customers to update their browser versions.

Similarly, cookies and temporary data in the browser can lead to this error. Hence, we ask customers to clear cookies and browsing data. Thereafter reloading the page may fix the error.

 

[Still having trouble in fixing Moodle errors? – We’ll help you.]

 

Conclusion

In short, Moodle JSON error occurs due to file upload errors, outdated browsers, etc. Today, we saw how our Support Engineers fix this error for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF