$wgSVGConverterPath = "/usr/bin" $wgSVGConverterPath = "/usr/local/bin" If you find something like, where it appears 1,5x instead of 1.5x, the problem is caused by task T181987, and you should add this to LocalSettings.php: If image thumbnails simply don't appear, and there's no error visible on those pages, look at the HTML source of the page and search for " srcset". This might happen due to wrong values of global variables as explained in: This section lists problems and solutions relating to thumbnails not rendering or displaying. See report: Topic:Rz2zo0m88rrxqrfn and Thread:Project:Support_desk/MediaWiki_don't_work_with_PCRE_8.34_(2) Image Thumbnails not working and/or appearing The problem is solved in all currently supported versions of MediaWiki (see task T60640). You need to update MediaWiki to a supported version. Non-digit at offset 4 in /var/www/wiki/htdocs/includes/MagicWord.php PHP Warning: preg_replace(): Compilation failed: group name must start with a MediaWiki Errors All pages have no content, but when editing a page the wiki text is there You can disable JavaScript on your browser, or set $wgUseSiteJs and $wgAllowUserJs to false to disable those scripts until you fix the broken scripts. document.write is legacy code that causes the entire page to become blank if it's used outside of the page HTML, and it may be present on the wiki's JavaScript pages. If the network tab returns a HTTP 200 status, and the transfer is of several kilobytes, it's very likely this is the problem. You can check if that's the case if you open your browser console (hit F12) and reload the page. If you can see the page contents briefly, and suddenly the entire page goes blank, most likely the problem is caused by the presence of a document.write JavaScript instruction in one of the scripts of the wiki. If it's the email server, check if you can connect to it from the server running MediaWiki, for example, running the Telnet client to the server and port configured on $wgSMTP and seeing if it can connect. This may be the database server, or if it happens doing a specific action, the mail server (if you have configured email settings). If the page just hangs loading during some time (like 30 seconds) doing a specific action, and then it results in a blank page or HTTP 500 error, the problem is a timeout connecting to some server. This change does not require you to restart apache. 20M may not be enough if you are running version 1.15.1. Scan for the line containing the memory_limit setting and increase as needed. The memory limit may also have been set in your LocalSettings.php file. Make sure to restart your webserver after you have changed this value. For example to raise it to 32 MB replace the existing text with " memory_limit = 32M". To modify this setting edit /etc/php.ini and increase the "memory_limit" setting. Please check your PHP and/or Apache error logs. A likely cause is the memory limit in default php installations (usually 8 MB). Many people report blank pages in recent versions after submitting articles to their new wiki. The fix is to update the fault_socket entry in the php.ini file. If LocalSettings.php is set to the correct MySQL socket but php.ini is not, it may result in a blank screen with no error output from the webserver or php. It may be necessary to refresh the cache and restart the webserver afterwards. If so, simply copy the missing files from the package into your MediaWiki directory. Check the original installation package at MediaWiki (make sure to consult the appropriate version) to see if this is the case. when the media folder in your /includes folder is no longer present, you may receive the message that a required imaging process "failed to open stream"). Certain files may be reported as missing (e.g.You are *required* to use the date.timezone setting or the date_default_timezone_set() function." Check if date.timezone = is set correctly (or set at all) in PHP.ini. "Warning It is not safe to rely on the system's timezone settings.In some cases, PHP errors might also be recorded in the web server error log. You can also set a value for error_log in PHP.ini and read the PHP error log to find out what's going on. Error_reporting ( E_ALL ) ini_set ( 'display_errors', 1 )
0 kommentar(er)
