useremil
Forum Replies Created
-
Forum: Plugins
In reply to: [Query Monitor] Error after update 4.0I am also not able to open the Query Monitor.
query-monitor.js?ver=4.0.0:2
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'match')
at gn (query-monitor.js?ver=4.0.0:2:34179)
at bn (query-monitor.js?ver=4.0.0:2:34350)
at q.kn [as constructor] (query-monitor.js?ver=4.0.0:2:35156)
at q.H [as render] (query-monitor.js?ver=4.0.0:2:8707)
at P (query-monitor.js?ver=4.0.0:2:5701)
at S (query-monitor.js?ver=4.0.0:2:2217)
at query-monitor.js?ver=4.0.0:2:7433
at P (query-monitor.js?ver=4.0.0:2:7799)
at S (query-monitor.js?ver=4.0.0:2:2217)
at query-monitor.js?ver=4.0.0:2:7433
gn @ query-monitor.js?ver=4.0.0:2
bn @ query-monitor.js?ver=4.0.0:2
kn @ query-monitor.js?ver=4.0.0:2
H @ query-monitor.js?ver=4.0.0:2
P @ query-monitor.js?ver=4.0.0:2
S @ query-monitor.js?ver=4.0.0:2
(anonymous) @ query-monitor.js?ver=4.0.0:2
P @ query-monitor.js?ver=4.0.0:2
S @ query-monitor.js?ver=4.0.0:2
(anonymous) @ query-monitor.js?ver=4.0.0:2
P @ query-monitor.js?ver=4.0.0:2
S @ query-monitor.js?ver=4.0.0:2
P @ query-monitor.js?ver=4.0.0:2
S @ query-monitor.js?ver=4.0.0:2
P @ query-monitor.js?ver=4.0.0:2
w @ query-monitor.js?ver=4.0.0:2
x @ query-monitor.js?ver=4.0.0:2
Promise.then
N @ query-monitor.js?ver=4.0.0:2
q.setState @ query-monitor.js?ver=4.0.0:2
t.__c.t.__ @ query-monitor.js?ver=4.0.0:2
k @ query-monitor.js?ver=4.0.0:2
onClick @ query-monitor.js?ver=4.0.0:2
(anonymous) @ query-monitor.js?ver=4.0.0:2Forum: Plugins
In reply to: [Filter Everything — WordPress & WooCommerce Filters] Issues with attacksHello @fesupportteam and @sybydesign
I am writing here to enlighten and to give my 5 cents on the issue, as I have had the same problem.
I have had the similiar experience with attacks/bots/crawlers. I have been trying to figure out what the issue has been for a long time. I suspected early, by the URL request, that it might have had something to do with the filter. Long story short, it was.
My CPU was constantly at 100% and the server had a hard time to cope with all the incomming hits on the various different URL filter searches. The bots/crawlers tried every combination that the filter had as options. The more filter options you had, the longer the URL. The bot/crawler kept calling them over and over.
Here is an example of two of the URLs:
“and/or” is the key here, it tries everything. Every combination of category, subcategory and brand,
- /butikk/k-fiber-special-care-or-hest-or-hover-tilskudd/me-trm/
- /butikk/k-diverse-and-elektrolytter-and-fiber-special-care-and-luftveier-and-pelspleie-and-strigleutstyr-and-tilskudd/
My first solution was to deactivate Filter Everything – waited a few days and checked back on the server. Problem still existed because the server now had to handle the 404.
My second solution was to block all the IPs at the server level. That’s a process worth nothing in the long run. New IPs pop up with small adjustments at the end of the IP.
Here is an overview over 404 status codes the last 24h:
Status Code: 404
Request Count: 102256That’s quite many hits on 404. Not every hit is related to the filter, but 99% is.
To fight off the incomming requests I added a rewrite rule in the .htaccess:
There are more rules, but I exclusevely just pasted the one for this topic. The rule is placed as high as possible in .htaccess.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule ^butikk/k- - [R=404,L]
</IfModule>This stops every URL-request that has “butikk/k-” before it hits wordpress and thus keeping the CPU idle for actuall work. Yes, it also stops real users to use the exact filter. This must be adjusted over time to make sure it doesn’t affect real users.
My CPU is now down at 14%.
Hope this insight helps.
Hi there,
I wanted to stop by to confirm Sven’s issue, inflated numbers in Woocommerce Analytics.
I was experience odd numbers in my store. After some investigation involving:- Manual database table checks in these tables:
wc_order_tax_lookup, wc_order_product_lookup, wc_order_stats, wc_orders
(I was looking for duplicate orders) - Multiple cleanups within WC -> Status -> Tools:
Database integrity, WC Transients, Old Transients, empty customer sessions, empty cache, update database, verify database, clear cache for analytics - Deleting and importing historical data
- Inspecting multiple plugins that “may” cause this issue
I came to the same conclusion as Sven, it must be Cost of Goods.
After deactivating Cost of Goods, then clearing analytics data, the analytics data was spot on as it should be.
For now, I have deactivated Cost of Goods until there is a fix.
Thanks.
Forum: Plugins
In reply to: [Pay with Vipps and MobilePay for WooCommerce] API call 401Beklager sent svar.
Jeg tar kontakt via mailen du har oppgitt. Har foreløpig ikke gjort noen endringer annet enn å oppdatere til siste versjon.
Forum: Plugins
In reply to: [Pay with Vipps and MobilePay for WooCommerce] API call 401Hei Iver, takk for svar.
Har oppdatering Vipps som foreslått. Ingen endring i forhold til det jeg har fra første post.
Ettersom jeg har testet/aktivert både live- og testnøkler, kan det hjelpe å deaktivere pluginen, slette og installere på nytt? Tror du det vil ha noen effekt?
Forum: Plugins
In reply to: [Pay with Vipps and MobilePay for WooCommerce] API call 401Hei Iver,
Takk for oppfølgning.
Nei, det er kun live-nøkler nå.
Før siden var i produksjon (da før domenet var overført og jeg hadde et midlertidig domene uten certificate, https), testet jeg funksjonen “Slå på utviklermodus”. Testet med test-nøkler, men fikk ikke testet ordentlig, da valgte jeg å skru av utviklermodus og gå tilbake til live nøkler. Ble forvirret hvor jeg fortsatt ikke fikk aktivert Vipps betaling selv om live-nøklene var 100% korrekte. Fant senere ut at det var fordi jeg ikke hadde https. Selv uten certificate med HTTP fikk jeg at gatewayen/tilkoblingen til Vipps var OK, men avkryssningsboksen for “slå på Vipps MobilePay” ble automatisk fjernet.Har ingen gjentakende betalinger.
Forum: Plugins
In reply to: [Pay with Vipps and MobilePay for WooCommerce] API call 401Supert. Takk.
Til info ligger den gjennomsnittlige sideforsinkelsen på 0,6s.
Forum: Plugins
In reply to: [Pay with Vipps and MobilePay for WooCommerce] API call 401Hei Iver, takk for svar.
Query Monitor fanger opp denne når jeg beveger meg rundt i wp-admin. Uavehengig hvor jeg beveger meg i backwend/wp-admin, kommer denne opp i HTTP calls.
Det virker som den sender et kall hver gang jeg beveger i WP-admin enten om det er for å endre innstillinger, sjekke ordre, redigere maler, rett og slett hvor som helst i WP-admin. Etter Vipps ble aktivt har jeg opplevd en noe tregere backend/Wp-admin.
Mulig jeg skriv litt misvisende angående det at jeg fikk opprettet og gjennomført en ordre med Vipps. Poenget her var å vise til at det ikke ser ut til å være noen feil med Credentials (som Vipps referer til ved 401 kode).
Hello,
Thanks for responding.
You were right, it wasn’t related to the minification. I was worried I had to do some heavy lifting regarding to find the issue by doing plugins 1 by 1. I really didn’t want to try that and make the site offline (even though staging was introduced, I have no experience by doing this and was worried it copied the same error and me not find the issue stilll).
- I did a Jetpack regeneration of critical CSS (manually, I don’t have premium to make it automatic)
- Wp-Optimize:
- Optimized the database (170 to be optimized)
- Delete expired transient (17 expired out of 151 total)
Now, the settings are visible and accessable to be customized.
Thank you for fast response.
I tried the suggestion to check the “disable minifi for logged-in users”. It was unchecked before I checked it. I purged the cache (it may have done it as a default), opened up a new incognito window to my login area and went to the “Customize” page. The problem still exists.
Even when disabling the minify completly, there is no change within the “Customize” page, it keeps looking like what the picture shows.
I’ve made a loom video for a better understanding: loom.com/share/713f8fd16c454c48a06b2b9498bd8e0b
After some googling and help with chatgpt, I found out that some of the lines where rendered “invisible” for the sortable objects. I don’t know if it is related to WP-optimize or not.
I had WP-optimize before I purchased Astra Pro. Will the minified files that was rendered with Astra free version not update if the Astra Pro Version was installed?
Here is the CSS that was related to my problem:
<li id="customize-control-astra-settings-single-product-structure" class="ast-section-spacing customize-control customize-control-ast-sortable"><label class="ast-sortable"></label><div class="sortable ui-sortable"><div class="ast-sortable-item ui-sortable-handle" data-clone_tracker="" data-value="title" data-index="title" data-title="Tittel">Tittel<i class="dashicons dashicons-visibility visibility"></i></div><div class="ast-sortable-item ui-sortable-handle" data-clone_tracker="" data-value="category" data-index="category" data-title="Kategori">Kategori<i class="dashicons dashicons-visibility visibility"></i></div><div class="ast-sortable-item ui-sortable-handle" data-clone_tracker="" data-value="ratings" data-index="ratings" data-title="Vurderinger">Vurderinger<i class="dashicons dashicons-visibility visibility"></i></div><div class="ast-sortable-item ui-sortable-handle" data-clone_tracker="" data-value="price" data-index="price" data-title="Pris">Pris<i class="dashicons dashicons-visibility visibility"></i></div><div class="ast-sortable-item ui-sortable-handle" data-clone_tracker="" data-value="short_desc" data-index="short_desc" data-title="Kort beskrivelse">Kort beskrivelse<i class="dashicons dashicons-visibility visibility"></i></div><div class="ast-sortable-item ui-sortable-handle" data-value="add_cart" data-index="add_cart" data-title="Legg i handlekurv">Legg i handlekurv<i class="dashicons dashicons-visibility visibility"></i><i class="dashicons dashicons-arrow-down-alt2 ast-option ast-accordion"></i><div class="ast-sortable-subcontrols" data-index="add_cart"></div></div><div class="ast-sortable-item invisible ui-sortable-handle" data-clone_tracker="" data-index="meta" data-value="meta" data-title="Meta">Meta<i class="dashicons dashicons-visibility visibility"></i></div><div class="ast-sortable-item invisible ui-sortable-handle" data-index="summary-extras" data-value="summary-extras" data-title="Extras">Extras<i class="dashicons dashicons-visibility visibility"></i><i class="dashicons dashicons-arrow-down-alt2 ast-option ast-accordion"></i><div class="ast-sortable-subcontrols" data-index="summary-extras"></div></div><div class="ast-sortable-item invisible ui-sortable-handle" data-index="single-product-payments" data-value="single-product-payments" data-title="Betalinger">Betalinger<i class="dashicons dashicons-visibility visibility"></i><i class="dashicons dashicons-arrow-down-alt2 ast-option ast-accordion"></i><div class="ast-sortable-subcontrols" data-index="single-product-payments"></div></div></div></li>Forum: Plugins
In reply to: [Omnibus — show the lowest price] Lowest price for 30 days: {price}.Hello @iworks
I’m not the original poster, but I want to let you know it worked with updating to 3.0.1.
Thanks!
Forum: Plugins
In reply to: [Omnibus — show the lowest price] Lowest price for 30 days: {price}.Hello,
I am experiencing the same problem as OP.
Whenever there is a change in the product (no matter what you change) the new lowest price shows 0 in the shop. In the product edit page in the backend, the ombibus column shows the correct price.
An example:
1. A product shows 100 $ with correct lowest price last 30 days 100 $
2. Edit the product: ex the short description and save
3. Frontend shop now displays lowest price 0 $, in the backend it still shows 100 $.Allow me to post screens with the example from my website:
Before Changes
After changes
The key here is the saving of the new changes which “breaks” the lowest price showing correctly.
It seems the problem started after the recent update (and migration of database). Has there been an error with the update which makes the pulling of the lowest price in the frontend linking to a wrong/old column?
- This reply was modified 2 years, 2 months ago by useremil. Reason: Added example with images