Joy jili casino app login apk.Makakuha ng libreng 700pho sa bawat deposito

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 28 total)

1 2 →

Forum: Fixing WordPress
In reply to: Install theme – Access Denied

Thread Starter demetrioffr

(@demetrioffr)

4 months, 2 weeks ago

They are set that way

Forum: Plugins
In reply to: [WooCommerce] Delete Varients using .cvs and WC Import Export

Thread Starter demetrioffr

(@demetrioffr)

4 years, 6 months ago

Not sure what you mean to change some of my ATTRIBUTES to add-ons?

As here is one of them

92016 variation Hoodie Slow the BEEP DOWN – Your Street and Beach Name 1 0 visible taxable parent 1 0 0 20 0 45 TeeHatch Adult 119 Model F2016 ATC ES ACTIVE CORE (Softer) 0 Size XS 0 Color Black 0

But if i go in my .cvs file I just can’t DELETE THIS ROW – is there a way to mark it DELETED. then import it back in and then it will be gone for that Variation

But if i get a PLUGIN they all want you to pay for them – I just can’t keep buying plugins yet just starting out.

Rick

Forum: Plugins
In reply to: [WooCommerce] variation show all possibilites

Thread Starter demetrioffr

(@demetrioffr)

4 years, 6 months ago

thanks I’ll as my theme company to see if there is a setting to change

Forum: Fixing WordPress
In reply to: How to see what Plugins they are using

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

thanks

Forum: Fixing WordPress
In reply to: How to see what Plugins they are using

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

If you would share what one that you use that would be great – if not i’ll look around

Forum: Fixing WordPress
In reply to: How to see what Plugins they are using

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

Do you know the BEST one to get?

Forum: Plugins
In reply to: [WooCommerce] Products – FILTER BY CATOEGORY – No more drop down

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

But just confused to why my 100+ list will show up on the PRODUCTS page to select the Category.

But it won’t on the ALL PRODCUTS page..

Just a bit odd

I would like to have less than 100 Categories but not sure else how to sort them out..

As I could use a TAG but there is nowhere in the ADMIN section to sort them out buy TAGS that I can find. So I had to do the Categories

have a peak if you wish

https://beachstickers.ca/

Forum: Plugins
In reply to: [WooCommerce] Selling items in a per pound capacity

demetrioffr

(@demetrioffr)

4 years, 7 months ago

You would need to setup different Varients for each of them

Something like

1 LBS – $10
2 LBS – $19
3 LBS – $25

So when you are at the product set the PRUDCT DATA to VARIABLE PRODUCT

Then go to attributes and click on ADD
then add in your name FOR LBS

Then Click on the LBS and enter your VALUES in
1 LBS | 2 LBS | 3 LBS

Check off Visable on the procut page and USed for vaiation

Clcik the SAVE attributes

Then once you are done that Click on the Varitaions TAB and you will now see your
1 lbs
2 lbs
3 lbs

Here you can set the PRICE of each one

Note the weight in the drop down is for the SHipping nothing to do with your so if you need to ship it but the ACTUAL weight in here

Hope this help you

Here is a video that can also help

RIck

This reply was modified 4 years, 7 months ago by demetrioffr.

Forum: Plugins
In reply to: [WooCommerce] Saving Product takes over 2-5 min???

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

Forum: Plugins
In reply to: [WooCommerce] Saving Product takes over 2-5 min???

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

Using 7.3 php

I think it was my FB plugin making up all the different varients as some of my shirts have 30-50 of them

Forum: Plugins
In reply to: [WooCommerce] Variatiion PRicing Won’t set to new Price – Sest some to new and keeps some old

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

This is Firefox

TypeError: e is undefined Grammarly-bg.js:1:1062837
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
TypeError: e is undefined Grammarly-bg.js:1:1062837
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
TypeError: e is undefined Grammarly-bg.js:1:1062837
TypeError: e is undefined Grammarly-bg.js:1:1062837
Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xhtml
TypeError: e is undefined 2 Grammarly-bg.js:1:1062837
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
TypeError: e is undefined Grammarly-bg.js:1:1062837
TypeError: e is undefined Grammarly-bg.js:1:1062837
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
TypeError: e is undefined 2 Grammarly-bg.js:1:1062837
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIInterfaceRequestor.getInterface] network-response-listener.js:84
TypeError: e is undefined Grammarly-bg.js:1:1062837
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
TypeError: e is undefined Grammarly-bg.js:1:1062837
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
TypeError: e is undefined Grammarly-bg.js:1:1062837

Forum: Plugins
In reply to: [WooCommerce] Products – FILTER BY CATOEGORY – No more drop down

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

Ok I just did this test.

Went to my Categories and had 120

I deleted 20 of them to drop it down to 100 and my drop down came back

Very odd. as if you are in the PRODUCT Page you still see the DROP down with 120 Categories on it

Forum: Plugins
In reply to: [WooCommerce] Products – FILTER BY CATOEGORY – No more drop down

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

I have read on other Websites if you have more than 100 Catoegires it will do this..

I’ll try to disable some plugins

Forum: Plugins
In reply to: [WooCommerce] Variatiion PRicing Won’t set to new Price – Sest some to new and keeps some old

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

Im doing about 24 variants.

But I have been doing the same products this way for 8 months. As i’m using Art of where tshirt drop shipper. they make up my products and make the product up and the varients up.

Then I go in and do the price change like I have for over 500 plus products..

I have tried both Chrome and FireFox

This is all I get for the Console in Chomre

JQMIGRATE: Migrate is installed, version 1.4.1
post.php?post=87371&action=edit:1 A cookie associated with a cross-site resource at https://wp.com/ was set without the <code>SameSite</code> attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with <code>SameSite=None</code> and <code>Secure</code>. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #body_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"body_bg_image" id=?"body_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"body_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"body_bg_image" type=?"button" value=?"Remove Image">?
post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #breadcrumbs_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"breadcrumbs_bg_image" id=?"breadcrumbs_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"breadcrumbs_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"breadcrumbs_bg_image" type=?"button" value=?"Remove Image">?
post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #content_bottom_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"content_bottom_bg_image" id=?"content_bottom_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"content_bottom_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"content_bottom_bg_image" type=?"button" value=?"Remove Image">?
post.php?post=87371&action=edit:1 [DOM] Found 2 elements with non-unique id #current-page-selector-1: (More info: https://goo.gl/9p2vKq) <select class=?"page-selector" id=?"current-page-selector-1" title=?"Current page">?…?</select>? <select class=?"page-selector" id=?"current-page-selector-1" title=?"Current page">?…?</select>?
post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #footer_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"footer_bg_image" id=?"footer_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"footer_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"footer_bg_image" type=?"button" value=?"Remove Image">?
post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #footer_bottom_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"footer_bottom_bg_image" id=?"footer_bottom_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"footer_bottom_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"footer_bottom_bg_image" type=?"button" value=?"Remove Image">?
post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #footer_main_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"footer_main_bg_image" id=?"footer_main_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"footer_main_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"footer_main_bg_image" type=?"button" value=?"Remove Image">?
post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #footer_top_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"footer_top_bg_image" id=?"footer_top_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"footer_top_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"footer_top_bg_image" type=?"button" value=?"Remove Image">?
post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #header_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"header_bg_image" id=?"header_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"header_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"header_bg_image" type=?"button" value=?"Remove Image">?
post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #page_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"page_bg_image" id=?"page_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"page_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"page_bg_image" type=?"button" value=?"Remove Image">?
post.php?post=87371&action=edit:1 [DOM] Found 3 elements with non-unique id #sticky_header_bg_image: (More info: https://goo.gl/9p2vKq) <input value type=?"text" name=?"sticky_header_bg_image" id=?"sticky_header_bg_image" size=?"50%">? <input class=?"button_upload_image button" id=?"sticky_header_bg_image" type=?"button" value=?"Upload Image">? <input class=?"button_remove_image button" id=?"sticky_header_bg_image" type=?"button" value=?"Remove Image">?
post.php?post=87371&action=edit:1 [DOM] Found 2 elements with non-unique id #woocommerce_meta_nonce: (More info: https://goo.gl/9p2vKq) <input type=?"hidden" id=?"woocommerce_meta_nonce" name=?"woocommerce_meta_nonce" value=?"735c9ddaad">? <input type=?"hidden" id=?"woocommerce_meta_nonce" name=?"woocommerce_meta_nonce" value=?"735c9ddaad">?
post.php?post=87371&action=edit:1 A cookie associated with a cross-site resource at https://wordpress.com/ was set without the <code>SameSite</code> attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with <code>SameSite=None</code> and <code>Secure</code>. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
post.php?post=87371&action=edit:1 A cookie associated with a cross-site resource at https://wordpress.com/ was set without the <code>SameSite</code> attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with <code>SameSite=None</code> and <code>Secure</code>. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
post.php?post=87371&action=edit:1 A cookie associated with a cross-site resource at https://widgets.wp.com/ was set without the <code>SameSite</code> attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with <code>SameSite=None</code> and <code>Secure</code>. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

Forum: Plugins
In reply to: [WooCommerce] Products – FILTER BY CATOEGORY – No more drop down

Thread Starter demetrioffr

(@demetrioffr)

4 years, 7 months ago

Note – this is the ADMIN SIDE

Viewing 15 replies - 1 through 15 (of 28 total)

1 2 →