No – please don’t.
I only come here occasionally and give my opinion on topics, but I have enough projects of my own at the moment – so I don’t want to take responsibility for other people’s projects.

for so few posts within a category, I would rather install a plugin that supports a custom post order to quickly find a solution. There you can customize the order of the posts by drag and drop.
Such a plugin would be, for example, Simple Custom Post Order

it is the structure of your titles – they formed with numbers ( your years ) there are options of natural sort order (SORT_NATURAL) etc.
the trouble is if you like to sort by titlel and titles are f.e. A1, A2, A10, B1, B20, B3 etc.
does a sort order could be A1, A10, A2, B1, B3, B20
i do not know if this has influence on that filter ?

Yes – if each post belongs to exactly one category, it should work. But what if the current post belongs to categories A and B – where should it be linked to then?
Multiple categorisation is not unusual.

big problem is – if you have “same category” set via your snippet – and you have portfolios that have more than one cat!

First of all, I would recommend using an SMTP plugin. It makes the e-mail / contact form exchange much more secure.
How does the not sending manifest itself? Do you get an error message from Enfold – or do you not receive any test emails via the contact form?

A lot has happened with providers in terms of security.
So if you do not have an spf record in your DNS settings, your emails may go out but be intercepted by your provider.
I always set spf-record , DKIM and DMARC in the DNS settings.

nicht alle generierten svg’s haben am svg tag width und height Definitionen – sondern haben ausschließlich viewBox Informationen.
Diese svg in der Media-Library werden mit weite und höhe von 0x0 geführt.
Eingesetzt als z.B. Image Element benötigen also um im Frontend zu erscheinen eine absolute Weite ( relative Werte genügen nicht – 80% etc. )

Daher füge mal in dein Quick css ein:

#wrap_all #main img[src*="svg"] {
  width: 1500px;
}

solltest du – wie ich oft ein Snippet in der functions.php haben, das solche img in inline-svg wandelt, mußt du auch diese mit berücksichtigen.

#wrap_all #main svg {
  width: 1500px;
}

die Größe wird letztendlich dann vom umgebenden Parent Container bestimmt.

and if i do want to have that on all single posts – i can use ?

add_filter( 'avf_post_ingnore_featured_image_link', '__return_true' );

and if i want to use an array of post id’s – is that the correct way?

function custom_avf_post_ingnore_featured_image_link( $ignore_image_links = false, array $current_post = [] ){
  //  e.g. available variables
  global $avia_config, $post_loop_count;

  //  e.g. remove link for posts:
  $postIDs = [ 36011, 45175 ];

  $ignore_image_links = in_array( $current_post['the_id'], $postIDs ) ? true : false;
  return $ignore_image_links;
}
add_filter( 'avf_post_ingnore_featured_image_link', 'custom_avf_post_ingnore_featured_image_link', 10, 2 );

many thanks !

you can edit your post by pasting the code snippet into code tags! (please copy and paste the code from your template again).
It’s hard to check the snippet – when many letters are converted by Board Soft.

One thing might be:

Since WooCommerce 3, the hook woocommerce_checkout_update_order_meta is outdated and replaced by woocommerce_checkout_create_order

PS: Isn’t that more a question for the Woocommerce support team?

if you like to synchronize it with the other widget titles:

#top #wrap_all .all_colors .sidebar .tribe-events h2 {
  font-family: var(--enfold-font-family-heading);
  font-size: var(--enfold-font-size-theme-h3);
  color: var(--enfold-main-color-heading);
  border-color: var(--enfold-main-color-border);
  font-weight: 600 !important;
  letter-spacing: 1px;
  border-style: solid;
  border-width: 1px !important;
  padding: 10px 0;
  border-left: none;
  border-right: none;
  margin-bottom: 15px;
}

if you have set in quick css ( or advanced styling) different attributes than the default ones (f.e. font-size) then you have to adjust it to your needs.

Yes – but on seo reasons it might be better to Not have a link here instead of hampering the Event.

And now the profi tip:
1( Go to Google Font – choose your font – download it. You will get a ttf font.
2) Go to: Transfonter
choose svg as font:

download the converted font – unzip and pull out the svg you get.
3) Go to fontello – drag & drop that svg to the “custom icons” field.
4) choose your selected icons – name it and download that zip file –
5) upload that to Enfold – Import/Export/…. Iconfont Manager
;)

see here – done with montserrat-regualar:

download here: https://webers-testseite.de/montserrat-numbers.zip

PS: sometimes it might be neccessary to adjust the size of those font-icons.
eg:

html body [data-av_iconfont="montserrat-numbers"]::before {
  font-family: 'montserrat-numbers';
  position: absolute;
  left: 50%;
  top: 50%;
  font-size: 2em;
  transform: translate(-50%, -50%);
}

see: https://webers-testseite.de/montserrat-numbers-2/

and – tip: you can combine more than one font-family in that upload.

By the way – this is not meant to be a solution! – Maybe Günter can implement a filter on that or ;) insert an option on the Single Post Style. ( with lightbox link / without link )

:lol: sorry for us-english ( behavior – behaviour)

yes you are right – the snippet turns the sequence to first image then titel.
Besides the css of setting only the pointer-events to none.:

#top .template-single-blog main .big-preview.single-big a {
  pointer-events: none !important;
}

there must be a hampering method to avoid generation of that link

can you show me your page – and the concerning text to style.
first to know – commata on css rules at selectors will combine different selectors with the same setting.
the asterisk ( * ) is a known as “CSS universal selectors” and is a wildcard for everything.

That : `#ls-global div .avia-layerslider .ls-wp -container .ls-layer > * means every child inside that selector will have that line-height.
But thats my question the first and second line there is no following element behind the “>” – on my opinion this makes no sense.
First will give a parsing error – second line will end in an unexpected token ;)

If this code is realy from the developers – Then they didn’t want to that day.