HappyKite

If you are unsatisfied with my plugin, then you can either just disable it on the Plugin page, Delete it from the plugin page (you will see both ‘Deactivate’ and ‘Delete’ under the plugin name in the list), Or if you have access to FTP delete the folder.

The first 2 are the more recommended options however.

Might I ask if you had any issues with the plugin that I can help with?

Hi b.herrero,

I’m not sure if you fixed this your end of not, but I also encountered this issue.

I have been able to fix it by adding the $post_id for the current post into the get_field function.

<?php $your_field = get_field('custom_field_name'); ?>

The above should work for the current post, and does seem to for everything except WYSIWYG fields, I need to add in the current post ID. In my case it was a Category so I made the changes below and it worked fine again.

<?php global $wp_query;
$current_id = $wp_query->get_queried_object();
$your_field = get_field('custom_field_name', $current_id); ?>

Hope this helps!

Thanks,
HappyKite

Hello PrismaPhonic,

Sorry it took me a little while to get back to you, I was on holiday.

Your problem sounds to me like it was probably caused by a Caching issue. Flushing your cache would have fixed this.

Thank you for using my plugin, sorry you had some issues with it.

Hello PrismaPhonic

It is impossible for a WordPress Plugin to Reactivate itself.
This sounds like a Caching issue to me.

I’m sorry you didn’t get on with my plugin.

Hello,

From the sounds of it you are using the HTML Block and not the Custom Block.

Please change the radio button list to be Custom Block and you will then be able to customise the page itself.

The HTML Block is only for if you have a pre-built flat HTML page ready.

If you are having any other issues please feel free to let me know and I’ll take a look.

Thanks

Hello,

Version 1.9 has just been uploaded. This will fix a known Javascript issue.
I’ll mark this topic as resolved now.

Many Thanks!

Hello,

Thank you for calling this to my attention, I have fixed this issue now.
There is a new update, please upgrade your version and let me know if you encounter any more issues.

Thanks!