ZappoB
Forum Replies Created
-
Hi @ajay,
thank you for the information about the output tab in the settings to exclude CRP from products, this I wasn’t aware of and did the trick for me.
Nevertheless was something odd about the update, that all my individual single page settings were overwritten.
Best regards
JoergHi,
so why did it work in previous times?
Best regards
JoergHi Mehmet,
the new update fixed the reoccurring message, many thanks for addressing it.
Best regards
Joerg.Hi Mehmet,
JFYI: I tried your example in the named field as the one and only entry, notification still appears.
Best regards
Joerg
PS: If I delete all entries in the field, this error occurs and no site will load – please make sure, that this query is more error-tolerant:Uncaught Error: in_array(): Argument #2 ($haystack) must be of type array, string given
in /home/mywlande/public_html/wp-shop_test/wp-content/plugins/wp-statistics/src/Service/Admin/NoticeHandler/Notice.php on line 61Call stack:
in_array()
wp-content/plugins/wp-statistics/src/Service/Admin/NoticeHandler/Notice.php:61WP_Statistics\S\A\N\Notice::displayNotices()
wp-includes/class-wp-hook.php:324WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:348WP_Hook::do_action()
wp-includes/plugin.php:517do_action()
wp-admin/admin-header.php:313require_once('/home/mywlande/publi...min/admin-header.php')
wp-admin/index.php:137
Query Monitor
Hi Mehmet,
thank you for this information, but it’s essential to know the ID of this message – what I don’t.
Can you supply this ID? And I really hope, that you address this in a future update.
Nevertheless: I don’t want to sound ungrateful, many thanks for the great plugin!
BR, Joerg
Hi Mehmet,
the workaround “Disable Inactive Essential Feature Notices.” did its job, but it’s really only a workaround.
The field wp_statistics_notifications does contain a long string, but what should I look for?
BR, Joerg
Hi Mehmet,
I couldn’t find any related errors in the error.log, nor the WooCommerce reports. Also, the browser console didn’t state anything.
Should there be anything stored in the database which I can look up?
BR, Joerg
Hallo Mehmet,
thanks for your fast reply, I managed to exclude the tracker.js already, but the message still keeps appearing even using your suggested complete string – I just used only “wp-statistics/assets/js/tracker.js” in “JS Excludes”, “JS Deferred / Delayed Excludes” and “Guest Mode JS Excludes”. I checked it in the developer tools of the browser, that the tracker.js is correctly excluded.
Any further suggestions how to get rid of the message is highly appreciated.
BR, Joerg
I was able to remove this message permanently by dis- and re-enabling the plugin.
Just FYI.
BR, Zappo
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] 2.9.5 “something went wrong….”(deleted)
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] 2.9.5 “something went wrong….”SOLUTION
For anyone having the same problem: it’s only ONE option to disable, no clearing of settings is necessary! Just disable “Vaulting” under “Advanced Card Processing“. That did it for us.
If you clear the settings and setup everything again (as suggested) and you adopt the settings from a cloned site, the problem will appear as before.
This costs us about 4-5 hours from discovering that customers can’t pay with PayPal to this post.
Again: this solution should have come from the developer! What do you pay your developers per hour?
Regards,
ZappoForum: Plugins
In reply to: [WooCommerce PayPal Payments] 2.9.5 “something went wrong….”PS: here the status report. I’m not quite happy with posting this in public.
PPS: Sorry, had to delete it, it included sensible data, like the database prefix. It is rather peculiar that your support asks you to post such data publicly.
- This reply was modified 1 year, 5 months ago by ZappoB.
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] 2.9.5 “something went wrong….”Hello @inpsydekrystian,
we did the same, it took us 35 minutes and the error is either
Irgendwas ist schief gelaufen. Bitte versuche es erneut oder wähle eine andere Zahlungsquelle.in the cart, or
NOT_ENABLED_TO_VAULT_PAYMENT_SOURCE The API caller or the merchant on whose behalf the API call is initiated is not allowed to vault the given source. Please contact PayPal customer support for assistance.on the checkout, so no solution.
Here is the log of the last test:
https://privatebin.syde.com/?0abf490109ee5ebb#4SsNfAnfZJExYawgeaJCW11hfwFiL1DkyhywLn9XRtHMBR, Zappo