Toukir Hossain

Hi,

The issue has been resolved and a new version of the plugin has been released. Please update your plugin to the latest version.

Thank you!

We’ve fixed the issue and released a new version. Please update your plugin to the latest version or remove the old plugin and activate the new one.

Thank you!

Thank you for your feedback! We’ve now added the CF7 to our FormyChat demo. CF7 is a free feature, but you can explore our demo anytime with all other advanced features.

Feel free to check it out, and let us know if you have any further questions!

Hi,

It seems the ‘f’ may have been placed there by mistake. While it doesn’t affect the widgets, we will remove it in our upcoming release. Thank you for bringing this to our attention.

We appreciate your understanding and patience!

Thank you for your raise, your concern is valid and we’re taking your feedback to improve our product.

Some technical decisions have been made intentionally to solve some contingency problems with diverse technology. Here we’d like to share some insights from our developers.

We had to keep both ajax_url and url.ajax_url to keep compatible with the older version of WP Dark Mode Ultimate. In the near future, we’ll keep only one which is URL. ajax. Plugins, including WordPress, and even PHP have a lot of deprecated functions/classes themselves. Removing them without a semi-long transition period may break other systems. We’ll remove deprecated keys soon.

We agree that we have both ways to fetch settings from Inline Script and Ajax (though only one option) because of the diversity of technology. This is not accidental, we had to do it intentionally for a real reason. Inline Script is mainly affected by server-side caching plugins. As it’s a printed JavaScript Object under content type text/HTML, it will always return a cached version of the object to all its visitors. So technically it’s not possible to check if the cache should be bypassed or not without making an extra Ajax Request to the server. Because Ajax and REST APIs are served dynamically, they are not affected by server-side cache technologies and they are not serving the same result for all users.

In this case, Dark Mode will fetch cache-free settings from Ajax only for a single option to check if it’s required to Apply Dark Mode on the client side or not. We could have fetched all the settings through Ajax, it would have required extra queries. The plugin will only fetch a single option asynchronously to keep it lightweight. Asynchronous HTTP request doesn’t let you feel blocked from rendering your webpage.

This Ajax request is not for everyone, it’s feature-specific. It’s being triggered after all the contents, components, and assets are fully loaded and executed to reduce any performance compromisation. Also, registering an Ajax hook in the backend will not be executed until it’s called from the client side.

We’re strictly following PHP Coding Standards, along with WordPress Coding Standards, WordPress Community Standards, and Guidelines to keep the plugin free from bad practices. Still, we may make mistakes so we’re open to taking advice, suggestions, and feedback from our beloved users to improve our product. It’s you who are stakeholders of WP Dark Mode, and we’ll always prioritize your requirements and your needs. We’d like to inform you that we’re actively working on WP Dark Mode’s performance, optimization, and algorithmic applications to reduce memory consumption, and resource allocation as well as improve its performance. We’re hoping to release a version with performance very soon.

We appreciate your understanding!

Hi,

We just shipped an update that should fix your issue. Please update your plugin and enable the “Disable email notifications” setting from Contact Form 7 (https://prnt.sc/7puQsH6K_66O).

If you still face any issues, please let me know.

Hi, sorry for the inconvenience.

Could you share a bit more details about the speed issue you encountered? You may open a support ticket on the WordPress support forum sharing your website URL and the tools you used to perform the speed test. Also, please let us know which specific feature you want in the Free version. We will review it and take action.

Thank you!

Thanks for sharing your feedback. The “Custom CSS” is a premium feature of our plugin. As per forum guidelines, support for commercial products isn’t allowed here. For assistance with the premium version, please contact us through our official support channel.

Have a nice day!

• This reply was modified 6 months, 2 weeks ago by Toukir Hossain.
• This reply was modified 6 months, 2 weeks ago by Toukir Hossain.
• This reply was modified 6 months, 2 weeks ago by Toukir Hossain.

Thanks for your cooperation. We’ll look into the issue and share an update!

Since we haven’t heard back from you, so we’re assuming the issue is resolved and are going to mark this thread as resolved. If you require further assistance, feel free to open a new thread.

Regarding the caching issue, it might help to enable the “Exclude WP Dark Mode from Caching” feature. This could resolve the inconsistency between Light and Dark Modes.

As for Safari 16, the latest version 5.0.9 should be compatible. However, if you’re still experiencing issues with the buttons not working please let us know.

We have released a new version where the “floating switch” issue has been fixed. The floating switch on-off toggle button is fully functional now.

Thank you!

We apologize for the inconvenience. It seems the translation for this keyword might be missing. We’ll fix this in our upcoming release, and the new version will include these keywords for translation.

Thank you for bringing this issue to our attention.

Please let us know your WordPress version and the version of the “WP Dark Mode” plugin you are using.

Sorry for the inconvenience with the ”?Exclude WP Dark Mode from Caching” feature. Could you please let us know which cache plugin you are using?