upgrade fipl/whoops 2.* in laravel 4.2.* - php-7

I using laravel 4.2.19 with php7 then have problem with Exception, I search and see problem in php7 remove Exception class and fipl/whoops 1.* then not working but upgrade to version 2.* then will working with php7.
images error when require fipl/whoops 2.*
And my problem how to upgrade fipl/whoops 1.* to 2.* in laravel 4.2.19 ?

The image you shared shows that Laravel 4.2.x doesn't support the package version you are going to install.
The better is to upgrade from 4.2 to minimum 5.1 to use PHP7 without issues.

Related

Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.1.0". 000webhost Laravel app deployment

i was trying to publish a laravel app on 000webhost aND finally i got his error " Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.1.0". and i don't know what to do
my php version 8.1.6
please help to to solve this challenge
i try to change php version in 000webhost to version 8 and still not support!

Creating project in Phalcon 3.2 is php version specific i.e. php 5.6 or php 7.0

In short : So if I install php5-phalcon (3.2) on local machine with php 5.6, can I easily move code to machine with php7.0 or is code version specific?
Detail scenario :
Local machine has following configuration :
Ubuntu 14.04
PHP 5.6
Phalcon 3.2.2 (installed using command php5-phalcon)
Phalcon devtools 3.2.5
Docker Image / Server Image has following config :
Ubuntu 16.04
PHP 7.0
Phalcon 3.2.2 (installed using command php7.0-phalcon)
Phalcon devtools 3.2.5
My concern here is that if I create skeleton and work on that using phalcon at local machine, will those same files and skeleton work on Docker/Server machine.
Yes. Phalcon 3.2.2 is supported on both PHP 5.6 and PHP 7.0. So either of your machines will work as expected. However, I'll advice that you run the same version of PHP and Phalcon your environments to prevent inconsistencies.
It's like any other php extension in the sense that it is built for your current version of php.
You just don't install it using pecl.
In simple words, it will work with both php version irrespective where I write code. In details answer can be found : https://github.com/phalcon/phalcon-devtools/issues/1106

Zabbix Agent installation on OpenSuse 13.2 with yum fails

when installing Zabbix v3.4 I get the following error message: http://imgur.com/a/xo3tg
Looks like an error in the yum repository. Do you have any suggestions for solutions or something similar?
Best regards
As you can see, there is just 2.2 version of Zabbix (agent, server, proxy, etc.) in that repository.
It seems Zabbix 2.2 (LTS) is the latest version supported by OpenSUSE using its repositories.
By the way, you can install older versions of Zabbix-agent (like 2.2) sending data correctly to newer server/proxy versions (like 3.0 or even 3.2).
I think the major item you will miss with using zabbix-agent older than 3.X is encryption. Other major features work very good.

Dojo 1.9.4 not installed in Notes Client and Domino Designer 9.0.1 FP2 IF1?

First I installed 9.0.1 FP2 IF1 on the server (901FP2HF384_W64) and I was told that this would make dojo 1.9.4 the default dojo, but it was not. I needed to add xsp.client.script.dojo.version=1.9.4 to my XSP Property file to get it to work
Next I need dojo 1.9.4 on the client as well, both as xpinc and when doing preview in web browser so I installed first FP2 IF1 (901FP2SHF63_W32_standard) and later on also FP2 IF3 (901FP2SHF63_W32_standard) but none of these fixes seem to have added dojo 1.9.4
I did try to add xsp.client.script.dojo.version=1.9.4 to my application but I get the following error in both xpinc and preview in web-browser
No Dojo library found matching the configured Dojo library version xsp.client.script.dojo.version=1.9.4.
I ran the following code in a repeat...
com.ibm.xsp.context.DojoLibraryFactory.getDefaultLibrary().getVersion()
...and found out the following
Dojo installed using Preview in webbrowser
1.8.3
1.5.2
1.8.3
1.5.2
Dojo Installed using xpinc
1.9.2
1.5.2
1.9.2
1.5.2
What am I doing wrong here, Why is the fixes not installing 1.9.4? and how can I get 1.9.4 (same as on server) without installing separate dojo packages
Related
http://www-01.ibm.com/support/docview.wss?uid=swg21686751
On the first issue, you should definitely not need the xsp property to apply dojo 1.9.4, it should be the default. We have not come across any issue with this, thus I'm not sure what the problem is that you are experiencing. Perhaps try uninstalling & reinstalling the IF and/or FP2 and/or both?
On the Notes client issues: The 9.0.1 FP2 Interim Fix 1 fixed an iOS8 issue on the server (for XPages mobile controls) by upgrading dojo to 1.9.4 - http://www-01.ibm.com/support/docview.wss?uid=swg21657963#Domino
At present there is no Interim Fix that upgrades the dojo version on the Client - http://www-01.ibm.com/support/docview.wss?uid=swg21657963#Notes. There is no use case involving the use of XPages Mobile controls in the client, so the dojo version in the client was left untouched. It was actually unprecedented to upgrade dojo in an Interim Fix, but the severity of the iOS8 issue meant it needed to be done on the server.
You could manually copy the "com.ibm.xsp.dojo" folder from the server over to your Notes install to have 1.9.4 on both server and client

Apache version 2.1 - What is the deal?

I've been given an assignment to confiure apache v2.1 (on any platform) as a reverse proxy.
Installing Apache2 on Ubuntu gave me version 2.2, but I can't find reference to a version 2.1 for download anywhere. I've seen references to v2.1 in the documentation but under 2.2.
Is it possible to get v2.1?
Apache 2.1 was the development version for Apache 2.2. So Apache 2.1 and 2.2 are essentially the same.
AFAIK, odd number releases are development version, and even numbered are production versions (So 2.3 is the current "development", and will become 2.4 is due time).
Why anyone would ask you to specifically install this version, I do not know, but unless you have a very good reason to do otherwise, just install the latest version.