EXED internet

Hi,

I had to change my patch, since hidden inputs are not the only fields without a html5 placeholder area.
https://html.spec.whatwg.org/multipage/forms.html#the-input-element

I’ve tried to find another solution (found some solutions using “‘placeholder’ in element”) but they didn’t work.

So for the new patch:

--- a/gravity-forms-auto-placeholders/gravity-forms-auto-placeholders.php
+++ b/gravity-forms-auto-placeholders/gravity-forms-auto-placeholders.php
@@ -86,6 +86,9 @@ jQuery(document).ready(function($){
                }
        ?>
        $.each($('.<?php echo $gfap_class; ?> input, .<?php echo $gfap_class; ?> textarea'), function () {
+               if (type == 'hidden' || type == 'file' || type == 'radio' || type == 'checkbox' || type == 'color' || type == 'date' || type == 'range' || type == 'month' || type == 'week' || type == 'time' || type == 'datetime-local') {
+                       return;
+               }
+               if (!this.id) {
+                       return;
+               }
                var gfapId = this.id;
                var gfapLabel = $('label[for=' + gfapId + ']');
                $(gfapLabel).hide();

closed because of duplicate (one post is more than enough flyingkites)

closed because of duplicate (one post is more than enough flyingkites)

Hi,

based on the solution mentioned on https://digwp.com/2010/04/call-widget-with-shortcode/ , you can use the code below.

function wysiwyg_widget( $atts ) {

    global $wp_widget_factory;

    extract( shortcode_atts( array(
        'widget_name' => "WYSIWYG_Widgets_Widget",
		'id' => null,
    ), $atts ) );

    if ( ! is_a( $wp_widget_factory->widgets[ $widget_name ], 'WP_Widget' ) ) :
        $wp_class = 'WP_Widget_' . ucwords( strtolower( $class ) );

        if ( ! is_a ( $wp_widget_factory->widgets[ $wp_class ], 'WP_Widget' ) ) :
            return '<p>' .sprintf( __( "%s: Widget class not found. Make sure this widget exists and the class name is correct" ), '<strong>' . $class . '</strong>' ) . '</p>';
        else:
            $class = $wp_class;
        endif;
    endif;

	if ( ! is_null( $id ) ) {
		$instance['wysiwyg-widget-id'] = $id;
	}

    ob_start();
    the_widget( $widget_name, $instance, array(
		'widget_id'=>'arbitrary-instance-'.$id,
        'before_widget' => '',
        'after_widget' => '',
        'before_title' => '',
        'after_title' => ''
    ) );
    $output = ob_get_contents();
    ob_end_clean();
    return $output;

}
add_shortcode( 'wysiwyg_widget','wysiwyg_widget' );

And then you can use either
[wysiwyg_widget id="<ID>"]
or even
<?php echo do_shortcode('[wysiwyg_widget id="<ID>"]'); ?>

Hello Oliredman,

Thank you for your feedback, I will have a look at it and if it is possibly already solved with the updates I’ve made so far.

In the next update I’ll be using a custom post type and thus using default WP methods to handle the request so it shouldn’t cause any problems when the new release comes out, until then I’m sorry for any inconvenience caused.

As for the support of Japanese characters, this is also fixed by using the custom post type ??

In the next release there will be an option for case sensitivity so you can choose if you want only the exact match to show or every match.

Hello Chloe,

I’m glad to hear your positive feedback ??
As for your second suggestion, I’ve already implemented this in the upcoming release so hang tight for that one.

The whole plugin is getting an overhaul, a lot of methods are going to be deprecated and no longer used.
One of those will be ‘add’ because I’ve switched to using a custom post type.

The next update is scheduled for release at the end of August

In the next updated I’ve switched to using a custom post type so that will fix the escaping problem and as for the button, that will be WordPress default.

Hello Mebrahim,

In the upcoming update I’ve switched to using a custom post type so it will work the same as native WordPress and should allow for Arabic script.

You will have to do this manually, in the next update the dictionary will be a custom post type and you can create your own dictionary page template so you can make the page anyway you want it.

I will see if I can fit in an option to not highlight words on the homepage in the upcoming update.

In the next update the dictionary is a custom post type with a WP editor so you will have all the HTML possibilities like a normal post.