bahead

I had the same problem. Until there’s a patch, you can edit media.php in /wp-includes and change line 1566 from:

. do_shortcode( $content ) . '<figcaption class="wp-caption-text" >' . $atts['caption'] . '</figcaption></figure>';

to

. do_shortcode( $content ) . '<figcaption class="wp-caption-text" ' . $style . '>' . $atts['caption'] . '</figcaption></figure>';

By inserting $style in the caption, you are inserting the same max-width variable into figcaption that is used in figure. Previously, figcaption inherited the “width” attribute from figure, but it does not inherit the new “max-width” attribute from figure.

IMO, this was very poor testing on the part of WP developers, who always seem to be in a rush to issue an update without conducting enough QC.

• This reply was modified 6 years, 12 months ago by bahead.

@jeffmatson I think I’ve isolated the problem. If I disable line 30 in settings.php:

wp_register_style( 'slider_ui', '//cdnjs.cloudflare.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.min.css', array(), '1.0' );

the slider appears. I have at least one other plugin already using jquery-ui.min.css. A quick search shows Contact Form 7 is already loading it.

I have not tested the impact of disabling line 30 but I can confirm that doing so displays the slider and allows me to adjust the setting.

• This reply was modified 7 years ago by bahead.

@bharatk Yes, I said the “generated code”. Some other code is hiding the slider. My guess is the maybeHideFrequency function in bundle.js, but why this is happening only for me (apparently) is probably a collision with some other jquery plugin I have installed, which I suspect is what @jeffmatson will suggest. I don’t have the time to troubleshoot, so for the time being I’ll just manually display the slider to make the adjustment. Or I’ll revert to the previous version.

@bharatk Deleting and re-installing the plugin had no effect. The slider option is still not displaying. Same in both Chrome and Firefox. No errors in the console. If I inspect the generated code, I see:

<div class="cmb-row cmb-type-slider cmb2-id-rules-0-heartbeat-control-frequency cmb-repeat-group-field heartbeat_frequency" data-fieldtype="slider" style="display: none;">

If I override this in the console by setting display:block, I can force the slider to appear and adjust the setting.

I just updated to v1.2.2 and I’m now experiencing the missing slider issue. So the fix outlined above doesn’t seem to be the root cause.

Thank goodness I updated to 4.8 on a staging server first. The visual editor on text widgets is buggy as hell. I’m seeing it insert the code for the “Save” button for the widget itself:

`<span style=”border-radius: 2px; text-indent: 20px; width: auto; padding: 0px 4px 0px 0px; text-align: center; font: bold 11px/20px ‘Helvetica Neue’,Helvetica,sans-serif; color: #ffffff; background: #bd081c no-repeat scroll 3px 50% / 14px 14px; position: absolute; opacity: 1; z-index: 8675309; display: none; cursor: pointer;”>Save</span>

Why the devs thought it was a good idea to make a text widget a non-text widget is beyond me. It’s a solution looking for a problem. Introduce a rich text widget as a new option. This was poorly conceived and implemented IMO. On a side note, I find the constant updates to WP problematic. Security updates, yes, but it’s becoming a major task to test any new version as WP becomes more and more complicated. </ rant>

• This reply was modified 7 years, 5 months ago by bahead.

The developer needs to replace deprecated CF7 tags. Here are the changes I made in my version to resolve the errors when WP_DEBUG is enabled.

modules\date.php
Line 32
//$tag = new WPCF7_Shortcode($tag);
$tag = new WPCF7_FormTag($tag);

Line 150
// wpcf7_remove_shortcode(‘date’);
wpcf7_remove_form_tag(‘date’);
Line 151
// wpcf7_remove_shortcode(‘date*’);
wpcf7_remove_form_tag(‘date*’);

modules\datetime.php

Line 26
//$tag = new WPCF7_Shortcode($tag);
$tag = new WPCF7_FormTag($tag);

modules\time.php
Line 27
//$tag = new WPCF7_Shortcode($tag);
$tag = new WPCF7_FormTag($tag);

• This reply was modified 7 years, 9 months ago by bahead.

Yup, that’s it. If I comment out the is_valid_template check in line 230-233 in class-amp-post-template.php, the AMP version renders as expected.

I have the same issue, blank AMP pages, and I’m also running on Windows server.

Thanks! I updated to the current version and copied over gifsicle.exe from the older version. As you suggested, this resolved the issue.

OK, I’ll follow your troubleshooting suggestions when I get a chance and will report back. Thanks for the advice, I am aware of the situation with 2003.

I’ll give it a try on my dev server. Unfortunately, IIS/FastCGI error logging isn’t much help.

Also, the plug-in is incorrectly reporting that the Windows back-up folder is not writable. The plug-in is able to move index.php and wp-config into the folder (which means it’s writable) and the backup is created in the folder (which means it’s writable). The plug-in returns the error message “Database Failed To Backup On ‘February 7, 2015 @ 8:38 pm’. Backup Folder Not Writable.” despite the fact that the backup is created. I can resolve the error message by giving the “Everyone” account modify access to the back-up folder but I’m not about to loosen security just to make the plug-in stop reporting a false message.

I’ll give it a try, thanks for the suggestion.

Khang, I see you’ve now released version 1.3.0. Did you look at this issue at all? I understand if you didn’t, as it’s not a major problem and from the release notes you’ve had more significant improvements to make. But I just thought I’d check.