Daniele Alessandra

Thank you for reaching out and sharing your feedback. It’s great to hear that you’ve successfully implemented the CSS code and are now able to remove a previously selected Reaction, as well as like an emotion that has already been selected.

Regarding your concern about the Reaction icons being replaced with a loading circle when the page is refreshed, this is indeed a normal behavior. The appearance of the loader at the beginning is due to the fact that not all widgets on the page load simultaneously. Asynchronous calls are made to ensure that the loading of these elements does not block the rest of the page. Typically, this loader should disappear within a few moments, unless there are issues with the loading process. Such issues can arise from a variety of factors, but I haven’t noticed significant problems either on my site or yours.

Since you are experiencing performance issues, I will investigate further. I strive to minimize loading times and maintain optimal performance. Any information you can provide about potential improvements will be very useful in enhancing the user experience.

Hello UK Sentinel, the behavior you reported is a known problem, it happens because the?count?badge?covers the button and captures the mouse events.

The click event is attached to the count badge because you may enable the click to see who added reactions, in the Premium version.

One of the solutions I suggest in this case is to add some custom CSS to change the size and position of the badge. You can check this article: https://www.da-reactions-plugin.com/knowledge-base/faq/how-can-i-resize-the-count-badge/

Another solution that worked for another user is to add a little JavaScript to?hide?the?count?badge?for a few moments when the mouse hovers over it.

Use the snippet below. When the mouse hovers over a Reaction, the?badge?is?hidden?for two seconds. You can change the duration of the effect by altering the milliseconds value (2000 = 2 seconds).

// Function to hide and show the count badge
function toggleCountVisibility(countDiv) {
  countDiv.style.display = 'none';
  setTimeout(function () {
    countDiv.style.display = 'block';
  }, 2000); /// <--- Change milliseconds here
}

// Delegate mouseover event to activate the effect
document.addEventListener('mouseover', function (event) {
  var reactionDiv = event.target.closest('.reaction');
    var reactionCount = event.target.closest('.count');
  if (reactionDiv && !reactionCount) {
    var countDiv = reactionDiv.querySelector('.count');
    if (countDiv) {
      toggleCountVisibility(countDiv);
    }
  }
});

If you have any other suggestions about the UX, I will be happy to receive any feedback, as I want this plugin to be useful for many.

Thank you for using my plugin.

Hello, I didn’t experienced that error during my tests, it may be related to your configuration. Please post a link to a page where I can see the problem and I will do my best to solve it.

I’m pleased to inform you that we have recently released version 5.1.2 of the plugin, which addresses the issue you mentioned. With this update, you should no longer encounter the problem of not being able to like a reaction that has already been liked by someone else. Additionally, the cursor issue should also be resolved, making your experience smoother.

Hello Mativve,

Thank you for using my plugin and for reporting this anomaly.

The plugin calls setcookie within a function hooked to the “init” hook, which should be entirely secure because at that point, no content should have been sent.

The reason you’re getting this warning is that a plugin or theme you’re using is generating output earlier than expected. This could be due to an error or incorrect programming practices.

On my end, with the next update, I will increase the execution priority of that function. I am also considering using the “wp” hook instead of “init”, but it seems like a too drastic solution. I will look for the best possible solution.

In the meantime, you can investigate the cause of the problem by identifying the point where output is generated too early.

Thank you for your support.

Hello, the latest version is 5.0.3 and fixes several bugs, also the one you reported.

Thank you for using the plugin.

Hello,

Thank you for reaching out and providing detailed information about the issue you’re facing with our plugin. I apologize for any inconvenience this may have caused. I’ve received your previous messages, and I’ve already answered through the Envato refund management panel and the contact form on your website.

I understand the situation you’ve described. The darea_fs function is indeed part of the Freemius system and should not exist in the version distributed through Envato. To resolve this issue promptly, I recommend activating a Freemius license. You can do this directly from the plugin’s dashboard when using the free version, and this offers several advantages:

1. You’ll have access to a 30-day free trial.
2. You can activate a monthly license, which provides flexibility and the option to cancel at any time.
3. You’ll receive more frequent updates, as the version distributed via Freemius is updated more regularly compared to the version on Envato.

This should help address the problem you’re encountering and ensure smoother functionality for your needs. If you have any further questions or need assistance with the process, please don’t hesitate to reach out.

Thank you for your understanding, and I appreciate your support of our plugin.

Best regards,

Daniele

Hi there,

Thank you for reaching out and for installing our plugin on your WordPress site. I appreciate your feedback and your patience.

The warning message you mentioned, “This plugin has not been tested with your current version of WordPress,” is likely due to the fact that I haven’t had the chance to run extensive tests on the latest WordPress version yet. However, based on your feedback, it seems that the core functionality of the plugin is working as expected.

Regarding the issue with the Da Reactions widgets not displaying data, this could be a bug, and I apologize for any inconvenience it has caused. I want to assure you that we take such issues seriously, and I’m confident that we can address this in our upcoming release.

If you’d be willing, it would be incredibly helpful if you could provide more details about the problem you’re experiencing. This will assist us in troubleshooting and resolving the issue more effectively. If the problem persists and you’re willing to help, please let us know how we can contact you to gather more information or arrange further testing.

Thank you for your understanding, and we appreciate your support as we work to improve the plugin’s compatibility and functionality with the latest WordPress versions.

Thank you for reaching out! The feature you’re inquiring about, displaying users who reacted on hover, is indeed available in the Premium version of our plugin. To help you get started with it, we’d like to offer you a 30-day free trial of our Premium features.

To access this trial, please log in to your dashboard, and you’ll find a link to start your 30-day Premium trial right there. This will give you the opportunity to explore all the additional functionalities, including the one you mentioned.

Thanks for using our plugin, and we hope you enjoy your trial!

Thank you for reaching out! Yes, the plugin does support adding Reactions to any type of content, including attachments. It automatically integrates Reactions in contexts where it’s easy to determine the specific content being viewed, such as at the end of an article or a page.

To add the widget in other locations, you have two flexible options:

• You can use a Gutenberg block, allowing you to choose the type of content and the ID. This block should be inserted below each image in your gallery and I don’t know if it is possible in your case (I dont’ know what you are using for galleries).
• Alternatively, you can use a shortcode. If you have access to your template’s code, you can locate where the image gallery is displayed and add something like this:

do_shortcode( '[reactions id="' . $attachment_id . '" type="attachment"]');

In this example, we assume that the variable $attachment_id exists and contains the image ID.

Using this method, votes for individual images will be preserved, just as if the Reaction were added from the Single Attachment page.

When the fix will be done, it will be available for both free and paid versions.

I use a third party service to manage subscriptions, you should have an account on this platform: https://users.freemius.com/

Hello,

that constant has been deprecated since PHP 8.1, which means you should receive a warning instead of an error.

The PHP manual suggests using htmlspecialchars to address this issue, but you can also consider using FILTER_UNSAFE_RAW as an alternative solution.

Change this:

$screen_name = filter_var( $_GET["page"], FILTER_SANITIZE_STRING, FILTER_FLAG_STRIP_HIGH );

To this:

$screen_name = filter_var( $_GET["page"], FILTER_UNSAFE_RAW, FILTER_FLAG_STRIP_HIGH );

Hello, thank you for using my plugin, and also for reporting this bug.

The code that generates error is the following:

public function addButtonsToComment( $comment_text ) {
    global $post;
    $options = Options::getInstance( 'general' );
    $globally_enabled = $options->getOption( 'post_type_' . $post->post_type . '_comments' ) === 'on';
    $locally_enabled  = $options->getOption( 'post_type_' . $post->post_type . '_enable_comments_' . $post->ID ) === 'on';
    $locally_disabled = $options->getOption( 'post_type_' . $post->post_type . '_disable_comments_' . $post->ID ) === 'on';

This function should only be executed when WordPress is rendering a single post page so that the variable $post exists. Maybe in your case the comments related hook is executed elsewhere.

A simple solution that you may implement right now is to exit from the function if there is no $post, before trying to access its properties. Someting like this:

public function addButtonsToComment( $comment_text ) {
    global $post;
    if (!isset($post)) {
        return; /// Exit the function
    }
    $options = Options::getInstance( 'general' );
    $globally_enabled = $options->getOption( 'post_type_' . $post->post_type . '_comments' ) === 'on';
    $locally_enabled  = $options->getOption( 'post_type_' . $post->post_type . '_enable_comments_' . $post->ID ) === 'on';
    $locally_disabled = $options->getOption( 'post_type_' . $post->post_type . '_disable_comments_' . $post->ID ) === 'on';

The function is located inside <_hosting_path_>public_html/wp-content/plugins/da-reactions-premium/classes/DaReactions/Frontend.php at row 45.

I will publish this fix as soon as possible.

Hi there,

Thank you for your inquiry. The plugin already supports BuddyPress and allows you to add Reactions to Activities, Profiles, Groups, and Comments. Additionally, when a Reaction is added, it gets listed in the Activities as well. These features are already available in the Premium version, and I recommend activating the Trial version for 30 days so you can verify if it includes all the functionalities you need. I would be delighted if you give it a try and let me know your feedback. We are constantly working to make this plugin even better for all users.

Hello, as far as I know WordPress does not generates Activity Streams without a plugin, so it’s difficult for me to imagine how to implement this feature.
Please, describe in detail your needs (along with a list of third party plugins involved) and I will try to settle you.