I loaded the latest version of the Fast and Easy Checkout Plugin for ZenCart. (2.1.8) I'm using ZenCart version 1.5.5 MySQL 5.5.45 and PHP 5.4.45 .
It is not working and I'm finding this in my log:
[23-Jun-2016 20:18:55 UTC] Request URI: /zen-cart-v155/thiRd-EMP-Brick/configuration.php?gID=32, IP address: 208.102.139.70
#1 trigger_error() called at [/home/dblisasmith/public_html/zen-cart-v155/includes/functions/plugin_support.php:68]
#2 plugin_version_check_for_updates() called at [/home/dblisasmith/public_html/zen-cart-v155/thiRd-EMP-Brick/includes/init_includes/init_css_js_loader_config.php:79]
#3 require(/home/dblisasmith/public_html/zen-cart-v155/thiRd-EMP-Brick/includes/init_includes/init_css_js_loader_config.php) called at [/home/dblisasmith/public_html/zen-cart-v155/includes/autoload_func.php:48]
#4 require(/home/dblisasmith/public_html/zen-cart-v155/includes/autoload_func.php) called at [/home/dblisasmith/public_html/zen-cart-v155/thiRd-EMP-Brick/includes/application_top.php:171]
#5 require_once(/home/dblisasmith/public_html/zen-cart-v155/thiRd-EMP-Brick/includes/application_top.php) called at [/home/dblisasmith/public_html/zen-cart-v155/thiRd-EMP-Brick/configuration.php:12]
[23-Jun-2016 20:18:55 UTC] PHP Notice: CURL error checking plugin versions: 28:Connection timed out after 9000 milliseconds
Trying file_get_contents() instead. in /home/dblisasmith/public_html/zen-cart-v155/includes/functions/plugin_support.php on line 68
I've been working on this for two days to get this far, and I'm stumped.
there is a folder called extras and within there is a curltester.php script.
i would ensure that curl is working first from that script. you might have to edit the .htaccess file in that directory to get that script to load.
the error does not seem related to FEC.
Related
This is a recent issue that is causing a headache.
Each time I try to upload a photo via media upload, I am met with the upload bar reading 100%... a stall, and then an error stating:
Maximum execution time of 120 seconds exceeded
The file could be tiny or big - it won't even upload a 10kb file.
My WP debug log states the following:
[05-Sep-2021 16:07:56 UTC] PHP Fatal error: Maximum execution time of 120 seconds exceeded in C:\wamp64\www\sns\wp-includes\functions.php on line 8051
[05-Sep-2021 16:07:56 UTC] PHP Stack trace:
[05-Sep-2021 16:07:56 UTC] PHP 1. {main}() C:\wamp64\www\sns\wp-admin\async-upload.php:0
[05-Sep-2021 16:07:56 UTC] PHP 2. wp_ajax_upload_attachment() C:\wamp64\www\sns\wp-admin\async-upload.php:33
[05-Sep-2021 16:07:56 UTC] PHP 3. media_handle_upload() C:\wamp64\www\sns\wp-admin\includes\ajax-actions.php:2549
[05-Sep-2021 16:07:56 UTC] PHP 4. wp_handle_upload() C:\wamp64\www\sns\wp-admin\includes\media.php:303
[05-Sep-2021 16:07:56 UTC] PHP 5. _wp_handle_upload() C:\wamp64\www\sns\wp-admin\includes\file.php:1037
[05-Sep-2021 16:07:56 UTC] PHP 6. clean_dirsize_cache() C:\wamp64\www\sns\wp-admin\includes\file.php:981
What I have tried:
Restarting WAMP server.
Upgrading my PHP version.
Using a different theme.
Deactivating all plugins.
One thing that may be the cause (and the only other thing I can think of), is that I recently installed and setup Homestead & Vagrant in order to create an environment to start developing using Laravel.
Could this have anything to do with it? If so, where do I start?
You need to change that configuration in the php.ini:
max_execution_time = 1200
or,
left click on wampmanager icon -> PHP -> PHP Settings
and find max_execution_time configuration
In case anyone else runs into this VERY unique issue...
The issue lied in the fact my site is a multi-site install. Apparently there is a cache bug that triggers this issue.
Source: Where I found people with similar issue.
Within that link someone had posted the following code, which can be installed as a plugin. Ultimately, it fixed my issue. Hope this helps someone until Wordpress fixes the bug.
<?php
/**
* Plugin Name: Multisite Cache Bug
* Description: A potential fix for the problem mentioned at https://wordpress.org/support/topic/iis-wordpress-5-6-multi-sites-file-upload-hang/#post-13867460
* Version: 0.1
* License: GPL2
*/
// Prevent direct access to this file
defined( 'ABSPATH' ) or die( 'No script kiddies please!' );
add_filter( "transient_dirsize_cache", function() {return; } );
That limit is part of the PHP.INI file.
WAMPServer has made that a bit easier to change, and can be done from the wampmanager menu in the system tray
Left click the wampmanager icon -> PHP -> PHP Settings ->
Max Execution Time
Then pick a larger number from the dropdown. Wait a few seconds and wampserver will restart Apache and the new Max Execution Time will be set
To do this, I copied the repository WP CLI into Root WordPress
And I wrote the following PHP code to encode it and encountered the following errors
define('WP_CLI_ROOT', ABSPATH . 'wp-cli');
require_once WP_CLI_ROOT . '/php/wp-cli.php';
Warning: include_once(D:\Web\Sites\jupiterx/wp-cli/vendor/rmccue/requests/library/Requests.php): failed to open stream: No such file or directory in D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Bootstrap\IncludeFrameworkAutoloader.php on line 48
Warning: include_once(): Failed opening 'D:\Web\Sites\jupiterx/wp-cli/vendor/rmccue/requests/library/Requests.php' for inclusion (include_path='C:\xampp\php\PEAR') in D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Bootstrap\IncludeFrameworkAutoloader.php on line 48
Warning: include_once(D:\Web\Sites\jupiterx/wp-cli/vendor/wp-cli/mustangostang-spyc/Spyc.php): failed to open stream: No such file or directory in D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Bootstrap\IncludeFrameworkAutoloader.php on line 49
Warning: include_once(): Failed opening 'D:\Web\Sites\jupiterx/wp-cli/vendor/wp-cli/mustangostang-spyc/Spyc.php' for inclusion (include_path='C:\xampp\php\PEAR') in D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Bootstrap\IncludeFrameworkAutoloader.php on line 49
Warning: array_slice() expects parameter 1 to be array, null given in D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Runner.php on line 905
Warning: Invalid argument supplied for foreach() in D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Configurator.php on line 138
Warning: implode(): Invalid arguments passed in D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Runner.php on line 1024
Fatal error: Uncaught Error: Class 'cli\Colors' not found in D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Loggers\Regular.php:70 Stack trace: #0 D:\Web\Sites\jupiterx\wp-cli\php\class-wp-cli.php(881): WP_CLI\Loggers\Regular->error_multi_line(Array) #1 D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Runner.php(248): WP_CLI::error_multi_line(Array) #2 D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Runner.php(1083): WP_CLI\Runner::set_wp_root('D:\\Web\\Sites\\ju...') #3 D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Bootstrap\LaunchRunner.php(23): WP_CLI\Runner->start() #4 D:\Web\Sites\jupiterx\wp-cli\php\bootstrap.php(74): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState)) #5 D:\Web\Sites\jupiterx\wp-cli\php\wp-cli.php(27): WP_CLI\bootstrap() #6 D:\Web\Sites\jupiterx\wp-content\plugins\tabanShahrSiteSaz\Plugin.php(72): require_once('D:\\Web\\Sites\\ju...') #7 D:\Web\Sites\jupiterx\wp-content\plugins\tabanShahrSiteSaz\app\core\SingletonPattern.php(26): TabanShahrSiteSaz\Plugin->includes() #8 D:\Web\Sites\jupiterx\wp-conten in D:\Web\Sites\jupiterx\wp-cli\php\WP_CLI\Loggers\Regular.php on line 70
Thanks in advance for your help
WP-CLI can only be run correctly under the PHP cli SAPI, not under a web server API like cgi, apache or similar. This has some technical reasons, but it is also directly related to your server's security.
WP-CLI is a console application
The first technical reason is that WP-CLI is a console application, and it assumes access to the console input (STDIN) and output (STDOUT) streams. Within the web server context that WordPress runs under, these don't exist. The "input" for a webserver is the URL and payload of a web request, and the output is the HTML or JSON that is sent back to the browser.
WP-CLI is a wrapper around WordPress
The second technical reason is that WP-CLI is basically a "hack" that "wraps" an entire WordPress installation and executes it as a subroutine within its own process. If you would try to use WordPress to launch WP-CLI, you'd have a chicken & egg problem, or a software interpretation of "Inception".
WP-CLI is a sysadmin tool
The reason why this is also directly relevant in terms of security is that WP-CLI is, in the broadest sense, a sysadmin tool. It will directly create, modify, delete files, do direct requests against the database, and more. All of its operations can bypass any security measures that might have been put in place at the application level by WordPress and its plugins. Making WP-CLI accessible to the public-facing frontend and letting it be triggered via web requests would turn it into a critical security vulnerability. No server-side administration tool should be exposed to the frontend in whatever way.
Hopefully, this explains why what you want to do cannot be done and why you would not want to if you could.
The company where I work at has a slightly modified backoffice done in Pydio 8.0.1 up and running in the server.
Thing is I want to run it locally in Xampp to test if it works well alongside the new website I made for the company.
My problem is that I can’t get it running locally even though I have the database running in PHP MyAdmin. The errors that I get are:
Deprecated : Function create_function() is deprecated in C:\xampp\htdocs\backoffice2\core\src\lib\dibi\libs\DibiConnection.php on line 120
Fatal error : Uncaught Pydio\Core\Exception\PydioException: Severe error while loading plugins registry : There was an error trying to connect to your database! Did you change any configuration for the core connection? Or maybe your database is down? in C:\xampp\htdocs\backoffice2\core\src\pydio\Core\PluginFramework\PluginsService.php:819 Stack trace: #0 C:\xampp\htdocs\backoffice2\core\src\pydio\Core\PluginFramework\PluginsService.php(203): Pydio\Core\PluginFramework\PluginsService->getDetectedPlugins() #1 C:\xampp\htdocs\backoffice2\core\src\pydio\Core\Services\ConfService.php(392): Pydio\Core\PluginFramework\PluginsService::getInstance(Object(Pydio\Core\Model\Context)) #2 C:\xampp\htdocs\backoffice2\core\src\pydio\Core\Http\Base.php(62): Pydio\Core\Services\ConfService::getGlobalConf(‘ADMIN_URI’) #3 [internal function]: Pydio\Core\Http\Base::handleRoute(’/backoffice2’, ‘/’, Array) #4 C:\xampp\htdocs\backoffice2\core\src\pydio\Core\Http\TopLevelRouter.php(139): call_user_func(Array, ‘/backoffice2’, ‘/’, Array) #5 C:\xamp in C:\xampp\htdocs\backoffice2\core\src\pydio\Core\PluginFramework\PluginsService.php on line 819
By the Way I noticed that the “Bootstrap.json” has the following custom lines:
“AJXP_CLI_SECRET_KEY”:“vkkhh$lskdNyoNpi$B4Gc5DN”,
“DIBI_PRECONFIGURATION”:{
“mysql_username”:“hardlevel_pt”,
“mysql_use_mysqli”:“true”,
“mysql_password”:“ubukN4g8”,
“mysql_host”:“hardlevel.pt.mysql”,
“mysql_driver”:“mysql”,
“mysql_database”:“hardlevel_pt”,
“group_switch_value”:“mysql”
}
Can anyone give me some insight on this situation? Any help is greatly apreciated.
Maybe it's problem of php version on Pydio 8.0.1
Try to upgrade to latest version of Pydio if you are using PHP 7.2
I am trying to shadow a live website to my local machine, I have finished all the copy thing for home folder and database from cpanel.
So far, I didn't make any change on code part, and just installed xampp and set up phpmyadmin.
after I set the localhost, and loaded the local page then below message displayed.
Fatal error: Uncaught Error: Call to undefined function
mysql_connect() in F:\htdocs\ramtaps\includes\php_library.inc:41 Stack
trace: #0 F:\htdocs\ramtaps\includes\php_library.inc(19):
phpLibrary->createGlobalDatabaseConnection() #1
F:\htdocs\ramtaps\includes\php_library.inc(469):
phpLibrary->__construct() #2
F:\htdocs\ramtaps\includes\config\master.php(859):
include('F:\\htdocs\\ramta...') #3 F:\htdocs\ramtaps\index.php(4):
include('F:\\htdocs\\ramta...') #4 {main} thrown in
F:\htdocs\ramtaps\includes\php_library.inc on line 41
So I looked into the code and it said that mysql_connect is deprecated.
I am pretty new one this field and tried few things and they didn't work so far.
If anyone advises me regarding on this, I would really appreciate.
although you did not mention your PHP version, it is obvious that you are using PHP with version > 7
mysql_connect was removed in PHP 7.0.0 and above
http://php.net/manual/en/migration70.incompatible.php
either install older version of PHP, or change your code
and maybe this is usefull for you http://php.net/manual/en/mysqlinfo.api.choosing.php
This question already has an answer here:
"Call to undefined function mysql_connect()" after upgrade to php-7 [duplicate]
(1 answer)
Closed 5 years ago.
My WP site is currently on php 5.6, but when updated to PHP7, I get the following fatal message and the white screen of death.
Fatal error: Uncaught Error: Call to undefined function mysql_connect() in /home/s7280o8m/public_html/wp-includes/wp-db.php:1568 Stack trace: #0 /home/s7280o8m/public_html/wp-includes/wp-db.php(658): wpdb->db_connect() #1 /home/s7280o8m/public_html/wp-includes/load.php(404): wpdb->__construct('s7280o8m_wp891', 'K(p64#S137', 's7280o8m_wp891', 'localhost') #2 /home/s7280o8m/public_html/wp-settings.php(106): require_wp_db() #3 /home/s7280o8m/public_html/wp-config.php(90): require_once('/home/s7280o8m/...') #4 /home/s7280o8m/public_html/wp-load.php(37): require_once('/home/s7280o8m/...') #5 /home/s7280o8m/public_html/wp-blog-header.php(13): require_once('/home/s7280o8m/...') #6 /home/s7280o8m/public_html/index.php(17): require('/home/s7280o8m/...') #7 {main} thrown in /home/s7280o8m/public_html/wp-includes/wp-db.php on line 1568
F.Y.I :
Ran the PHP7 compatibly test and the plugins + theme were all good.
In trying solve the fatal error, I have deactivated all the plugins (one by one) and then re-activate (one by one), plus changed the theme, but the problem still persists.
Really would appreciate any help on this.
You seem to be using pretty ancient installation of your Wordpress as mysql extension was deprecated for a long time and is removed from PHP7 completely. New code uses mysqli (directly or via PDO), you need to upgrade your Wordpress to recent codebase. Or downgrade PHP.
Are you sure that you are running the latest version of WordPress? (at the time of writing the current version is 4.8.1, you can download it from this page: https://wordpress.org/download/)
It looks like you're running an outdated version because it refers to the mysql_connect function which has been deprecated in PHP 5.5.0 and totally removed in PHP 7.0 (as you can see here).
Also check for any plug-in installed which may be outdated: rename the plugins directory inside of wp-content if you want to disable every plugin at once.