I've just started to use mediawiki.el to edit out internal wiki page. I've set it up as described. I connect to the wiki, Edit the file I want. When I want to submit my edits I hit C-x C-s, it prompts me for a summary, but after it I get the following error:
let*: The server encountered an error: (unknown_action) Unrecognized value for parameter 'action': edit
Any idea what am I doing wrong? Thank you very much!
Per this thread, the error most likely means that you either have an ancient version of MediaWiki (not likely), or that you have the API disabled.
To enable editing though the API, you need to set $wgEnableAPI and $wgEnableWriteAPI to true in LocalSettings.php of your wiki.
Related
In one of the courses, an error occurs when trying to create a backup copy of the test: "Missing required parameter (id)".
The test was previously ported from moodle 1.9.9 to moodle version 3.11.6 and works great.
Why then it is not copied? What parameter is missing?
I turned on debug mode and error output, but I didn't see anything on the page.
I looked in the logs, but found nothing there (little experience).
I cleared all site caches through the Administration section.
Is the debug level set to developer?
I can't see "Missing required parameter" as a language string in the core moodle code - is that the exact string?
If it isn't the exact string, can you update the question with the exact string.
If it is the exact string, then it might be a contributed / custom plugin
When you backup the course, in the backup settings, try selecting 1 activity/module at a time until the error occurs. Then you know which activity is displaying the error - can you update the question with the activity type/plugin name.
Let's say I have some website with the name website.eu. When I deploy it and try to get access to a page online like this website.eu/about I catch the error:
"404 The page you're looking for could not be found. The resource that you are attempting to access does not exist or you don't have the necessary permissions to view it"
When I click on the link that brings me a website.eu/about it works well, but trying to type that URL in the input field it fails.
Everything works fine locally.
The project is developed using Vue3.
The project is no GitLab.
If someone helps I would appreciate it.
Hard to tell without seeing the code, but my guess is your router setup uses the web history mode, which relies on the server to have certain settings applied.
I believe switching to hash mode (while adding # to the routes) will work.
Alternatively, you can update your server to support redirects to have the html mode work.
example server configurations
I have a custom backend module.
If an editor now has several browser windows showing this backend module, the following error message is always displayed:
#1417988921: The CSRF protection is necessary or invalid (More information)
TYPO3\CMS\Core\Exception thrown in file
vendor/typo3/cms/typo3/sysext/backend/Classes/Http/BackendModuleRequestHandler.php in line 82.
Can anyone help me?
...just a shooting from the hip:
Check php.ini and increase the values for max_input_vars und upload_max_filesize. Helped me out of a similar trouble.
(I assume you have checked https://forge.typo3.org/issues/66704 before)
I have installed the wordpress seo (yoast) plugin on my wordpress site, but if i am activating the plugin it breaks the site. I can access the backend (dashboard) but nothing is visible on front end. It's showing an error message
"The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
This problem can sometimes be caused by disabling or refusing to accept cookies."
I have already gone through the plugin support but couldn't find anything related to this.
Please provide any solution to resolve the issue.
Thanks!
There might many causes of breaking site after activating plugin. In your case, may be the reason is memory limit. Please try to add support for more limit. You can use WP_MAX_MEMORY_LIMIT to increase it.
You can debug the site using WP_DEBUG in wp-config.php, set it true you will get all the warnings and fatal errors to check the main cause of break.
I Request you to enable debug the site using WP_DEBUG in wp-config.php, set it true you will get all the warnings and fatal errors to check the main cause of break. as mentioned above by #Trimantra Software Solutic.
Go to wp-config.php and find define('WP_DEBUG', false); replace with below
define('WP_DEBUG', true);
After then you will find the error !
I've created a fresh install of Moodle 2.5. I installed successfully, I thought. I have not customized the theme, so it can NOT be theme-based.
TinyMCE's file picker is not loading...whether trying to upload a file or creating/editing a course under the Course summary files section...all I get is the "Loader" star. I did some research and found no solutions that worked. Quite a few said "custom themes," but I have no custom themes yet. Now, in checking the console, I got this:
- Uncaught SyntaxError: Unexpected Identifier /lib/editor/tinymce/tinymce/3.5.8/tiny_mce.js:2
- Uncaught ReferenceError: tinymce is not defined module.js:1
- Uncaught ReferenceError: tinyMCE is not defined yui_combo.php?moodle/1374671241/editor_tinymce/collapse/collapse-min.js:1
Digging further, I found the error on tiny_mce.js with the "uncaught syntax error" is around this area (I beautified the JavaScript for better readability and it ended up on line 3344):
pi: function(h, i) {
if (i) {
c.push("")
} else {
c.push("")
}
if (a) {
c.push("\n")
}
}
I also have no clue why the page is not seeing TinyMCE as defined.
In my browsing of multiple sites, one person mentioned being able to open the file picker in Moodle 2.5 when logged in as a regular non-Moodle user. They, too, have no answer to the problem, but I tried that and the file picker did, indeed, open.
Update
I've found it's not quite just the file picker. This whole thing is tying in to TinyMCE not loading properly...with the editing toolbar capability (whether collapsed or not.) It acts as if it's a simple text editor.
I fought with it and ended up causing more problems than solutions, so I uninstalled everything, and started from scratch. I have no plugin add-ons, no fancy themes (it's the basic one it installs with), and no customization, and it's still buggy.
The console continues to say:
- Uncaught SyntaxError: Unexpected Identifier /lib/editor/tinymce/tinymce/3.5.8/tiny_mce.js:2
- Uncaught ReferenceError: tinymce is not defined module.js:1
- Uncaught ReferenceError: tinyMCE is not defined yui_combo.php?
And it pauses the debugger on practically every page with this. It's telling me that there's a problem with how TinyMCE is called in.
I've submitted a bug report, but haven't gotten the answer yet. What I'm hoping for is someone else to have had the same problem and come up with the solution, remembering there is no theme customization, no add-ons...so they can't be at fault.
As a matter of fact I also banged to this issue after upgrading to Moodle 2.5.1+, and after digging it for hours came up with a solution that made things work smooth again, I have disabled Cache JavaScript from:
Home / ► Site administration / ► Appearance / ► AJAX and Javascript
After saving the settings the file picker started working as normal. I am not sure how bad this will affect overall moodle performance and how bad it will increase the load on server and website loading overhead, but at the moment that was the only solution that I came up with.
Hope this will help...
version 2.5.1+
The FilePicker doesn't load when editing is turned on.
If you have this issue where the FilePicker hangs while loading, click on the following:
Administration | Course Administration | Turn editing off
Then refresh the page with the FilePicker that you need to use.
I'm putting this as an answer, because I received one, and I want everyone who ends up with a similar problem to know the way to solve it.
The problem was with the admin user profile settings. The Moodle team responded, and told me what to do.
It's as simple as:
Change the admin's user profile and set not to use html editor by default.
Purge all caches both in moodle and in your browser.
Make sure that in "Site administration ► Development ► Debugging" you have "debug messages = developers" and "display debug = yes"
Thanks!