Azragh

You are not alone, look at the latest entries in the forum. Honestly, I can’t understand how you can be bombarded with one and the same message for over 2 days but simply not make a statement. Why are other questions being answered? Does that mean a solution is not being worked on?

I appreciate the work of @takayukister, but I simply don’t understand how the community can be left in ignorance about such obvious problems. I would even settle for “that’s just the way it is from now on”, but I want an answer. Do I have to carry out over 200 updates or not?

I haven’t found a statement about the error message in v 5.7 yet either, same points there.

Same error here.

If you don’t have access to the CSS files of the theme/child theme, you could add a wrapper div with an inline style in the form template.

Just add <div style="color:#fff"> at the beginning of the form and </div> at the end. =)

Just another weird thing in the Gutenberg world I suppose. Great plugin though – I’ve almost given up trying to find a solution to configure the editor for all users at once, thanks for that!

Just remove the codes on the “integration” settings page.

I only get these:

Uncaught TypeError: Cannot read properties of undefined (reading 'then')
    at 16 (gbm.js?ver=1.2.2:1:1102)
    at r (gbm.js?ver=1.2.2:1:110)
    at gbm.js?ver=1.2.2:1:902
    at gbm.js?ver=1.2.2:1:912

Just noticed this too. Any updates on this?

Hi @fahidjavid!

Thanks, this is great! I do like the addition of the default rating too, really helps in maintaining a consistent layout on archive pages and engaging people to rate.

Good work! ??

No problem, we are all very busy these days. ??

I meanwhile could solve my issues by applying ′font-size: 0;′ to the wrapper in specific areas, but ′display: none;′ still would be better in terms of SEO & code quality. =)

Thanks for looking at it!

I use WP Featherlight on over 100 Websites and I have no problems at all. I bet you didn’t set the link to the media file or another plugin disturbs the functionality somehow.

The “Doesn’t work for others either” part is obsolete as the guy didn’t wrap the image with a link tag pointing to the image.

As another user has replied to exactly the same question on an earlier version:

“Just because the developer has not (yet) updated the “Tested up to” version number in the readme.txt, does not automatically mean the plugin stops working with later WordPress versions and you need to find an alternative.

Most plugins that predominantly rely on third-party JS and CSS code and not core WordPress functions are unlikely to be affected by minor WordPress updates (even major ones in most cases).”

WP-Featherlight only scans your content for image links and attributes, therefore the WP version doesn’t matter at all.

I just figured out why it crashes on 8.0.

Open the file dcwp_jquery_accordion.php in the plugin folder. Go to line 63 and comment out or remove

add_action('widgets_init', create_function('', 'return register_widget("dc_jqaccordion_widget");'));

Replace the code with

function your_function_name_to_register() {
	return register_widget("dc_jqaccordion_widget");
}
add_action( 'widgets_init', 'your_function_name_to_register');

Reason for the error is the create_function part. Just create a “real” function before and it works. Usually I would say don’t forget to bump up the plugin version to prevent changes on updates but on this one.. yeah you know.

• This reply was modified 2 years, 2 months ago by Azragh.

Interesting. When I access the WP installation directly from my local IP it seems to work. Usually I use Xampp in combination with Prepros, which compiles everything and gives me live updates on https://localhost:8848/xxx. If i just use https://localhost/xxx it doesn’t work either – could there be an issue in getting the right base URL or something?

I just ran into this issue again – completely forgot that I posted here already. This time I have all the message strings in curly braces (in default language german) and they do appear in string translations, but don’t apply. I also tried with the original english strings (with and without curly braces) but it just didn’t work.

The fix above doesn’t seem to work too – copied the customized plugin from eisenbart.ch but no luck. Maybe cause the second language is french and not english this time?

Update: In my strings file I have:

{One or more fields have an error. Please check and try again.}

Translated to german with:

Ein oder mehrere Felder weisen einen Fehler auf. Bitte korrigieren Sie diese.

But the text that appears on front is the default german one:

Ein oder mehrere Felder weisen einen Fehler auf. Bitte überprüfe das und versuche es erneut.

? But when I use The same german string in the messages setting as in the string translation, it takes the custom one, not the default..

• This reply was modified 2 years, 2 months ago by Azragh.
• This reply was modified 2 years, 2 months ago by Azragh.

@w-sky “Alle %” was special to my case – at the same location in your error message I can see an empty ′sprintf()′, maybe an empty string which needs a parameter (%s) in a translation file is causing the error?