Alimir

Yeah I think they have moved your posts using a plugin instead of moving whole database! we can’t help on this case! You need to check it with your sever provider.

Hey @duckland

Yes, but you need to do it with a custom hook in Elementor.

Hey @n33d

Can you give us some details on how you implemented the like button on your pages? Do you have this problem in both single and archive pages? And can you make sure you don’t any other server-side cache?!

Because we have a specific method for WP Rocket to purge the cache after submitting the like button and we have not had a similar report until today!

Hey @michaeloestergaard
Please try following sample code and let me know if you had any issues:

add_action( 'wp_footer', function() { ?>
    <script>
      (function($) {

        document.addEventListener('facetwp-loaded', function() {
          $(".wpulike").WordpressUlike();
        });

      })(fUtil);
    </script>
  <?php
}, 100 );

hey @hessi2
we save likes info in wp_ulike_meta table! But if moved and can’t see the right values, It means that probably your post IDs has been changed!
How did you move your database to the new sever?!

Hey @grosso2020

Do you use the latest version of plugin?!I tested with php 8.2.4 and no error occurred!

Hey @unster

Unfortunately no. Dislike functionality is only available on the PRO version.

Hey @webfactorydotsu

We are glad you liked wp ulike and shared this feedback. ??

Regarding your first issue, can you please make a support ticket and share your error log in there?
We are using wp ulike in different php 8+ versions and so far we have not encountered any error! That’s why we guess that it might be a conflict with another plugin!

and for second case, I will try to check it with infinity scroll! We already have a kind of trigger that when a new DOM content added we will reload our js functionalities. But we will make sure about it inside infinity scroll!

the “Cache enabler” plugin support has been added on V4.6.6

Hey @lfedele

Try to use following custom css code:

.wpulike .wp_ulike_general_class {
  flex-direction: row-reverse;
}

@biobolt This vulnerability has been fixed in version 4.6.5.

Hey @samsam113
Thanks for your report. I found a solution to prevent this issue. After final tests, we will release it in the next few days.
https://github.com/Alimir/wp-ulike/issues/87

Hey @pronamic_reuel
Thanks, Do you have any plan to replace XML with JSON?

@damarowerbeagentur Can you please let me know what your situation is?
everything is ok now?
Do you face any other issues?

Hey @damarowerbeagentur
Probably there is an error inside another plugin which makes this problem! Can you check your error logs? and please share an online link to check it out.