Our WooCommerce Site produces an error on Checkout. This was not fixed when I updated to the latest WC version. The only thing that changed between it working and the error is the version of WordPress... The error is in checkout after you submit your payment info (credit card, using Authorize.net) you get the message 'Internal Server Error'. The order does appear in the WC Orders section, a customer account is created, payment is also submitted (but marked as pending). The Console shows a 500 error for ?wc-ajax=checkout
in debug the errors I get are:
Notice: The called constructor method for WP_Widget in LayerSlider_Widget is deprecated since version 4.3.0! Use
__construct()
instead. in /home/content/p3pnexwpnas08_data03/30/2845930/html/wp-includes/functions.php on line 3892
Notice: The called constructor method for WP_Widget in SocialWidget is deprecated since version 4.3.0! Use
__construct()
instead. in /home/content/p3pnexwpnas08_data03/30/2845930/html/wp-includes/functions.php on line 3892
Notice: The called constructor method for WP_Widget in ContactsWidget is deprecated since version 4.3.0! Use
__construct()
instead. in /home/content/p3pnexwpnas08_data03/30/2845930/html/wp-includes/functions.php on line 3892
Strict Standards: Declaration of WC_Shipping_USPS::calculate_shipping() should be compatible with WC_Shipping_Method::calculate_shipping($package = Array) in /home/content/p3pnexwpnas08_data03/30/2845930/html/wp-content/plugins/woocommerce-shipping-usps/includes/class-wc-shipping-usps.php on line 0
Strict Standards: Declaration of WC_Shipping_UPS::calculate_shipping() should be compatible with WC_Shipping_Method::calculate_shipping($package = Array) in /home/content/p3pnexwpnas08_data03/30/2845930/html/wp-content/plugins/woocommerce-shipping-ups/includes/class-wc-shipping-ups.php on line 0
Notice: Use of undefined constant outlet_primary_colour - assumed 'outlet_primary_colour' in /home/content/p3pnexwpnas08_data03/30/2845930/html/wp-content/themes/outlet/includes/theme_customize.php on line 1231
A 500 error could be caused by many things. Do you have access to your apache/php error logs? That's the quickest way to figure it out in most cases.
This issue is now resolved. Apparently, WooThemes own plugins got 'disconnected' and although I had updated the licenses and the plugins, they didn't 'connect' so the updates were not 'live'. I had to disconnect my WooThemes account and remove and reinstall the WooThemes Helper Plugin - once I did, I could reconnect the plugins and then they actually updated. This SOLVED the problem. The main issue for me were the UPS and USPS plugins which were not updated and thus not compatible with the latest WOO standard for Shipping Zones. Ugh.
Related
I'm getting an error when I click on the abandoned cart email link.
Warning: Undefined array key "line_total" in wp-includes/class-wp-list-util.php on line 169
There is 4 method to fix this error:
1: Go To Dashboard -> Update -> On You have the latest version of WordPress, click Re-Install Now.
2: try to use the default WordPress theme to see if your current theme causes this error.
3: Sounds like you are using an incompatible plugin, try disabling plugins one by one to find which plugin causes this error.
4: Finally you may disable wp_debug to ignore this error, go to wp-config.php
and find and set it to disable like the example below:
define( 'WP_DEBUG', false);
I got this error once run my Drupal Project,
Recoverable fatal error: ini_set(): Cannot set 'user' save handler by ini_set() or session_module_name() in C:\xampp\htdocs\jordan\sites\default\settings.php on line 145
You seem to have an older Drupal version which does not run on PHP 7.x. You have to switch back to PHP 5.6 (or switch to a newer Drupal version but that will be more complicated). Usually you can do this in the administration interface of the company where you host your web site.
For example, in the "Odin Automation" panel used by the "magic online" group, you go into the section "Hosting" of the left menu; then, in the list of hosted domains, choose Action => "PHP config", and then, on the next screen, you will see the setting of the PHP version which you can choose from a selection list. You will have to choose a 5.x version, the latest (and only one not to be "not recommended") being 5.6.
After the wordpress update to 4.4 i got the blank admin after the process finished. WP_debug true reveals the following error for wp-admin
Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /var/www/vhosts/site.net/httpdocs/wp-includes/functions.php on line 3787 Notice: wp_register_style was called incorrectly.
Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /var/www/vhosts/site.net/httpdocs/wp-includes/functions.php on line 3787 Notice: Undefined index: enableMultiplein /var/www/vhosts/site.net/httpdocs/wp-content/plugins/menufication111/menufication.php on line 102 Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use
__construct()
instead. in /var/www/vhosts/site.net/httpdocs/wp-includes/functions.php on line 3619 Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 262144 bytes) in /var/www/vhosts/site.net/httpdocs/wp-includes/meta.php on line 844
Even with deactivation of all the plugins error is still present. Only wheb I switch the theme it withdraws and wp-admin can be accessed.
Here is my function.php of the theme:
http://pastebin.com/01XJunTf
Video that explains the problem is to follow.
https://vid.me/6Utj
Every help is much appreciated.
Best regards,
Igor
It was memory limit problem if anyone encounters the same issue.
Thanks for help.
Igor
I am trying to get FOSElasticaBundle to work.
ElasticSearch Instance is running on localhost:9200 and responding.
I followed each step in the docs https://github.com/FriendsOfSymfony/FOSElasticaBundle/blob/master/Resources/doc/setup.md
but at the last step, I get this error in my console:
c:\xampp\htdocs\my\folder>php app/console fos:elastica:populate
Resetting app
Fatal error: Wrong parameters for Exception([string $exception [, long $code [,
Exception $previous = NULL]]]) in C:\xampp\htdocs\my\folder\vendor\rufli
n\elastica\lib\Elastica\Exception\ResponseException.php on line 34
[Symfony\Component\Debug\Exception\FatalErrorException]
Error: Wrong parameters for Exception([string $exception [, long $code [, Exception $previous = NULL]]])
fos:elastica:populate [--index[="..."]] [--type[="..."]] [--no-reset] [--offset="..."] [--sleep="..."] [--batch-size="..."] [--ignore-errors] [--no-overwrite-format]
It seems like there are 3 parameters mandatory for "__construct"-Function, but there are only 2 of them. I've simply tried to add "NULL"-parameter to get it work, but then another function throws an error.
public function __construct(Request $request, Response $response)
{
$this->_request = $request;
$this->_response = $response;
parent::__construct($response->getError());
}
Is this a common problem? How do I solve it?
This is because the ruflin/Elastica package is not compatible with elasticsearch 2.0 yet.
https://github.com/ruflin/Elastica/issues/946
An alternative for now (until ruflin/Elastica is 2.0 upgraded), is to use the latest 1.x version.
You can download it here: https://www.elastic.co/downloads/past-releases/elasticsearch-1-7-3
ES 1.7.3 + FosElasticaBundle (which uses ruflin/Elastica) works fine with Elasticsearch 1.7.3 version.
The reason for this issue is, that with elasticsearch 2.0 the structure of the response error changed (more details here: https://github.com/ruflin/Elastica/issues/946). Instead of a string before it is now a nested array. Elastica is currently not yet fully compatible with elasticsearch 2.0. As soon as a new release of Elastica is out which is compatible with Elasticsearch 2.0 it will probably mean that also foselastica bundle will have to be updated as these changes will break backward compatibility. Be also aware, that this is not the only backward compatibility breaking change.
To follow the progress of the upgrade, follow this issue: https://github.com/ruflin/Elastica/issues/946
I m learning to develop plugin and I am getting error on activation saying
The plugin generated 157 characters of unexpected output during
activation. If you notice “headers already sent” messages, problems
with syndication feeds or other issues, try deactivating or removing
this plugin.
I tried removing and making a new one but same error. here is my code (basic PHP comment to start a plugin, nothing fancy).
/*
Plugin Name: Awesomeness
Plugin URI: http://www.example.com/
Author URI: http://www.example.com/
Author: abc
Description: Just a fun plugin
*/
function fubs(){
error.log("this is working");
}
register_activation_hook(__FILE__,'fubs');
There is no white space before or ending on PHP code.
error is an undefined constant in your PHP code. You try to mix JavaScript with PHP, so PHP prints an error message.
Solution: Use PHP code in PHP and JavaScript code in JavaScript.