Last modified: 2010-05-15 16:03:32 UTC
Warning: ignore_user_abort() has been disabled for security reasons in /home/gwendolau/public_html/includes/Article.php on line 1425 What do I have to make to modify an article without having message?
Want some extra input, but: throw a function_exists() at the two places it's called? Would be simple enough to just skip it if we can't use it anyway.
Or declare that MediaWiki doesn't work with random "hey let's disable this function for security" installations?
That would also work :)
What? I don't understand your explanation.
Niklas raises a good point. With some things, we can degrade nicely when people don't have particular features available to them. However, there's a point where we have to say "if you've got X function disabled, we can't really do much." Not sure if this is one of those instances or not.
I add only sentence: # Prevent new user registrations except by sysops $wgGroupPermissions['*']['createaccount'] = false; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['user']['edit'] = true; $wgGroupPermissions['sysop']['edit'] = true; I want that is that the users to record and that the administrator to add to him even the users.
You're receiving an error because your host has disabled the function "ignore_user_abort()". You may experience some bugs due to this decision; we can't help that. Most likely your wiki will basically work okay despite this and you can ignore the warning. I would suggest complaining to your host about the absurdity of disabling this function, however, just on principle. If the warning is showing up for you when you edit pages, then add this to the very top of LocalSettings.php (after "<?php"): ini_set( 'display_errors', '0' ); If that just gives you more errors, you could also try this (again, very top of LocalSettings): error_reporting( E_NONE ); If that *also* doesn't work, your host is completely and ridiculously broken and you should probably leave them ASAP. As far as MW goes: we could avoid the warning by checking whether the function is disabled, but it's not remotely sane for us to do that for every function out there. In this case, the warning doesn't hurt anything in this case -- it just makes the function a no-op, which is the best we could do here. It also does the service of informing users that their hosts are complete jerks. So, resolving INVALID.
Nothing, the modification is not saved.
