Jorge Rodriguez

I think this is the fix to line 820

$recipe_settings = ( $atts['id'] ? $recipe_settings = Cooked_Recipes::get( esc_attr( $atts['id'] ), true ) : ( !empty($recipe_settings) ? $recipe_settings : false ));

Dear all,

That answered everything I needed. Thank you for your kind advice!

Thank you!

Link to information about how to fix it: https://stackoverflow.com/questions/59158548/array-and-string-offset-access-syntax-with-curly-braces-is-deprecated

The previous messages come from the plugin “Query Monitor” after updating our server’s php version to 7.4

I later on tried to install the plugin on a different site and got it partially working. But not much. Only in the backend. Though not completely. It would allow a bit more editing but most of the metaboxes where only displaying a label, not a box to edit contents.

Also, once activated, the front-end would completely break. Blank screen. Not the backend though. On that particular time, only the plugin was installed, not the LSX theme, it was running a different theme.

• This reply was modified 5 years, 5 months ago by Jorge Rodriguez.

Ok, thanks anyway for your quick response. I will try to modify the plugin and see if I can achieve that which I said.

Cheers ! ??

Ahh ok. Well thanks for the quick reply.

Any chance you could update that in the future to accept shortcodes as output?

Cheers,
Jorge

Thank you very much! ?? That’s amazing!

By the way, I found that when using the Storefront Theme, this CSS helps it display the image and the stars a bit more spaced. Check it out. You might also like it.

div.woo-awaiting-review.woocommerce picture img {
margin-bottom: 20px;
}

div.woo-awaiting-review p.stars {
font-size: 23px;
margin: 15px 0 0 15px !important;
line-height: 23px;
}

I would like to just say something here. I also have interest in this kind of development if possible. The USDA Food Composition Databases offer a free API to request this kind of information.

https://ndb.nal.usda.gov/doc/

Awesome plugin this one. I really like it.

Cheers

Update: my bad. When I wrote the message I had just installed php curl to see if it fixed the issues but still got the same results. I had to restart apache to be able to see it work. Now it works. Also, curl_exec was disabled on our php.ini and was needed for this plugin to work. Now that I see it working I can see this was somehow the issue. Sorry for the false alarm.

It turns out it wasn’t your plugin, it was my cache plugin concatenating scripts. When I saw this I thought it came from your CSS but now that I see that even if your plugin is deactivated it will still happen due to another plugin probably.

This will be marked as resolved. Sorry. False alarm.

Dear Sehgal,

thank you for your message. It was very helpful, and you were right. With a bit of jQuery could be done. I will add this information just in case it could be useful for somebody else:

I added these 2 lines of code to the end of the file “history.js”(just before the last “});” and it worked.

$(“.events”).css(“transform”, “translateX(226px)”);
$(‘.events > ol:nth-child(1) > li:nth-child(3) > a:nth-child(1)’)[0].click();

Cheers

• This reply was modified 6 years, 8 months ago by Jorge Rodriguez.

Dear Gioni,

Sorry for replaying so late. I hadn’t seen your reply yet.

Lately, I have been trying a plugin called Risk List:

https://risklist.co.uk/
https://www.ads-software.com/plugins/risk-list/

It’s not yet very popular, and that is a pity, because it is very good.

Imagine if one could implement your static code inspection analysis and then see a risk heat map of your own plugins. That would be just amazing. Wouldn’t you think?

The errors I found in the first comment, might be related to undeclared variables $red, $green and $yellow, but I haven’t really managed to fix them by just declaring them.

Searching on the internet I saw that the errors appear probably because these variables are expected to be arrays.