I called v-webmail using open source to try to fix a few
However, at the time of installation,
Unfortunately this application needs the imap extension
loaded and the version of php to be at least 4.1.0 to run.
Other configuration parameters may also be faulty.
Config file local.config.xml: Writeable!
IMAP Extension loaded: Loaded Message is output.
This file is normally created local.config.xml, and gave the necessary permission to 644.
I wonder what caused this error to why.
Why this error occurred ever know about them?
Related
I'm transitioning my website from PHP v.5 installed on a shared web-hosting account (at DreamHost) to run on PHP 7.3.11. After transition, I started noticing that once in a while I get these warnings:
Warning: preg_match_all(): Allocation of JIT memory failed, PCRE JIT
will be disabled. This is likely caused by security restrictions.
Either grant PHP permission to allocate executable memory, or set
pcre.jit=0
The last one originated from this line of code that was supposed to replace special tags in my posted HTML for the page:
if(preg_match_all("/\[".$tagBegin."(\S)+\]/U", $html, $matches, PREG_OFFSET_CAPTURE) !== false)
Is there something that I need to do differently in v.7.3 to avoid that warning?
You should be able to ward off this warning by using ini_set to change the config value suggested by the warning message itself:
ini_set("pcre.jit", "0");
Be sure to run that line of code before any usages of regular expressions.
For me I have added pcre.jit=0 to php.ini file in [Pcre] and this worked very nice.
Search in whatever system manages your website : the cPanel's File Manager, your web hoster's admin dashboard, your computer's disks- for 'php.ini'. There won't be many files named like that in places that have something to do with your website or application that is giving you an error message.
Edit that php.ini file and find the section [Pcre] and add this line at the bottom of that section : pcre.jit=0
It should look something like this:
Save your changes and reload the page or application.
Open your php.ini file (C:\xampp\php\php.ini) and search for this setting:
;Enables or disables JIT compilation of patterns. This requires the PCRE
;library to be compiled with JIT support.
;pcre.jit=1
Remove the comment and make sure that it is set to 1:
pcre.jit=1
Restart your Apache server and the warning will go away with the correct permission set.
I have Xampp and a previous version of PHP.
I fixed that error by following a video on Youtube called :
PhpMyAdmin Error Warning in .\libraries\classes\Config\FormDisplay.php#
basically what he did is he went in the button of PHPAdmin page and downloaded a new version, then he made the config file inside PHPAdmin folder(in Mac) and deleted all files then pasted the new files of the new PHP admin along with the config. It worked great for me and him.
When I try to install Opencart V3.0.2.0 in Linux server, getting following error message.
Fatal error: Internal Zend error - Missing class information for in
/system/storage/vendor/twig/twig/lib/Twig/ParserInterface.php on line
31
I am not able to start my installation process. Any idea, Please help.
While this is not guaranteed to work, but since few people reported that they have been able to solve it disabling APC I would give it a try.
If you want to disable Alternative PHP Cache (APC), you can do so by modifying your PHP initialization file file.
Using your hosting account's editor (Web & Classic / cPanel / Plesk), open your website's PHP initialization file.
Note: I recommend backing up your PHP initialization file file before modifying it. You can do this by copying and renaming it in your file manager.
On a new line, type apc.enabled=0
Save your changes.
Why ftp_connect () fails for networksolution hosting using PHP? and produce following error as:
500: Internal server error This error is generated when a script
running on the server could not be implemented or permissions are
incorrectly assigned for files or directories
Troubleshooting suggestions:
Temporarily disable any rewrite rules by renaming your .htaccess file
if it exists.
Ensure that any CGI or Perl scripts have at least .755. permissions.
If trying to run PHP and you get this error, you may have an invalid
php.ini in your /cgi-bin, or may be missing your php.dat file in this
folder.
The error 500 indicates a fatal error in the PHP code.
The only reason I can imagine, why the ftp_connect can fail fatally, is that the function actually does not exist. Meaning, your PHP installation was built without an FTP support.
See https://www.php.net/manual/en/ftp.installation.php
What does function_exists("ftp_connect") return?
Hello I have simple php script well it is more a html file with few php lines.
Yet it produces tons of errors in log that look like this on every line:
PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20100525/suhosin.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20100525/suhosin.so: cannot open shared object file: No such file or directory in Unknown on line 0
I can not locate in nowhere in code where suhosin might been called...
This error is present on 2 different servers.
EDIT:
In phpinfo there is no suhosin present...
Thanks.
We will likely need more information in order to provide an accurate resolution, such as What version of PHP is installed on your system? however I will give you a general resolution.
Generally this issue is caused by PHP Upgrade, most recent PHP versions does not support suhosin as this only applied to older versions of php that needed additional security.
If you are on a shared hosting server you need to contact to your hosting provider and notify them about this issue, they are likely able to resolve it quickly.
If you are on a Dedicated server, VPS server or a localhost environment you can solve this issue by following the steps below:
Find your php.ini location [You can use phpinfo() to locate php.ini file]
Open the php.ini file and search suhosin.so
When you find suhosin comment this line extension = "suhosin.so" by adding semicolon at the beginning of the line, For example: ;extension = "suhosin.so"
Save this file
Restart Apache service httpd restart
Note: If ClouldLinux installed on your server, you need to force update CageFS by issuing the following command at the command line cagefsctl --force-update
I have problems after updating Zend FR to 1.11
Mimetype file checking generates:
Warning: string extension `B' invalid
It looks like cause of problems the string in the Zend_Validate_File_MimeType
$finfo = finfo_open(FILEINFO_MIME_TYPE, $file);
I have created simple test case
$finfo = finfo_open(FILEINFO_MIME_TYPE, '/usr/share/misc/magic');
echo finfo_file($finfo, PUBLIC_HTML_PATH . '/images/missing.png');
finfo_close($finfo);
And i got same error :(
finfo_open(FILEINFO_MIME_TYPE, '/usr/share/misc/magic'); //generates: Warning: string extension `B' invalid.
My OS: Kbuntu 10.10
Where am i wrong?
Ran into the same error message ("Warning: string extension w' invalid in Command") as Mike Purcell, but the fix for it was different.
On our servers we had a /usr/share/misc/magic and a /usr/share/misc/magic.mgc file. The magic.mgc file had been compiled from the magic file, but PHP still wasn't happy talking directly to the /usr/share/misc/magic file (we'd shifted to that file as part of debugging that the magic.mgc file needed updating).
The fix for us was changing our putenv line back to the magic.mgc file:
putenv('MAGIC=/usr/share/misc/magic.mgc');
Then, magic-ally :-) , the whole mime-type detection system started working again.
This may not pertain to your EXACT issue, but it did resolve the issue I was having which resulted in a very similar error message: "Warning: string extension w' invalid in Command".
For us, we have a heterogenous setup where some servers are still running php 5.2 and others running php 5.3. On the 5.2 boxes the magic file resides in /usr/share/file/magic, but on the 5.3 boxes the file resides in the default path of /usr/share/misc/magic. Apparently someone tried to reconcile these path differences by symlinking the 5.2 path so the codebase could be php version agnostic. But according to some comments posted on PHP site regarding symlinks to the magic file, it will result in unexpected behavior, which of course was resulting in the aforementioned error message.
So be sure the path you are passing is to the actual magic file, and not a symlink, and see if that resolves your issue.
Depending on your PHP version the magic format may be updated. This is documented in a note at http://php.net/manual/en/function.finfo-open.php
run php -v to see your version
I got the same error when pointing to an older magic file in our source tree, and resolved it when pointing to a newer magic file from my current linux distro
I had this error in Laravel (minus Zend FR, of course). Running PHP 5.3.21 on a Windows box with IIS.
Finding very little info online I was close to giving up. It worked initially when I followed instructions in the comments on PHP.net, which were basically to add fileinfo.dll to your PHP installation, and to also download the relevant magic files and point an environment variable to them.
There was some initial confusion until I realised I didn't actually have php_fileinfo.dll, so as well as adding it to the php.ini file, I had to download the file itself and add it to my ext directory.
Now what really had me stuck, was that it worked initially. The next day it didn't. To cut a long story short, it didn't need the environment variable, MAGIC. The reason this had me stuck, is because I had tried every possible scenario, but once the environment variable had been set, it had been set. And I had to restart the Windows server after removing it, to unset it. Once I did this it worked perfectly.