xninedesign

It didn’t occur to me to show you in any way that I used your solution, because firstly, I use it myself in my code, and hence I know that your solution doesn’t work, and secondly, on the first of my screenshots, it’s clearly visible that I used exactly the same thing, but not to change the class of the <li> elements, but <a> (class=more hover). If your solution would worked (which my screenshot shows), the second menu with product categories would have links with arrows looking the same, because the same snippet I use (without a condition relating to the taxonomy type) to add additional classes to <a> elements implies this for all elements of this type on the page. In the second of my post, I clearly wrote that the widget I use to display the list of Woocommerce product categories is the Gutenberg block widget, so since I specified that then, I don’t understand why you didn’t immediately realize that your code wouldn’t work, but instead asked if I used it at all. If you had written instead that it’s not possible to do it because of using the Gutenberg block widget (which I didn’t know), I wouldn’t have pasted those screenshots links and wouldn’t have continued explaining.

I didn’t write anywhere that I’m referring to UL (the arrows on screenshot also don’t suggest that at all) because it was not my need. In the first post here, I wrote about links, so your suggestion was quite accurate in terms of understanding my needs, but unfortunately, also ineffective.

Nevertheless, thank you for your time and willingness to help. Regards.

• This reply was modified 2 years, 1 month ago by xninedesign.

Thank you @serafinnyc for your reply.
Unfortunately this not resolve my needs.

You tried manipulate the standard WordPress widget which displays a <ul> element with categories. Woocommerce widget which create similar HTML element but with <ul> element with Products categories is a different gutenberg block widget, so your solution do not affect anything in it.

• This reply was modified 2 years, 1 month ago by xninedesign.

Hello @michael-travan .

Thank You for response.
What I needed support for was a bit more complex, as I was integrating my own script for the Newsletter subscription form. The plugin you suggested wasn’t entirely suitable for my case because my website also functions as a store based on Woocommerce. Creating an account in Woocommerce automatically added me to the subscriber list, which shouldn’t have happened. My intention was for the form to generate a WordPress account assigned the Subscriber role (through custom code), consequently enrolling it in the list of subscribers managed by your plugin. When someone created an account in Woocommerce, your WP Users Integration plugin caused them to also be added to the list. It doesn’t offer the ability to exclude accounts with a specified role. Moreover, my script supports sending links to confirm subscription and unsubscription, so signing up and unsubscribing required a different solution than what the aforementioned plugin provides. Consequently, I familiarized myself with API v1 of your plugin and successfully managed everything by adjusting my code accordingly. Thanks to this, my script no longer needs to create any user accounts; it simply adds a subscriber to the list from your plugin.

I have already achieved what I needed most. Thanks for your interest.

Hi. Thank You very much for Your answer.
What i understand from this article is that I should all my Polish strings change to English first, and then create with Loco Translate a Polish translation. Do I understood well?

Best regards
Chris

Hello.

I got this problem even on fresh WordPress installation.
Here is the clip uploaded to Youtube.

https://youtu.be/yXWB7fCv4KA

Chris

Hello. Thank You for Your answer.

First of all i forgot to mention about the main action which cause this error.

I remember that i entered into Add New Form page and nothing was bad yet. What i had to do to make this error happen is to expand the LifterLMS panel (that one from LifterLMS pinned button between Update and Settings icon on top right corner) and after that reactivate the WordPress Settings panel. Now i can’t enter into Add New Form Page because this problem, but i figured out how to reproduce this issue on Add Lesson page. So here is the short video with it.

https://gemoo.com/tools/upload-video/share/602950044051046400?codeId=MpK91JXYJOK01&card=602950040083234816

The difference between Add New Form page and Add Lesson page is that i can open Add New Lesson Page every time after this issue happen, but when it comes to Add New Form page every opening of this subpage immediately ends with this error.

Yes it is about the WordPress Dashboard > LifterLMS > Forms page.