I’m Shelby from YayMail dev team. We’re trying to integrate with WC Vendors and improve our addon.
Till now we haven’t confronted any big problem with the integration since the code from your plugin is very well-written and clear (hats off to your Developers!).
I only get a little issue that 2 of your email classes below is having the same email ID “admin_notify_application”:
Of course we can do a workaround, but it’s a bit inconvenient. I wonder if it’s a mistake or you guys did it on purpose?
I’m looking forward to hearing from you guys,
Thank you.
]]>I’ve set up my site locally with a domain that’s the same as my production environment apart from the top level domain as follows:
Production environment: https://mydomainname.com
Local dev environment: https://mydomainname.local
When I open the edit page containing an Emage block, the Emage panel on the left-hand side asks for the purchase code, and the text “Activate Your Plugin” is shown where the image should be. Ideally the plugin would see that the domain name is the same as the one associated with the purchase code and activate the plugin automatically.
]]>Indispensable feature namely when it comes to quickly turn on
define(‘WP_DEBUG’, true);
(as long you can still reach the plugin).
Thank you Ninja Team!
]]>// Function to set the direction
function updatePageDirection(language) {
const rtlLanguages = ['ar', 'he', 'fa', 'ur']; // List of RTL language codes
const htmlElement = document.documentElement;
if (rtlLanguages.includes(language)) {
htmlElement.setAttribute('dir', 'rtl'); // Set to RTL
htmlElement.style.direction = 'rtl'; // Optional: Enforce CSS direction
} else {
htmlElement.setAttribute('dir', 'ltr'); // Set to LTR
htmlElement.style.direction = 'ltr'; // Optional: Enforce CSS direction
}
}// Function to set the direction
function updatePageDirection(language) {
? ? const rtlLanguages = ['ar', 'he', 'fa', 'ur']; // List of RTL language codes
? ? const htmlElement = document.documentElement;
? ? if (rtlLanguages.includes(language)) {
? ? ? ? htmlElement.setAttribute('dir', 'rtl'); // Set to RTL
? ? ? ? htmlElement.style.direction = 'rtl'; // Optional: Enforce CSS direction
? ? } else {
? ? ? ? htmlElement.setAttribute('dir', 'ltr'); // Set to LTR
? ? ? ? htmlElement.style.direction = 'ltr'; // Optional: Enforce CSS direction
? ? }
}However, the developers can be slow to resolve issues. It seems that every three months, a new update is released that not only breaks the plugin but sometimes affects the website itself.
If you’re planning to install this plugin, a word of advice: always back up your website and check the support forums before updating. You never know what the next update might disrupt!
]]>We segment our users into many different types of activities and capabilities. These segments need to be flexible as users can move between groups as they progress through various levels, or as they move into whole different sets of activities. The Groups plugin achieves all this with ease, either through the users admin page, but primarily through hooks to automate the transitions.
Previously, trying to achieve this with standard WP functions was restrictive and complex to maintain. Many thanks to Groups.
]]>package.json may have script start:hot to view changes live in the browser. How can I change proxy in my webpack.config.js?