Upgrading Apache, PHP and MySql in Vtiger 6.5 to migrate to Vtiger 7 - vtiger

I was using the vtiger 5.4 and gradually upgraded to 6.5. Now when I tried to upgrade to vtiger 7, its showing the blank page. My version is not matching with the pre-requisites.
What I have the versions are as below:
PHP Version:
C:\vtigercrm-5.4.0\php>php -v
PHP 5.2.6 (cli) (built: May 2 2008 18:02:07)
mysql> select version();
+----------------------+
| version() |
+----------------------+
| 5.0.51b-community-nt |
+----------------------+
Apache Version:
C:\vtigercrm-5.4.0\apache\bin>Apache -v
Server version: Apache/2.0.52
How can I upgrade this to the next level, so that I can continue the Vtiger 7 migration?

If you have no custom code of your own, I would suggest the following steps -
Backup your code and database for 6.5
Uninstall your vtiger 5.4 version
Install XAMPP with PHP7.1 support. Moving away from the standard vtiger installer will let you upgrade to future versions of PHP/apache without this hassle.
Import your database to this new XAMPP and setup the code (you will need to change the config.inc.php)
If everything goes fine, you should have your 6.5 version back working normally and you should be able to upgrade to vtiger 7.
Some pointers -
The new XAMPP installation will have different PHP/mysql settings
Check the Mysql UTF-8 support when creating db
Don't panic if you see lot of notice/warnings, it just means your php.ini is not configured properly yet

Related

How to upgrade SQLite in AWS MWAA Airflow?

I am using yfinance library to get some values like market_cap.
Code:-
import yfinance as yf
com = yf.Ticker('1140.SR')
print(com.fast_info['market_cap'])
I've updated the library to latest version i.e. 0.2.9 locally and on AWS MWAA Apache Airflow.
Locally, I'm able to run the code.
But on Amazon MWAA Airflow, I'm getting an error 'near "without": syntax error'.
Based on my searching, I believe, that the issue is because of a lower version of SQLite. One person was able to resolve the issue by upgrading SQLite version - https://github.com/ranaroussi/yfinance/issues/1372
Locally, here is the configuration:-
Python version - 3.10.8
yfinance - 0.2.9
SQLite3 - 3.37.2
and my Amazon MWAA Airflow configuration is:-
Python version - 3.10.8 (main, Jan 17 2023, 22:57:31) [GCC 7.3.1 20180712 (Red Hat 7.3.1-15)]
yfinance - 0.2.9
SQLite3 - 3.7.17
SQLite is not a python library version, but it’s the a system-level application that needs to be upgraded manually.
I'm able to do locally, but how do I upgrade SQLite to >3.34.x version on Amazon MWAA?
Can anyone help me?
Tried upgrading SQLITE version with requirements file. It didn't work.
apache-airflow-providers-sqlite==3.3.1

How to install multiple sitecore 9.0 instance in different CM servers with single database?

I am installing Sitecore 9.0 instance in 2 CM servers. I have successfully installed Sitecore 9.0 instance in first CM server with the database on a different server.
But when I try to install a new Sitecore 9.0 instance in the second CM server it is trying to create a new database. But I want both my Sitecore instance to use the same database created during the first Sitecore 9.0 instance creation.
Please find below the PowerShell commands used to install Sitecore 9.0
Invoke-SitecoreInstall –Path ‘D:\Sitecore\Sitecore 9.0.1 rev. 171219 (WDP XM1 packages)\XM1 Configuration files 9.0.1 rev. 171219\sitecore-solr.json’
Invoke-SitecoreInstall –Path ‘D:\Sitecore\Sitecore 9.0.1 rev. 171219 (WDP XM1 packages)\XM1 Configuration files 9.0.1 rev. 171219\sitecore-XM1-cm.json’
You can't easily skip the database creation step in sitecore-XP1-cm.json, but as a quick solution you can simply change the SqlDbPrefix parameter when running the installation script on the second CM instance. As a result it will still create another set of databases what you can delete later. And on the successful completion of the Sitecore installation script you will need to change the connection strings on the second CM in ../App_Config/ConnectionStrings.config to point it the databases you want to use.

Vtiger 7.1 Active Directory

Previously installed vtiger 6.5 and had active directory authentication working as per Vtiger 6 CRM AD
Clean Installed Vtiger CRM 7.1 and followed same procedure again for AD, user authenticates ok but it just loops back to the login page again.
Anyone experience this with 7.1?
Have checked config.php and confirm "$AUTHCFG['authType'] = 'AD';" is there.
Have also run the test ldap script and user also authenticates ok.
You seem to be doing everything right but I have found your not the only one with this issue, but if you take a copy of your 6.5 version and migrate to 7.1 using vtiger new files
If you are upgrading from 6.5 to 7.1, you will need to run this process twice. First to upgrade vtiger 6.5 to 7.0 and after that repeat the process to upgrade vtiger 7.0 to 7.1
Download the migration path from the SourceForge site. Patch 6.5 to 7 or Patch 7.0 to 7.1
Unzip patch.zip into Vtiger CRM Folder. A file called vtiger7.zip and migrate folder will be unpacked.
Through browser open /migrate path http://yourdomain.info/vtigercrm/migrate
Someone has successfully compete what you are trying to achieve.
https://discussions.vtiger.com/discussion/188023/vtiger-7-1-active-directory

PHP Parse error: syntax error, unexpected '?' in helpers.php 233

When I create a new Laravel project, the browser displays an error 500. I found this in the log:
PHP Parse error: syntax error, unexpected '?' in vendor/laravel/framework/src/Illuminate/Foundation/helpers.php on line 233
the code in 233 is:
return app('cache')->get($arguments[0], $arguments[1] ?? null);
But as i know, null coalescing operator( ?? ) is supported from PHP 7.0
My PHP Version:
PHP 7.1.8-2+ubuntu14.04.1+deb.sury.org+4 (cli) (built: Aug 4 2017 14:34:05) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.1.8-2+ubuntu14.04.1+deb.sury.org+4, Copyright (c) 1999-2017, by Zend Technologies
Laravel Version: 5.5.0
Who knows what happened?
If I had to guess, I'd say you installed the PPA 7.1.8 as CLI only (php7-cli). You're getting your version info from that, but your libapache2-mod-php package is still 14.04 main which is 5.6. Check your phpinfo in your browser to confirm the version. You might also consider migrating to Ubuntu 16.04 to get PHP 7.0 in main.
I had approximately the same problem with Laravel 5.5 on ubuntu, finally i've found a solution here to switch between the versions of php used by apache :
sudo a2dismod php5
sudo a2enmod php7.1
sudo service apache2 restart
and it works
If you came across this error while using the command line its because you must be using php 7 to execute whatever it is you are trying to execute. What happened is that the code is trying to use an operator thats only available in php7+ and is causing a syntax error.
If you already have php 7+ on your computer try pointing the command line to the higher version of php you want to use.
export PATH=/usr/local/[php-7-folder]/bin/:$PATH
Here is the exact location that worked based off of my setup for reference:
export PATH=/usr/local/php5-7.1.4-20170506-100436/bin/:$PATH
The operator thats actually caused the break is the "null coalesce operator" you can read more about it here:
php7 New Operators
If you have newly upgraded your php version you might be forget to restart your webserver service.
I had the same error and the problem is that I had not correctly installed Composer.
I am using Windows and I installed Composer-Setup.exe from getcomposer.org and when you have more than one version of PHP installed you must select the version that you are running at this point of the installation
I had the same problem with the laravel initiation. The solution was as follows.
1st - I checked the version of my PHP. That it was 5.6 would soon give problem with the laravel.
2nd - I changed the version of my PHP to PHP 7.1.1. ATTENTION, in my case I changed my environment variable that was getting Xampp's PHP version 5.6 I changed to 7.1.1 for laragon.
3rd - I went to the terminal / console and navigated to my folder where my project was and typed the following command: php artisan serves.
And it worked! In my case it started at the port: 8000 see example below.
C: \ laragon \ www \ first> php artisan serves
Laravel development server started: http://127.0.0.1:8000
I hope I helped someone who has been through the same problem as me.
I had similar kind of problem. It looked like this:
Null coalescing operator( ?? ) is not supported by my version of PHP. As I had no option to upgrade the version, I wrote something like this: {{ $product->price ? $product->price:'' }} instead of {{ $product->price ?? '' }} and it solved the problem.

Install Drupal 8.x PostgreSQL

Tell me, how to install Drupal 8.1.9 or 8.2.0 with PostgreSQL? Interestingly, in earlier versions, when the installation was attended by a selection of PostgreSQL. In newer versions this is even no mention
Alternative database engines such as SQLite and PostgreSQL are still available in Drupal 8. However, only the available engines are shown.
If you install the correct PDO module for your PHP environment (e.g. php70-pdo-pgsql) you should have that engine available to you:
You can also use phpinfo() to tell if PostgreSQL support is correctly enabled. You will find the following statement there if it is:
PDO Driver for PostgreSQL => enabled
remove the commented code extension=pdo_pgsql from php.ini file and then start the setup you will see the postgreSQL database option