whax
Forum Replies Created
-
Hi Sarun,
I was experiencing the same error, found this thread, tried your code, but ended up with the same “0.375” error.However, I was just able to reconnect and sync our site with ShipStation after disabling the plugin “Advanced Product Quantity”. Are you by chance using that, too? I haven’t dug into its code to see where the problem lies and I have yet to see if the problem will reoccur after reenabling it, but wanted to pass this along.
My apologies. I will do further testing to see what happened here. Thank you!
I’m also searching for a solution to this. I’m experiencing it on Safari v15, too. 16 and newer do not exhibit the problem.
I’m still encountering this error with v2.9.9.5 and Elementor v3.8.1.
PHP Fatal error: Uncaught Error: Class ‘Elementor\\Scheme_Typography’ not found in /xxx/wp-content/plugins/all-contact-form-integration-for-elementor/includes/gravity-form.php:551
The file includes/gravity-form.php:551 still includes a reference to the Scheme_Typography class removed from Elementor in v3.6.
Thank you for looking into this.
Forum: Plugins
In reply to: [Entry Expiration for Gravity Forms] Entries not deletedUpdate: The form in question was inactive when I set this up. As soon as I reactivated it and allowed the cron task to run, a number of items were deleted as expected.
Forum: Plugins
In reply to: [Speed Optimizer - The All-In-One Performance-Boosting Plugin] Fatal ErrorThe site was running PHP 7.2.34. Before upgrading to PHP 7.4 I attempted to reactivate the plugin (now v7.1.4) but received the same error as before. After upgrading to PHP 7.4 I was able to successfully activate the plugin.
Thank you for your help!
Sorry folks, I was in a hurry so migrated to a different redirect plugin. :/
Also encountering OP’s issue though it was hit and miss; some redirects worked but most did not. I disabled all other plugins on a staging site and still am encountering the problem.
Forum: Plugins
In reply to: [Column Shortcodes] Compatibility issues with WordPress 5.5?Encountering the same issue and also using ACF. Disabling the plugin is the workaround.
Console error:
Uncaught TypeError: $(…).live is not a function
https://kelvix.com/wp-content/plugins/column-shortcodes//assets/js/admin.js
in thecodepressShortcodesfunction, line 35.Just here to say I’m having this problem too. I’ve initiated a support ticket with iThemes. But I have this installed on 30+ sites and so far 3 of them have gone down in this manner in the last week after updating to the latest version of the plugin.
Thanks for your response. This will solve the issue for now.
Perhaps you will consider this feature request/change:
In the case where WooCommerce is set to sell only to specific countries, no other options (neither the store base’s country nor the “other” option) should appear in the country switcher selectbox. I do not see a reason a customer should be allowed to choose anything but the countries I can sell to.Thank you for your good work on this plugin!
Thank you for your reply,
How do I prevent that from happening? We do not wish to show the base shop’s location as this site does not sell to that country. This is why we specify the two countries we do serve in the WooCommerce settings.
Related question: If we buy the Pro version of the plugin, would the currency switcher work the same way? Would it show USD (which we don’t support) in addition to the two currencies we do support?
Forum: Plugins
In reply to: [Geolocation IP Detection] Fatal error: getWithPrefixLen()Resolved
Forum: Plugins
In reply to: [Geolocation IP Detection] Fatal error: getWithPrefixLen()@benjamin4 this is working great, thank you! I am concerned what might happen should WooCommerce’s implementation of the geolite2 library change. I’ll be following the Github issue you started. Thanks again for your attention to this issue.
Forum: Plugins
In reply to: [Geolocation IP Detection] Fatal error: getWithPrefixLen()I agree with @howdy_mcgee, I understand library dependencies can be a problem with plugin dev but I’m hoping there’s some namespace(?) changes that could be made to isolate this plugin’s code? Thank you!