On my hosting with my MW (1.28.2) and SMW (2.5.3) a have:
/home/www/mediawiki-1.28.2
/home/www/w -> mediawiki-1.28.2 (link to mediawiki-1.28.2)
/home/www/.htaccess
Following https://www.mediawiki.org/wiki/Manual:Upgrading#Command_line I do:
Downloading mediawiki-1.29.0.tar.gz to /home/www/mediawiki-1.29.0.tar.gz
Unpack mediawiki-1.29.0.tar.gz to /home/www/mediawiki-1.29.0
Copy from /home/www/w to /home/www/mediawiki-1.29.0 files and folders: LocalSettings.php, images, some extensions
Then from command-line I do:
Change link /home/www/w from /home/www/mediawiki-1.28.2 to /home/www/mediawiki-1.29.0
cd /home/www/w
/opt/php/7.1/bin/php ~/bin/composer.phar require mediawiki/semantic-media-wiki "~2.5" --update-no-dev
/opt/php/7.1/bin/php ~/bin/composer.phar update
/opt/php/7.1/bin/php maintenance/update.php
And maintenance/update.php does nothing! At all!
And my site down to HTTP 500.
What is wrong and how can I debug maintenance/update.php ?
Okay, there is how I try to solve it:
I removed (temporary) .htaccess
I switched on error reporting in LocalSettings.php
When I went to my website/w/index.php I found that there were two(!) missing extensions: PdfHandler and SpamBlacklist. After removing them from LocalSettings.php all works fine.
That is the question: where were PdfHandler and SpamBlacklist gone???
https://www.mediawiki.org/wiki/Manual:How_to_debug
My guess (just a guess) is that there might be a problem with PHP7 as your default, since some MediaWiki extensions don't support it yet.
I think there was some problem with your dependencies try running "composer update" in the terminal and According to me it actually runs Localsettings.php file and aborts if it identifies any errors in the file so you have to check if there is any mistake in it and finally run php maintanence/update.php in mediawiki directory
Related
I'm attempting to install PHP Code Sniffer for PhpStorm, but have been unable to get it to work. I've been following the steps here: https://confluence.jetbrains.com/display/PhpStorm/PHP+Code+Sniffer+in+PhpStorm
I added PHP Code Sniffer as a Composer dependency, and it now appears in the project directory. I then went to the code sniffer settings page, where I entered the path to the PHPCS.bat file. When I click Validate, I get an error message saying "Can not run PHP Code Sniffer".
Have I missed a step or is there a log somewhere with more information on what is not working?
I solved the same problem by editing the phpcs.bat file and replacing the paths:
PHPBIN=#php_bin#
with
PHPBIN=path\to\php.exe
and
"%PHPBIN%" "#bin_dir#\phpcs" %*
with
"%PHPBIN%" "path\to\phpcs" %*
I had the same issue, I solve it adding the php path to the PATH environment variables on windows. Because when it runs the scripts needs to run php and if it not present on the global path of windows will fail.
I use Jenkins 1.656 and HTML publisher plugin 1.11.
I have successfully added HTML report section in the job:
Jenkins project configuration
Unfortunately when I click on HTML Reports, it shows only blank page.
The zip button works -- it downloads the report archive.
I will appreciate any help
The issue was with nginx server, it was
add_header X-Frame-Options DENY;
changed to
add_header X-Frame-Options SAMEORIGIN;
I faced the same issue but when I executed the command below in the script console it worked. Please try:
System.setProperty("hudson.model.DirectoryBrowserSupport.CSP"," ")
perhaps you have some JS in your report? Read this page: https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy and try to relax the security rules by changing JAVA_OPTS in tomcat.conf, then restart tomcat and clear broveser cache
I just saw your comment, try empty parameter:
-Dhudson.model.DirectoryBrowserSupport.CSP=
Try by adding one more Build step in configuration with below command:
npm install newman-reporter-html -g
For me above didn't work.
I publish report from IBM RPT (multiple .js files and index.html).
Jenki: reads index.html, first 2 .js files, but then it cracks on the others (searching them on the wrong path.
when downloaded in zip it works fine.
thx
Recently we have upgraded our mysql from 5.5.x to 5.6.x in an Ubuntu 12.04, also we have changed php5-mysql library with php5-mysqlnd(Which is recommended from MySql).
Since our change in library phpmyadmin stopped working and shows a blank page.
I have followed so many forum and advises from forum contributor but have not had success so far.
I also used ubuntu repository as suggested in this other topic at stackoverflow ppa:nijel which I believe has the modified phpmyadmin package and include the support of php5-mysqlnd, but still no success.
I also have enabled highest verbosity on the php.ini but still nor error or warning is generating in any log, using chrome developer tools it shows "500 Internal Server Error".
I am clueless now, if anyone can help me to determine what I may be missing obvious.
I just ran into a very similar error and I thought I would leave my solution here in case anyone finds this searching for my error. The difference was, that phpMyAdmin showed a blank page after a successful login.
The solution was, removing the "X-Frame-Options: Deny" header.
When setting up the webserver, I didn't remember that phpMyAdmin would rely on iFrames to serve its interface.
Check Mysql & Php error log files located at /var/log/mysql/error.log and /var/log/apache2/error.log respectively
Even after multiple uninstall, purge and reinstall of phpmyadmin I did not get a success.
Finally I used bruit-force approach and from another Linux server where phpmyadmin was running properly I copied all i.e. /usr/share/phpmyadmin, /etc/phpmyadmin and /var/lib/phpmyadmin folders and over write them in the problematic server.
Every thing works perfectly now.
Thanks for help Vibhas... I just thuoght to post just for someone's help.
In case someone (like I was) is using phpmyadmin via xampp on windows and has skype turned on - try turning skype off (or configure xampp to use another port).
I was facing a similar issue with phpmyadmin (phpmyadmin was returning a blank page). It was alright once I reinstalled phpmyadmin using:
apt-get install --reinstall phpmyadmin
If you are not root:
sudo apt-get install --reinstall phpmyadmin
When i changed this inside the config.inc.php:
$cfg['UploadDir'] = '/tmp';
$cfg['SaveDir'] = '/tmp';
to:
$cfg['UploadDir'] = '';
$cfg['SaveDir'] = '';
and reloaded the page then it worked directly!
This is a long shot, but it happened to me when I realised after a cPanel password reset I did not check the "Synchronize MySQL password" option.
This used to be defaulted as checked in previous cPanel versions.
To fix all I did was reset my cPanel password again and selected the "Synchronize MySQL password" checkbox and PhpMyAdmin was back.
Hope this helps others, and if its causing a big issue cPanel should select this option by default again.
I had a similar experience after installing mysql 5.5.60 and phpmyadmin 4.2.12 and what did the trick for me was changing folder ownership for /var/lib/php/session which was the solution in another case for getting php-scripts tu run in general. In my case user www-data is trying to execute related scripts, so I set folder permissions accordingly
chown -R www-data:www-data /var/lib/php5/
and the page appeared as expected.
A web search for [phpmyadmin blank page] shows many people are having this problem and there are almost as many different solutions proposed. So let me add one more after spending a day and finally having success:
When the blank page was displaying, I opened Developer Tools (Command-Option-i on Mac in Chrome or Brave). I immediately observed multiple instances of failing to load .js files from phpmyadmin/js/dist. Checking that directory I found that it was indeed empty.
I then went to https://www.phpmyadmin.net/ and downloaded the zip file into a different location. When I unzipped it, I found js/dist did in fact contain many .js files. I copied all of these files to my webserver's phpmyadmin/js/dist directory. And the problem was solved! I now have a working page.
I hope that helps some of you.
Perhaps I should add that I installed phpmyadmin using the Composer install method (% composer create-project phpmyadmin/phpmyadmin). I did it a second time in an offline directory and again the js/dist directory was empty. I don't know if that means I did something wrong or if that install method is broken.
I am trying to install supervisor on my Fedora 17, using this link as reference:
https://www.digitalocean.com/community/articles/how-to-install-and-manage-supervisor-on-ubuntu-and-debian-vps
It works fine except one trivial problem (I believe).
A simple configuration for our script, saved at /etc/supervisor/conf.d/long_script.conf, would look like so (...)
My problem is, that I have only files/directories:
/etc/supervisord/
/etc/supervisord.conf
I have tried to create conf.d directory under /etc/supervisord/. I have put my config file into /etc/supervisord/conf.d/ and /etc/supervisord/ and also /etc/sueprvisor/.
Despite my effort when issuing command:
supervisortctl reread
I receive:
No config updates to processes
Anyone has a clue what I might be doing wrong? Thanks in advance.
(I'm on Fedora 20) If you look at /etc/supervisord.conf at the bottom you see
[include]
files = supervisord.d/*.ini
So on Fedora your configuration files should end in .ini instead of .conf. I had this same problem and running supervisorctl reread after this detects stuff
There is no need to create a folder specifically for your configuration file, you can specify its path with the -c /path/to/your/file or --configuration=/path/to/your/file option.
Source: http://supervisord.org/running.html
I have installed Laravel and and I am playing around with it.
I am following the tutorial :-
http://geekanddummy.com/how-to-laravel-4-tutorial-part-3-using-external-libraries/
I need a new library and have added that in composer.json.
But when I run
php composer.phar update
I get the following message :-
Composer could not find a composer.json file in
What do I need to do to get this corrected..?
I'm the author of the tutorial you link to (hope our Laravel tutorial series is of some use, by the way). I can't quite tell from your answer whether you restored all the content of the original composer.json file when you created a new file of the same name...? You definitely shouldn't need to nuke the composer.json file and start again. As you probably know, that file contains all the Composer-based dependencies for your Laravel project, so you would of course lose significant functionality if you were to wipe it and leave anything out when you start again.
The error message looks to me like you're either in the wrong directory or it's a permissions problem with the composer.json file. It's too late to be certain now, but if you come across the problem again, try running:
chmod a+r composer.json
at the console/ssh shell before running composer update. This restores read permissions (for all users). You may also wish to check file ownership. (Both commands assume we're in a Unix/Linux system, so YMMV.)
Watch out also for instances where you're running a Composer command with the global parameter. This will cause an change that relates to wherever you've installed Composer, rather than the directory you're currently working in.
Note that you can also update using the --working-dir parameter, thus:
php composer.phar --working-dir=/path/to/laravel/project update
Hope this helps.
Rob
Deleting the existing composer.json after copying the content and then saving a new file with the same name works.
If your on windows (at least in my experience) you actually use just 'composer', not composer.phar/.json or any extension.
composer update
composer dump-autoload
This is all I need to type in to be able to access composer in my laravel directory.
i had the same issue, tried several many solutions that worked for others but not in my case.
then some-one told me to drop the 'php' and '.phar' from my command. i.e. directly use
composer update
composer create-project etc.etc.
and to my surprise it worked..
Occasionally, and for reasons that remain a bit vague, restarting the server seems to solve the issue. That step might be worth trying before making changes to file permissions.
Go to https://git-scm.com/download/win
Then download related version and run your composer command inside the git bash
Or else you can use vscode bash;
enter image description here