So, in college I had a Debian server which used to host a wiki, with mediawiki version 1.9. This server stopped working, and all I have now is its HD. I want to transfer this wiki to a new server, which also runs Debian, but I can't do that with Debian's current stable version of mediawiki, 1.15, because it is not possible to transfer a wiki to another version of mediawii.
So, my idea is to install mediawiki 1.9 on the new server, and then move the wiki. But I am having problems with installing it.
When I go to http://my_hostname/config/index.php, to configure the new wiki, so that I can transfer the other one, I get the following message, and nothing happens:
Checking environment...
Please include all of the lines below when reporting installation problems.
PHP 5.3.3-7+squeeze8 installed"
I really don't have a clue on what is wrong. ANY help would be greatly appreciated!
Like you commented yourself, it would certainly be worth a try to using your existing configuration. The configuration is typically some site preferences and database configuration, so make sure dat your database is setup in the same way as before.
Regarding your configuration problems, maybe php filters away the errors. You can check this by searching for error_reporting in your php.ini.
Just follow the instructions at http://www.mediawiki.org/wiki/Manual:Upgrading. Probably no point in trying to install at MediaWiki 1.9.
You may want to do a clean install of MediaWiki 1.18.1 first just to make sure your system is ready, all dependencies met, etc.
Related
We have a productive GitLab 6.8.1 running. I've set up a parallel VM with GitLab 7.10.4. Now I want to move all data from the old installation to the new one. I've already found a way how to move the bare repositories, but I have no clue how to import the user account information, issues, etc.
EDIT: The thing is further complicated by the fact that the original installation was built from source, was running on Debian, used MySQL as a database and the whole installation was pretty much messed up. That's why I didn't manage to migrate the old server and decided to set up a new one. The new server is an Ubuntu machine with GitLab installed from apt-get package (I think that's Omnibus, but I'm not sure what this means.) The new installation seems to use PostgreSQL.
FYI You haven't specified whether the old or new server is running a source installation or omnibus, or whether you're running a MySQL or Postgres database. Instructions differ depending on these factors, so please clarify and I will update my answer.
The first thing is that you will need your old and new servers to be on the same version of GitLab. You cannot migrate anything other than repos without having synchronized versions.
Depending on your reply to the above you will either follow instructions similar to the backup and restore tasks or by running the backup and restore tasks. Both options generally require you to manually copy configuration files or migrate settings from multiple files to a single new file (in the case of going from a source install to Omnibus). The Omnibus upgrade guide above lists the configuration files that need to be migrated depending on your environment.
Update based on edited question: There's a guide specifically for that scenario in this section of the Omnibus upgrade guide, using Option 2. You still need to have the same version on both old and new servers, though, I believe.
For some days I've been using MAMP Pro 3.07 from http://www.mamp.info.
Great tool and all works fine.
But now I have the problem, that for a new project I need to connect to MSSQL.
I searched for a howto the last 3 hours in www, but can´t find a working answer or am I to stupid?
Is there a possibility to install "PDO-dblib" on MAMP on OSX Yosemite?
Or can somebody explain me how I can do this?
Thanks in advance!
From PHP website:
PDO_DBLIB: This extension is not available anymore on Windows with PHP 5.3 or later.
I see MAMP allows you to use different versions of PHP, so if you choose php 5.1.6 it may work. There is also a comment there from a guy who wrote its own class for this purpose. I am adding you also the pecl repository for this PDODblib.
Apart of this I am recommending you to use the latest version of PHP and do not rely on maintained extensions. PDO, which comes now by default with PHP, allows you to connect to MSSQL databases and you can find documentation here and here.
I have created a module on a development server (xampp) all is fine and working. However when I have move the module to my production server it fails to install properly, WSOD. From db I can see that my fields are not being created.
Drupal version 7.27 on both, both clean installs with the same dependencies installed.
Nothing in apache error log.
Grateful for any tips.
Mathew
ok just incase this helps someone else further down the line - this was an issue with different versions on PHP on the two servers one had 5.3 the other 5.5. One supports short form arrays [] and one does not which was my problem.
Would i have been able to resolve this from PHP logs?
I am hosting a website, using the Symfony framework, on a MAMP server on my Mac, and I'm trying to generate bundles automatically with the help of the terminal.
If it is relevant in any way, here is what I try to type into the terminal:
php -c /Applications/MAMP/bin/php/php5.4.10/conf/php.ini php
app/console generate:bundle
And here is the error I get:
XCache requires Zend Engine API version 220100525. The Zend Engine API
version 220090626 which is installed, is outdated.
Could not open input file: php
Do any of you have an idea of how I could update the Zend Engine API or otherwise fix my problem? That would be of HUGE help!
Edit:
Thanks to the help of whistlergreg I've gotten rid of one of the problems it seems, but I still get the following response:
Could not open input file: php
Edit:
I was told by someone that the second php in my command shouldn't be there. Instead I should write:
php -c /Applications/MAMP/bin/php/php5.4.10/conf/php.ini app/console
generate:bundle
It seems like the second error was caused by a noobish typo by me, and now everything is working.
Note: With Xcache 3.0, xcache.so is no longer a Zend Extension but a PHP extension
remove zend_extension = */xcache.so
load it using extension = xcache.so
This might be why the error is being thrown:
The main cause for the error is because of outdated build of XCache
(not related to its actual version though), that mostly happens when
user upgrades PHP version. When compiling and building XCache, it’s
been associated with the version of Zend Engine API that exists on the
system at the time.
When PHP is updated or upgraded, the Zend Engine API is updated too, causing XCache module to fail as the version no longer matched.
The solution for the Zend Engine API version is newer error is pretty
simple. Just download, compile and install XCache again will fix and
resolve the issue permanently (until new PHP major version update). 1
Switch MAMP to use APC from the MAMP preferences menu, that worked for me! Make sure you restart apache after making the change.
Has anyone had luck compiling mod_libpq for Apache 2? I know there were some fairly major changes so the source might have to be updated, but has it been done already by someone?
Also, has it been compiled for win32 (either version of Apache, or another web server altogether?)
I've written an updated version for Apache2.2 which can be downloaded from
http://asmith.id.au/source/mod_libpq2.c
However, it is my first attempt at writing a module for Apache2 and it is not debugged yet.
Previously I had no use for it as I was still using Apache1.3 but since I am now faced with retiring that old server I guess I'll have to finish off the new version.