polarracing

Run two loops.
1. A loop colleting the sticky elements with parameter

"sticky="true"

and sort order “date”.
2. A loop with the same parameters but

sticke="false"

If you need to stick to 12 posts, you can count the number of post delivered by your first loop and use that value to limit the 2. loop to show the rest of the posts.

Hope that helps.

• This reply was modified 4 years, 5 months ago by polarracing.

Oh, and you can use <p class="">

This preserves the <p> even in DIVI code modules.

To detail it a bit more:

Old code:

<div class="evr-close">
  <a href="#close">close</a>
</div>

New code:

<a href="#close" class="evr-close">close</a>

is altered to:

<a href="#close" clas="evr-close" data-et-has-event-already=”true”>close</a>

This causes my own close button then to be inactive.

When I disable the “close-button” option in the popup setup – the close button and my own button is gone.

Two potential solutions:

1. allow more than one instance of the close link & class
2. add a second # & class combination for an own close button

• This reply was modified 4 years, 5 months ago by polarracing.
• This reply was modified 4 years, 5 months ago by polarracing.

No it seems the javascript has changed.

Now I need to a link with classes previously I could place a link within a div with the needed classes.

Also my own link is altered with “data-et-has-event-already=”true” during the page is loading. this seems to be a counter of the instances for your javascript listerners.

Also I found out, that my button disappears when I disable the close button option for the popup.

So it seems its the new script causing the issue.

That one fixed the issue for me.

.da-close-wrap {
overflow: hidden;
}

The [related] does not let you define the post you are searching in – just the field.

That said I would try following approach.

1. In the current code I would run the [related] to get the ID of the first relation.
2. Then pass this to the meta-shortcode and run a loop there to get the right post
3. Run related in the loop within the meta shortcode to return my result.

• This reply was modified 4 years, 5 months ago by polarracing.

Have you tried to use a Metashortcode. So you could run one [relation] within you code – pass the id of the post to the metashortcode and get back the final title from there.

I never tried this for [related] but in other cases I was able to break some limits I had using this method.

• This reply was modified 4 years, 5 months ago by polarracing.
• This reply was modified 4 years, 5 months ago by polarracing.

Hi,

Update 2:

I nailed the issue further down to the “Enhanced Media Library” plugin. If this plugin is active – the issue appears – if not I can create the translations as needed.

So now I need to change the plugin I use for managing my media.

Hi,

first update.

After looking into the db it shows that there is a datarecord present in the term_taxonomy table when two translations are made. Creating the third deletes the record in the term_taxonomy db.

When the relationship is created manually, its possible to edit the translations and save them. All relations are keept.

Oh, and btw. – All other post types work fine – its just the attachements.

• This reply was modified 4 years, 5 months ago by polarracing.
• This reply was modified 4 years, 5 months ago by polarracing.

Because you are looping for all elements and then limit to those with checkbox.
You need to add the checkbox field to the loop to get the six elements you like to get.

Having the same issue with DIVI. Using <div> as workaround.

Hi,

the issue is gone. You can close the topic.

Thanks

Thanks so much for the fast reply. Will keep you updated.

Hi,

sorry for the late answer.

1. I use PHP 7.3.2 – so PHP version should be no issue
2. No, sorry but I removed your plugin and implemented FontAwesome locally. So I have currently no access to the previous dashboard. But the dashboard was just ending with the error message I posted – so nothing spectacular to see there.
3. As far as I remember it was the icon short-code.

Hope that helps.

Quick resolve for this issue:

Delete plugin folder and replace with previous version and post editor is back.