All set, please close the ticket.

PS – everybody else reading this because something is busted with your site, turn off all your plugins and see if it’s still happening. It’s the WordPress equivalent of the “turn it off / turn it back on” troubleshooting tactic with computers.
If that fixes things, turn them back on one by one and test till you find the problem again.
It’s the first step we sometimes forget, and it’s probably the first question Rikard and his team are going to ask when they reply to your help request.

Hi @Victoria,
When you say “Did you try adding it?” do you mean “Did you try commenting it out?” then the answer is yes.
See here:

Quoting:

We are going to update the file soon however if warning is visible on your website, please feel free to comment out or delete the code above.

Please let me know if I’ve misunderstood something.
Thank you!

Update: I found more forum posts on this topic and replaced the avia_gutenberg CSS file, but it didn’t work.
Here is the forum post addressing this issue specifically:
https://kriesi.at/support/topic/shortcodes-window-after-updating-to-wordpress-5-4/

…and here’s the forum post addressing the “Deprecated: contextual_help is deprecated since version 3.3.0!” error message we’re all seeing:
Error code after wordpress update post
Unfortunately, commenting out that code didn’t help for me either.

• This reply was modified 4 years, 7 months ago by steed. Reason: Making the link prettier

Hi Rikard,

I think you might have looked in on my issue when I was working on another one and had removed all the QuickCSS as an experiment. Sorry about that!

I have changed several things in the last few days, so I’d like to ask you to take yet another quick look, and I have a question about your previous suggestions.
You first said to try this:

.template-single-blog .content {
  padding-top: 0 !important;
}

…then later you said “Please try this as well:”

.template-single-blog .content {
    padding-top: 10px;
}

I am unclear whether you want me to replace the first quickCSS with the second one, or add include second one in addition to the first.

I want to reduce the height of the white space at the top of my pages — product pages and regular pages — (see the green area in my screenshot above) by half.

Thank you.

Hi again,
Your second QuickCSS looks almost the same as the first one, and neither are working on the page I’m testing on:

I must be missing something. Thanks for helping me understand.

Hi Victoria,

Whoops! I’m so sorry. Try this shorter one.

Hi Mike,
Thank you for your help. I tried to write you back around year end, but you guys were closed for the holidays (which is great! – welcome back).
In the meantime, I’ve made a ton of changes (ditched WooCommerce for EasyCart, got that entirely configured, now am switching back – argh.)
At this point, the table is indeed wider, but that’s true whether or not your code is in General Styling > Quick CSS.
Here’s what I’m wanting it to look like ideally –

…specifically, with the first column narrower, and the second one to be wider to accommodate longer text.

Thanks for your previous help, and in advance.

• This reply was modified 4 years, 10 months ago by steed. Reason: had the wrong password in there

Thank you, @guenni007, for your quick response.
Regarding manual layout: Really what I need is help finding a way to define margins in text blocks appearing in content elements?

Before starting this topic, one of the things I tried without success was the Grid Layout of blog posts (as you suggested).
But similar to the Portfolio Item >> Books idea you helped me explore in another thread, Grid Layout doesn’t offer the control I want over which content is displayed. I need the cover image, the book title, subtitle, and author name. Grid Layout (like Portfolio Item) at most allows for a sometimes-cropped feature image, title, and excerpt. Example screenshot – top of page is grid layout, bottom is my manual layout. (Extra problem: all the entries with no image and lots of text shouldn’t be there, as they’re in categories not specified)
Here’s a very specific image of what I’m trying to achieve:

If it’s not possible to restrict the width of the text, I guess an alternative would be to make the cover image wide (and hence taller) enough to give the same appearance of alignment. I’ll play with that for a while.

Whoops – I didn’t see your request before posting my “Final Note.”
My functions.php was this:

<?php
/*
* Add your own functions here. You can also copy some of the theme functions into this file. 
* WordPress will use those functions instead of the original functions then.
*/
/* CHANGES 'PORTFOLIO' POST TYPE TO 'BOOK TITLES'*/
// portfolio args
/**** Portfolio umbenennen im Dashboard ****/
add_action( 'init', 'unregister_taxonomy_for_custom_label', 30);
function unregister_taxonomy_for_custom_label(){
  global $wp_taxonomies;
  $taxonomy = 'portfolio_entries';
  if ( taxonomy_exists( $taxonomy))
    unset( $wp_taxonomies[$taxonomy]);
}

// portfolio args
add_action( 'init', 'init_reg_portfolio', 50 );
function init_reg_portfolio() {
  add_filter('avf_portfolio_cpt_args', 'avf_portfolio_cpt_args_mod', 50, 1);

  $tax_args = array(
    "hierarchical" => true,
    "label" => "Books Categories",
    "singular_label" => "Books Category",
    "rewrite" => array('slug'=>_x($permalinks['portfolio_entries_taxonomy_base'],'URL slug','avia_framework'), 'with_front'=>true),
    "query_var" => true
  );

  $avia_config['custom_taxonomy']['portfolio']['portfolio_entries']['args'] = $tax_args;

  register_taxonomy("portfolio_entries", array("portfolio"), $tax_args);
}

add_action( 'after_setup_theme', 'init_reg_portfolio' );

function avf_portfolio_cpt_args_mod($args) {
  $labels = array(
    'name' => _x('Books', 'post type general name','avia_framework'),
    'singular_name' => _x('Books Entry', 'post type singular name','avia_framework'),
    'add_new' => _x('Add New', 'book','avia_framework'),
    'add_new_item' => __('Add New Book Entry','avia_framework'),
    'edit_item' => __('Edit Book Entry','avia_framework'),
    'new_item' => __('New Book Entry','avia_framework'),
    'view_item' => __('View Book Entry','avia_framework'),
    'search_items' => __('Search Book Entries','avia_framework'),
    'not_found' =>  __('No Book Entries found','avia_framework'),
    'not_found_in_trash' => __('No Book Entries found in Trash','avia_framework'),
    'parent_item_colon' => ''
  );

  $args['labels'] = $labels;
  return $args;
}
/*** Ende ****/