dyszczo

Hi @gutding,

Debug log should now point to wpdesk_debug only when the logging is enabled in flexible shipping shipment settings. I though that would be sufficient. Before, the log file was always redirected and this behavior was surely invalid.

I would rather not add the hook here: if we do this, it will be much harder to get the final debug info from some clients. Many times they have no idea where the log file really is and this would add another possible layer of abstraction for some clients.

The full path of log file is generated in flexible-shipping/vendor/wpdesk/wp-logs/src/WP/WPCapture.php line 129 in get_log_file()

Best regards,
Dyszczo

Hi @gutding,

The bug was fixed in 3.3.14 about two hours ago.

Best regards,
Dyszczo

Hi,

@aloom I’m quite sure that the error is caused by partial incompletion of the plugin files on the server.
Please try to replace all plugin files on the server again. Please note the “failed transfer” and “sucessful transfers” tab in FileZilla on the bottom and make sure all files are successfully transferred.
Make sure that the class that appears in the error message is indeed on the server.
There is no call to WPDesk_Flexible_Shipping_AB_MenuTest in any part of the plugin now so if the error still appear it has to be invalid uploaded file.
If after that error still persists please paste the error message again.

Ok, I see the error in another thread https://www.ads-software.com/support/topic/fatal-error-3187/

Hmm.. the error says that there is no WPDesk_Flexible_Shipping_AB_MenuTest class. Are you sure that you have the latest plugin version? There is no WPDesk_Flexible_Shipping_AB_MenuTest class in v 3.3.9.

Hi,

@aloom can you paste error message or log? It would help as to reproduce the bug.

• This reply was modified 5 years, 11 months ago by dyszczo.

Hi clamonni,

Is it possible that you have PHP older than 5.5? If so, please consider upgrading to at least 5.6 as PHP version 5.4 does not have security support since 3 Sep 2015.

Hi monikasstempelwerkstatt,

I think you have an old wpdesk helper plugin. In my opinion, the easiest way for fixing this is to delete wpdesk helper plugin and installing it again in the newest version. You will need to use FTP access to the WP.

I’m really sorry about that error.

Best regards,
Christopher

Hi navi4all,

Firstly I’d like to thank you and everybody who reported the bug for your help.
In my previous response, I was trying to explain why we are fighting with this bug so long and was not searching for an excuse.

I think we found the cause why the warnings are appearing in specific scenarios, and now our QA is checking if bugfix resolves the problem. There should be a new version available very soon.

Best regards,
Christopher

Hi navi4all,

> is so diffciult to check what you do ok in 3.1.1 or 3.1.2 and 3.1.4 and not in 3.1.5 or 3.1.6

Well yes:) You have said that in version 3.1 problem was solved and in 3.1.1 problem appeared again.
The only difference in those versions was one line of code – code that for sure was never used in your installation.
It seems that it’s not the version that makes the difference. It must be something much more elusive like the order of plugin activation or some other semi-random factor.

Best regards,
Christopher

Hi jdewit,

We have done a quick review of the possible causes of such behaviour, and the most probable cause is invalid tax settings in WooCommerce. In that scenario, the warnings will probably show themselves whether any shipment method is configured.

Could you please check if the warning persists when FS is disabled, but some other shipment method is an available, ie. flat rate?

Best regards,
Christopher

Hi Tib,

The plugin is checking whether WC is active by doing a lookup into the WordPress activated plugin list using the phrase “woocommerce/woocommerce.php”. The WC version should not make any difference.
As the name needs to have the dir name included, could you check if your WooCommerce installation is in the woocommerce dir and not in any other?

Best regards,
Christopher

Hi,
thank you both very much.
It is strange as there should not be any changes that could cause such errors.

For the time being please disable warning notices by settings in wp-config.php

define( ‘WP_DEBUG’, false );

Best regards,
Christopher

Hi Ellis,

Could you provide content of the warnings? We have checked https://www.suppleform.co.uk/cart/, and there are no warnings at the moment.

We will try to fix the issue as soon as possible.

Regards,
Christopher

Hi michme79,

big thanks for precise info about an error.

It looks like WC team has changed their approach to WC_Logger_Interface, and we have to think if using WC logging engine is still a good idea.

For now to quickly patch the exception please add

 
public function clear( $source = '' ) {}
public function clear_expired_logs() {}

to file located in flexible-shipping/vendor/wpdesk/wp-logs/src/WC/WooCommerceMonologPlugin.php in line 23 (after closing } of the constructor).

Hmm.. are loopreqest still dumping cURL error? If so, then flexible shipping can’t be the main culprit as FS does not have any code related to curl.
Also I’ve FS installed on my WP 4.9.5 with WC 3.3.5 and it works fine so I will try to go deeper ??

Do you have advanced-cache.php in wp-content? If so, please temporarly change its name to advanced-cache.php.old.
Maybe the theme is trying to add something to shipping methods – please try to switch to StoreFront theme for a second and check if it helps.
Generally we have to isolate the reason why FS goes berserk.