David Frank

Actually, the problem with get_post_custom might just be that it doesn’t take url in content into account as well. Not sure this is standard or not…

https://codex.www.ads-software.com/Function_Reference/get_post_custom

I have collected 1000+ surveys and no problem reported so far, I think wpgform is working as expected with the new google form. I am using following setup:

[gform form=’https://form-link/’ confirm=’https://confirm/’ legal=’off’ br=’on’ email=’off’ style=’redirect’]

so honestly I am not using a lot of built-in features… but the basis seem solid.

Hi there mike, is the workaround still needed at this point? think google has removed the “create legacy form” from spreadsheets options.

Also I am able to get the new form to show up in latest plugin release, maybe I need to test further to see where it breaks.

Or you can try the default media library ( go to /wp-admin/upload.php ), which allow you to batch delete. We currently don’t offer mass delete in editing interface because it’s not our frequent tasks.

You cannot change the alt text of an image by editing alt text of such image in media library. Once the text is inserted into the post, it’s a part of the post content, just like any single image you inserted.

You may use gallery shortcode (WP built-in) if your image alt text/title text need frequent update.

I think the best idea would be to try out a local install without plugin, to see if it’s flash plugin or browser related issue.

FII plugin does nothing to the upload process, I highly doubt it’s plugin related issue. (You are still using the default core wordpress upload, note that WP3.5 made significant change on their upload module)

We don’t have that option just yet, you can of course edit the numbering in script, between line 194-202

var num_count = 0;
                $('.media-item').each(function(e) {
                    num_count++;
                    if(typeof massedit[0] !== "undefined" && massedit[0].length > 0) {
                        $(this).find('.post_title .field input').val(massedit[0] + " (" + num_count + ")");
                    }
                    if(typeof massedit[1] !== "undefined" && massedit[1].length > 0) {
                        $(this).find('.image_alt .field input').val(massedit[1] + " (" + num_count + ")");
                    }

change it to something like

$('.media-item').each(function(e) {
                    if(typeof massedit[0] !== "undefined" && massedit[0].length > 0) {
                        $(this).find('.post_title .field input').val(massedit[0]);
                    }
                    if(typeof massedit[1] !== "undefined" && massedit[1].length > 0) {
                        $(this).find('.image_alt .field input').val(massedit[1]);
                    }

I should note that it’s accessibility best practice to keep the title and alt text unique and descriptive, which is why we went with the numbering.

This is a WordPress 3.5 core change, see this ticket: https://core.trac.www.ads-software.com/ticket/18984

Basically, WP3.5 will no longer add title to image (to accomandate assistive software), this is the behaviour even when you use default “Add Media” button.

We are not going to overwrite this WP behaviour.

You should be using the Faster Image Insert metabox (below main editor), not the default media button (we left it there so you can still use wordpress built-in function).

If you cannot find the metabox below editor, go to top-right of the screen and find “screen options”, make sure “Faster Insert” checkbox is ticked.

If there are problems within the metabox, post some screenshots to illustrate the issue and let us know your steps of reproduction.

hopefully by now you notice the customn post type setting in the FII setting page. if by “custom admin” you mean third-party admin with editor, then FII probably does not support it.

should be fixed in 2.4.0, finally. Thanks George.

*resolved

no support for this so far, will consider using date() to format string in next release..

Mark this so no one run into it again ??

should be fixed in 2.4.0, thanks for reporting