get_the_excerpt doesn’t work with default items but works with my customs post types

the excerpt function not work in my custom post template using WordPress default posts in the query loop, but they work fine with custom post type.

I enabled the display of excerpt by checking the "excerpt" option in the post options fields.

I also added "add_post_type_support(‘page’ ‘excerpt’)" in my function.php file but it doesn’t working.

I suspect a problem coming from the database because the excerpts are displayed when I test the website locally with Xampp.

Here is a snippet of the code used in my page template:

<div class="container">                      <div class="row">                         <div class="col-lg-9 col-mg-9 mp-blog" style="padding-right: 24px;">                                                 <div class="row">                                  <?php                                 $  paged = (get_query_var('paged')) ? get_query_var('paged') : 1;                                  $  args = array(                                   'post_type'=>'post', // Your post type name                                   'posts_per_page' => 6,                                   'cat' => 26,                                   'paged' => $  paged,                                 );                                                                  $  loop = new WP_Query( $  args );                         if ( $  loop->have_posts() ) {                             while ( $  loop->have_posts() ) : $  loop->the_post();?>                        <?php the_excerpt();?>                        <?php endwhile;                              $  total_pages = $  loop->max_num_pages;      if ($  total_pages > 1){          $  current_page = max(1, get_query_var('paged'));     ?>     <div class="custom_pagination">        <?php         echo paginate_links(array(             'base' => get_pagenum_link(1) . '%_%',             'format' => '/page/%#%',             'current' => $  current_page,             'total' => $  total_pages,             'prev_text'    => __('« précédent'),             'next_text'    => __('suivant »'),         ));?>     </div>     <?php }     } wp_reset_postdata();?>                     </div>                 </div><!-------------- end of col-8 ------------------>               <div class="col-lg-3 col-mg-3" style="padding: 0;">                   <div id="tching" class="blog_right_sidebar" style="padding: 0 15px;">                       <?php get_sidebar(); ?>                   </div>               </div>             </div>          </div> 

How does a Battle Master’s Parry work with multiple damage types? [duplicate]

Suppose an attack does 5 piercing and 5 poison damage (or 5 slashing and 5 fire, etc.) and the player parries the attack, and rolls to reduce 6 points of damage. Which type of damage is reduced first? Would the answer be different if it were 9 weapon damage and 1 elemental, or vice versa?

Parry:

When another creature damages you with a melee attack, you can use your reaction and expend one superiority die to reduce the damage by the number you roll on your superiority die + your Dexterity modifier.

This matters if, for example, the character has resistance to one of the damage types.

The kindest interpretation (and one that does make some “sense”) would be that it reduces weapon damage first, and if it reduces the weapon damage to zero, none of the additional damage is done either, but that seems over powered. Unless someone can unambiguously point me to rules that support this interpretation, I prefer an interpretation where the total damage reduced is as rolled.

Does the optimized column order for a PostgreSQL table always have variable length types at the end?

There’s a popular and seemingly authoritative blog post called On Rocks and Sand on how to optimize PostgreSQL tables for size to eliminate internal padding by re-ordering their column length. They explain how variable-length types incur some extra padding if they’re not at the end of the table:

This means we can chain variable length columns all day long without introducing padding except at the right boundary. Consequently, we can deduce that variable length columns introduce no bloat so long as they’re at the end of a column listing.

And at the end of the post, to summarize:

Sort the columns by their type length as defined in pg_type.

There’s a library that integrates with Ruby’s ActiveRecord to automatically re-order columns to reduce padding called pg_column_byte_packer. You can see the README in that repo cites the above blog post and in general does the same thing that the blog post describes.

However, the pg_column_byte_packer does not return results consistent with the blog post it cites. The blog post pulls from from PostgreSQL’s internal pg_type.typelen which puts variable-length columns always at the end via an alignment of -1. pg_column_byte_packer gives them an alignment of 3.

pg_column_byte_packer has an explanatory comment:

    # These types generally have an alignment of 4 (as designated by pg_type     # having a typalign value of 'i', but they're special in that small values     # have an optimized storage layout. Beyond the optimized storage layout, though,     # these small values also are not required to respect the alignment the type     # would otherwise have. Specifically, values with a size of at most 127 bytes     # aren't aligned. That 127 byte cap, however, includes an overhead byte to store     # the length, and so in reality the max is 126 bytes. Interestingly TOASTable     # values are also treated that way, but we don't have a good way of knowing which     # values those will be.     #     # See: `fill_val()` in src/backend/access/common/heaptuple.c (in the conditional     # `else if (att->attlen == -1)` branch.     #     # When no limit modifier has been applied we don't have a good heuristic for     # determining which columns are likely to be long or short, so we currently     # just slot them all after the columns we believe will always be long. 

The comment appears to be not wrong as text columns do have a pg_type.typalign of 4 but they’ve also got a pg_type.typlen of -1 which the blog post argues gets the most optimal packing when at the end of the table.

So in the case of a table that has a four byte alignment column, a text column, and a two byte alignment column, pg_column_byte_packer will put the text columns right in between the two. They’ve even got a unit test to assert that this always happens.

My question here is: what order of columns actually packs for minimal space? The comment from pg_column_byte_packer appears to be not wrong as text columns do have a pg_type.typalign of 4, but they’ve also got a pg_type.typlen of -1.

What approaches are there to blending multiple terrain types? [duplicate]

So for my university final assignment I’m doing a procedural world generator in unity. The idea is that different types of terrain are generated such as ocean, swamp, hills etc. I have the different biomes generating as chunks with different colours at the moment and the next step for me is to smoothly transition between them rather than drop off from one terrain type to another.

To do this I’m going to need to adjust the heightmap so that the edges join together rather than having gaps between them. The noise is continuous so biomes of the same type connect seamlessly. However with different biomes the height generated from any given noise is different, that way my mountains stick up without my ocean chunks being weird shapes. The result is like I said earlier, there are seams between my chunks that I need to stitch.

So my real question is what approaches are there currently to blend from one height map to another?

What mechanical implications exist when allowing duplicate stronghold types in a castle?

Matt Colville’s supplement Strongholds & Followers details, among other things, rules for building optional strongholds and castles, with castles being complexes of multiple strongholds.

The strongholds are divided into four broad types: keeps, towers, temples, and establishments. A stronghold (of any variety) can be controlled by only one PC at a time, and can only offer its most direct benefits to that character. On page 11 of Strongholds & Followers the rules state that castles cannot contain more than one of each stronghold type.

A castle cannot contain multiple of the same type of stronghold. If you build a castle with two towers, for instance, only one of them grants the benefits of spell research. Also, a stronghold’s benefit only applies to one character at a time. (Strongholds & Followers, page 11)

I am running a game using these rules in which two PCs (a Wizard and a Sorcerer) will almost certainly want to build a tower each. Even if they don’t, the party has no use for a temple (or variant on a temple, like a Druid’s Grove). With four players that means that unless there is at least one duplicate stronghold type, at least one player will be left out. This is easy enough to just overrule (I plan on allowing two towers), but I’m curious about why the restriction on duplicates exists. I have not found anything in the book itself.

Is there a mechanical implication to duplicating stronghold types within a single castle?

What is a women’s blouse and what are its types?

Blouse is the English word for blouse and refers to the loose, relatively long dress that is commonly worn by miners, workers, peasants, women, and children. In the past, its appearance was such that it was fastened around the waist by a belt or a belt, and they felt comfortable when wearing it. This causes the belt to loosen and sag in the shoulders and upper torso. As you know, blouses often include women’s clothing, and it has sometimes been seen that this clothing is also worn by the military and men.

In the case of men’s clothing, we must say that the T-shirt is the same as the blouse, but its material is thinner. T-shirts are produced in the model of seven-collar and round models, and men can use them in spring and summer. The collar of women’s blouses also includes different models, from narrow to wide collars.

More about different types of collar models in women’s blouses: Collar seven: This model of collar is very popular in women’s clothing, its appearance is the same as the number seven, and you can use blouses that have this collar at family parties. Round collar: This collar, like the previous model, is widely used in women’s clothing. Blouses with this type of collar can be used at both formal and informal parties. Loose collar: Few women are not interested in this type of collar. Its appearance has a loose and hanging shape that makes the charm of your style multiplied. A collared blouse is one of the dresses that most women wear to formal parties with trousers or short skirts and shine in the house. Sweetheart collar: This model of collar is not very widely used and is more visible in old women’s clothes. It is a bit difficult to describe the appearance of this collar, https://www.banimode.com/

Counter for selected dofollow / nofollow link types and titles

Hello guys! of GSA SER
I would like to ask for 2 requests to implement in GSA SER as I see that feature is not yet integrated. It would be a great help visually.
1. Know how many Dofollow links exist in my verified records, see image:

You can only see dofollow sites with an X, but you cannot see the “exact” amount quickly. It would be great to add at the bottom how many follow / nofollow links exist.
2. Creation of titles.
I have observed that there is also not a counter for selected titles visually. View image:

It would be great to have a counter at the bottom every time a title is selected, to know how many titles I am selecting.

What Redirect Types (301,302,Meta,Refresh..) count as DoFollow?

To be more accurate, I would like to set the DoFollow Flag for the links that SER builds. In latest update (v15.04) it can also detect what type it is (301, 302, 307, META, Refresh, Java,…) but I have a real problem telling what will count as DoFollow.
The 301 Redirect is obviously a DoFollow link and I think the Refresh one should also considered to be one. But what about the Rest? Any input is welcome here.