MindCreatesMeaning

@magnigenie Thank you, this was helpful.

@salvatorefresta Thank you I will bookmark your recommended plugin for other taxonomy ordering use cases!

Marking this as closed as the answer from @magnigenie was the solution I was seeking.

@philosurfa where did you find your fix? I only have phone, flat number, & landmark.

Hello @archanabarik67 ,

I too find this to be ‘unclear’. What do you mean by tags? (are these checkboxes on the settings pages or special shortcodes that go on the actual frontend pages?)

Ah, thank you Gijo. I understand.

Hmm, I’ve done this and it has not worked. I’m at a loss for now.

With myFacet2p3.4.5 NOT EXCLUDED there are zero JS console errors upon initial page load. The following error appears only upon user interaction with a facet:

Uncaught SyntaxError: Unexpected token u in JSON at position 7991
    at Function.parse [as parseJSON] (<anonymous>)
    at Object.success (autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569)
    at c (autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:186)
    at Object.fireWith [as resolveWith] (autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:188)
    at l (autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:434)
    at XMLHttpRequest.<anonymous> (autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:440)
success @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569
c @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:186
fireWith @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:188
l @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:434
(anonymous) @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:440
load (async)
send @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:440
ajax @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:411
FWP.fetch_data @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569
FWP.refresh @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569
FWP.autoload @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569
(anonymous) @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569
dispatch @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:255
v.handle @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:248

When myFacetWP3.4.5 IS EXCLUDED there are 3 JS console errors upon initial page load. (No interaction is possible because facets do not appear on screen.)

The 3 errors are:

Uncaught ReferenceError: jQuery is not defined
    at autoptimize_single_f6cf72b14b8588f3810eb056b7253107.js:1

Uncaught ReferenceError: jQuery is not defined
    at front.min.js:1
    at front.min.js:1

Uncaught ReferenceError: jQuery is not defined
    at autoptimize_single_5b97a9665877ae41e3f1e28eecb19285.js:42

• This reply was modified 4 years, 10 months ago by MindCreatesMeaning.

Optimizing HTML is the culprit for making the facets disappear. This raises an interesting question, because how can one minify HTML and exclude one plugin from being minimized?

Optimizing JS is the culprit for making the facets work or not work. Excluding the plugin folder ‘ wp-content/plugins/myFacetWP3.4.5/ ‘ causes the facets to disappear. I can’t seem to make them appear and work at the same time.

Optimizing CSS doesn’t appear to have any effect.

The only way I can get the plugin to work with Autoptimize is to Not optimize HTML or JS. (Not something I want to do because it defeats 2/3rds of the purpose of Autoptimize which I enjoy using).

• This reply was modified 4 years, 10 months ago by MindCreatesMeaning.

ANSWERED:
Solution found here: https://www.ads-software.com/support/topic/qr-verification-2/

The problem seems to have been resolved though I have absolutely zero clue as to how or why. It may have been a plugin or caching conflict.

Why has there been no answer to @mazharcatalyst and their follow up? This seems like a very pressing issue for all users and the plugin’s development team.

Does this issue persist?
Has it been fixed via a plugin update?

Any update status for all of us in the community who are following the current status and usability cases of Restopress would be most welcome.

I understand. It’s a little disappointing because [mt-purchase-page] and [mt-reciept-page] would make placement when using page builders, etc. simpler rather than having important elements hiding behind menu bars by default.

Thank you for your response. It’s much appreciated.

• This reply was modified 5 years ago by MindCreatesMeaning.

If I switch away from an Elementor theme it wouldn’t do much good in the end.

Is there any existing record of the filters not working correctly with Elementor present and operational?

I’d be happy to deactivate Themify Product Filters, but in the end – I’ll need use of Elementor for page layout.

Could one of the many extraneous div wrappers that Elementor introduces be there cause of the problem?

Would it be possible to inspect using dev tools to see if this is the case?

Themify Product Filter is deactivated. Only WooCommerce and Elementor and Elementor Pro are activated.

• This reply was modified 5 years ago by MindCreatesMeaning.

Hi Amanda,

It seems to be the opposite, actually.

Even without Themify Product Filter Plugin ( which is the filtering solution I wish to use) the issue persists when WooCommerce product filter exists and is used alone.

The issue seems to arise at the WooCommerce + Elementor level. The problem merely extends to Themify Filter Plugin.

@wzislam Thank you for the answer up to my initial inquiry. I will follow the feature request for ‘auto assigning agents’ and look for it in future versions.

What do you mean by ‘amended’ my recommendation about default status?

Thank you.

I have changed my page back to /support/ from /helpdesk/ and everything is working as should be. It was my mistake as I did not know that the plugin was so rigid in it’s URL structure.

NOTE:
I am not getting e-mail notications (not even in spam folder), but I am opening a new topic for that.

• This reply was modified 5 years, 3 months ago by MindCreatesMeaning.