Virtualgeo
Forum Replies Created
-
Forum: Plugins
In reply to: [Meta pixel for WordPress] fbq is not definedI encountered the exact same problem on multiple sites. (Uncaught ReferenceError: fbq is not defined). After reading the discussion, I ran the same tests, even trying to test the page via VPN from various geographic locations. The problem persisted.
I finally solved the problem by deactivating this plugin and using the code from the snippet provided directly by meta.
I found the code here: https://www.facebook.com/events_manager –> Dataset –> Configure Meta Pixel –> See Instructions –> “Copy the base code”.
This base code doesn’t generate errors, but I would have preferred to save time and use this official plugin. How can the base script work but this plugin doesn’t? There must be some problem.Forum: Plugins
In reply to: [YITH WooCommerce Subscription] conflict with woocommerce-paypal-paymentsHello,
I encountered the same problem and opened a discussion with the “WooCommerce PayPal Payments” support. They replied that “yith-woocommerce-subscription” is causing the problem.
This is the other discussion: https://ww.wp.xz.cn/support/topic/update-to-3-06-broke-my-woocommerce-site/#post-18504012
I am waiting for you to take action to resolve the issue.Forum: Plugins
In reply to: [WooCommerce PayPal Payments] update to 3.06 broke my Woocommerce siteHi,
I have the same issue on my site. Fatal error on DisabledFundingSources.php at line 54.
I’ve read the procedure you indicated and the result of my tests is that the plugin generates a fatal error every time I use version 3.0.6.
I also tried uploading the previous version of the yith-woocommerce-subscription plugin, which is mentioned in the error and that I use on my site, but with no success. With version 3.0.5 of your plugin, there is no error.
I am attaching the error log below:Fatal error: Uncaught ArgumentCountError: Too few arguments to function WooCommerce\PayPalCommerce\Button\Helper\DisabledFundingSources::__construct(), 3 passed in /home/kiinform/public_html/wp-content/plugins/yith-woocommerce-subscription/includes/gateways/woocommerce-paypal-payments/module/src/class-ywsbs-wc-paypal-disabled-sources.php on line 39 and exactly 4 expected in /home/kiinform/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-button/src/Helper/DisabledFundingSources.php:54 Stack trace: #0 /home/kiinform/public_html/wp-content/plugins/yith-woocommerce-subscription/includes/gateways/woocommerce-paypal-payments/module/src/class-ywsbs-wc-paypal-disabled-sources.php(39): WooCommerce\PayPalCommerce\Button\Helper\DisabledFundingSources->__construct(Object(WooCommerce\PayPalCommerce\WcGateway\Settings\Settings), Array, Object(WooCommerce\PayPalCommerce\WcGateway\Helper\CardPaymentsConfiguration)) #1 /home/kiinform/public_html/wp-content/plugins/yith-woocommerce-subscription/includes/gateways/woocommerce-paypal-payments/module/src/class-ywsbs-wc-paypal-payments-module.php(38): YWSBS_WC_PayPal_Disabled_Sources->__construct(Object(WooCommerce\PayPalCommerce\WcGateway\Settings\Settings), Array, Object(WooCommerce\PayPalCommerce\WcGateway\Helper\CardPaymentsConfiguration)) #2 /home/kiinform/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php(58): YWSBS_WC_PayPal_Payments_Module::{closure:YWSBS_WC_PayPal_Payments_Module::services():37}(Object(WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer)) #3 /home/kiinform/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-button/services.php(123): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer->get(‘button.helper.d…’) #4 /home/kiinform/public_html/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php(58): WooCommerce\PayPalCommerce\Button\ButtonModule::{closure:/home/kiinform/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-button/services.php:88}(Object(WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer)) #5 /home/kiinform/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-button/src/ButtonModule.php(57): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer->get(‘button.smart-bu…’) #6 /home/kiinform/public_html/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\Button\ButtonModule::{closure:WooCommerce\PayPalCommerce\Button\ButtonModule::run():53}(Object(WP)) #7 /home/kiinform/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #8 /home/kiinform/public_html/wp-includes/plugin.php(565): WP_Hook->do_action(Array) #9 /home/kiinform/public_html/wp-includes/class-wp.php(835): do_action_ref_array(‘wp’, Array) #10 /home/kiinform/public_html/wp-includes/functions.php(1342): WP->main(”) #11 /home/kiinform/public_html/wp-blog-header.php(16): wp() #12 /home/kiinform/public_html/index.php(17): require(‘/home/kiinform/…’) #13 {main} thrown in /home/kiinform/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-button/src/Helper/DisabledFundingSources.php on line 54
Hi, in the paid version are the payment methods not compatible with renewals eliminated or can they be managed?
I too, after updating from version 2.9.0 to 2.9.1, encountered a fatal error on my test server.
Fatal error: Uncaught TypeError: Argument 1 passed to WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package::addModule() must implement interface WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Module\Module, instance of YWSBS_WC_PayPal_Payments_Module given, called in /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php on line 37 and defined in /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php:244 Stack trace: #0 /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php(37): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->addModule() #1 /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(77): {closure}() #2 /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(92): WooCommerce\PayPalCommerce\init() #3 /var/www/html/wp_ic_eu/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCo in /var/www/html/wp_ic_eu/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php on line 244I also loaded the plugin in the test environment that I ran to test with you, as you can see it works.
https://www.geomaticscube-experiments.com/wp-test/block-editor/HI,
I am very happy to tell you after running various tests that the version of “so-widgets-bundle” you sent me solved the problem!
I am very satisfied, I hope you will include this update in the next versions of “so-widgets-bundle”.
Thanks for everything!Ok, so include the shortcodes with the WordPress function, do_shortcode().
I make a consideration before considering the ticket closed.
I have always preferred your pagebuilder to others because it is one of the few that is light during page construction and clean on the front-end, but above all it also gave me the freedom to create simple but also complex layouts by combining multiple shortcodes inside the widgets , for me this was a great added value compared to all the others and therefore I will no longer be able to use it as I did before.
I would like to know if I can feel comfortable and continue using it with the classic editor but if it works in a way that you developers don’t want, I don’t think it’s advisable.OK, Thanks for the help!
Here are all the cases:
1) Classic Editor with SiteOrigin plugins:
https://www.geomaticscube-experiments.com/wp-test/classic-editor/2) Block Editor with SiteOrigin plugins:
https://www.geomaticscube-experiments.com/wp-test/block-editor/3) Classic Editor without SiteOrigin plugins:
https://www.geomaticscube-experiments.com/wp-test/classic-editor-no-page-builder/4) Block Editor without SiteOrigin plugins:
https://www.geomaticscube-experiments.com/wp-test/block-editor-no-page-builder/Up until version 2.29.5 I have been very happy with the Block Editor with SiteOrigin plugin (2).
With the new version 2.29.6 from this test I see only the classic Editor with SiteOrigin plugin (1) working as before.Sorry, it was a typo, I confirm that there is only one “div” plugin.
Here is the download link:
https://www.geomaticscube-experiments.com/wp-test/data/virtualgeo-div-plugin.zip
Classic Editor Page:
https://www.geomaticscube-experiments.com/wp-test/classic-editor/
Thank youMy test site is a clean installation of wordpress with the “Classic Editor”, “Page Builder by SiteOrigin”, “SiteOrigin Widgets Bundle” and “VirtualGeo DIV” plugins active while the theme I use now is “Twenty Seventeen”, we should see the same things.
I don’t know why we don’t see the same things but anyway the result you got is the problem I’m having.
The shortcodes work, I don’t see why they can’t work.If you can analyze the situation and explain to me what the problem could be, I would be happy.
For me the problem is solved when I comment the line of your plugin as I described.If, despite the tests I sent you, you still believe that the problem is not attributable to the Page Builder, ok, I won’t make you waste any more time.
Thank youVirtualgeo DIV plugin shortcodes work in all cases.
To activate the classic editor on my site I use this plugin.
https://it.ww.wp.xz.cn/plugins/classic-editor/
In this way for each page I can decide whether to use the classic editor or the block editor.Hi, the result you sent me is what I see with the block editor.
are you sure you are using the classic editor?
Here you can see my test (I also tried changing the theme, no I have no involvement.)
Block Editor Page:
https://www.geomaticscube-experiments.com/wp-test/block-editor/
Classic Editor Page:
https://www.geomaticscube-experiments.com/wp-test/classic-editor/Ok,
in this case both shortcodes are executed correctly.
This is the resulting html “<div class=”ic_box”><h1 class=”ic_intro”>Cloud Applications</h1></div>”