Drupal installation issue. GD and PDO unrecognized - drupal

sorry if this has been answered already, but my searches brought me to nowhere.
I have just installed LAMP environment on Amazon EC2 instance. It runs on:
Ubuntu precise 12.04 amd64 server
PHP Version 5.3.10-1ubuntu3.4
MySQL 5.5.28
Apache/2.2.22 (Ubuntu)
Drupal 7-18
Drupal installation tells me that I have not GD enabled and PDO extension are disabled. However, looking at phpinfo() I have :
GD Support enabled
GD Version 2.0
FreeType Support enabled
FreeType Linkage with freetype
FreeType Version 2.4.8
T1Lib Support enabled
GIF Read Support enabled
GIF Create Support enabled
JPEG Support enabled
libJPEG Version unknown
PNG Support enabled
libPNG Version 1.2.46
WBMP Support enabled
Directive Local Value Master Value
gd.jpeg_ignore_warning 0 0
and
PDO
PDO support enabled
PDO drivers mysql
pdo_mysql
PDO Driver for MySQL enabled
Client API version 5.5.28
Directive Local Value Master Value
pdo_mysql.default_socket /var/run/mysqld/mysqld.sock /var/run/mysqld/mysqld.sock
So, in theory everything must work, why does Drupal not recognize them? I haven't changed anything at all from the clean install of LAMP. May I be missing something then?
Thanks in advance,
maxim

For some reason the problem was solved with reinstalling:
sudo apt-get install --reinstall php5-gd php5-mysql

Related

Supported versions of nginx

Trustwave PCI (Payment Card Industry) compliance has just failed with 'The remote host is running a version of nginx that is no longer supported'. I am running the latest LTS version of ubuntu server 18.04 with the latest version of nginx 1.14.2.
I have looked on line, but I cant find a list of which versions of nginx are still supported/unsupported. I would like to find either a way to determine if 1.14.2 is supported, or an authoritative list to dispute the finding.
Thanks to #lex-li, everything listed under "legacy" is unsupported here, though I thought nginx 1.14.2 was the latest because using the ppa for a stable version of nginx, apt install was telling me that it was the latest version. Recently nginx must have changed their install so that if you want to upgrade past 1.14, you need to uninstall nginx, then follow the instructions here

Intall MCrypt extension in nginx server with PHP 7

I got a server with Ubuntu 16.04. I've installed nginx and PHP 7 with fpm. I need to install MCrypt extension but I cannot find how to do it, I found some information for PHP 5.6 and I'm not sure if the process is the same. How can I do it?
You may have to download the latest version of phpmyadmin 4.6.6
Fixes for PHP 7.1
Problems with MySQL servers running with lower_case_names=2
Fixes for several PHP notices/warnings being shown
they've fixed this bug
by the way , to install mcrypt in unbutu for PHP 7:
apt-get install php7.0-mcrypt
which again is DEPRECATED in PHP 7.1.x
Warning
This extension has been deprecated as of PHP 7.1.0 and moved to PECL
as of PHP 7.2.0.

how to upgrade apache on bitnami wordpress ubuntu instance

I have apache version:
Server version: Apache/2.4.10 (Unix)
Server built: Oct 26 2014 13:31:18
I want to update apache version for http2 support. But simply adding http2 module in httpd.conf give error saying that module not found and sudo apt-get install --only-upgrade apache also doesn't work. Didn't find any solution on internet. How can I upgrade apache?
If you're using a Bitnami WordPress Stack, you have to understand that the Apache installed on the Stack is not installed by apt-get install XXX actions. Therefore, you can't upgrade it that way.
My recommendation install the new WordPress Stack available at https://bitnami.com/stack/wordpress (this way you're installing the latest version of Apache, PHP, MySQL, etc.) and then migrate your WP from the old stack to the new one as explained in the guide below:
https://docs.bitnami.com/google/how-to/migrate-wordpress/
After that, you can remove the old Stack.

Drupal 8 Composer Your requirements could not be resolved to an installable set of packages - commerceguys/intl

I want to install it.
drupal.org/project/social
But also ssh I get an error.
I installed Composer and Drush.
composer-creator of the project goalgorill / social_templat to: giant-master Dr --no-interaction
I get an error in the command enters the picture.
Composer is telling you exactly what is wrong:
the requested PHP extension bcmath is missing from your system
and how to fix it:
To enable extensions, verify that they are enabled in those ini files
Install and enable the bcmath extension. The exact process will depend on your operating system and how you installed PHP.

Composer take too long tu update/install Symfony project (on Windows 10)

Why is 'composer update' running so slow when updating a Symfony project on Windows? If I run diagnose everything looks fine, but the update command takes like 25 min or something. Anyone knows whats is going on?
$ composer diagnose
Checking platform settings: OK
Checking git settings: OK
Checking http connectivity to packagist: OK
Checking https connectivity to packagist: OK
Checking github.com rate limit: OK
Checking disk free space: OK
Checking composer version: OK
And here are my php module:
$ php -m
[PHP Modules]
apc
apcu
bcmath
bz2
calendar
Core
ctype
curl
date
dom
ereg
exif
filter
ftp
gd
gettext
hash
iconv
intl
json
libxml
mbstring
mcrypt
mhash
mysql
mysqli
mysqlnd
odbc
openssl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
Reflection
session
shmop
SimpleXML
soap
sockets
SPL
sqlite3
standard
tokenizer
wddx
xml
xmlreader
xmlrpc
xmlwriter
xsl
zip
zlib
[Zend Modules]
As you can see Xdebug is not ON. Anyone knows what cause composer to run so slow (while Internet speed is decent)? Are virtual machines (i.e. VirtualBox) with Ubuntu on it + Putty the only solution to this issue?
Ps. Symfony 2.4.10 is not supported by Symfony installer.
Composer is stoping at:
> post-update-cmd: Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile
A thing to improve the version resolve speed is by narrowing down the version constraints yourself. In general, I recommend applications to use pretty narrow version constraints (while packages should use the widest version constraints supported). This especially applies to the symfony/symfony version, as there are many versions.
For instance, assume your composer.json file contains something like this: ~2.3. This will simply resolve to the latest version in the 2.x series, which is 2.8. So you can bypass 100 versions (all 2.3-2.7 releases) by setting your version constraint to ~2.8. The result will be the same.
try
composer config --global repo.packagist composer https://packagist.org

Resources