Archived topic
3.0.2 broke archive layout
4 replies · Started by Craig on December 10, 2020
Hello,
Upgrading theme to 3.0.2 on my sites is breaking one of my archive layout pages. Instead of displaying my custom PODS template, it's displaying the standard excerpt.
Example:
3.0.1 site (working) - https://sjb-school.org/staff
3.0.2 site (broken) - https://spmsjbvermsch-staging.u01g7zk5-liquidwebsites.com/staff
The staff pages use PODS templates to replace the THE_EXCERPT. In 3.0.2, it doesn't appear to be replacing it.
IMPORTANT NOTE: I'm using the following custom template on those staff archive pages.
<?php
/**
* @package GeneratePress
*/
// No direct access, please
if ( ! defined( 'ABSPATH' ) ) exit;
?>
<article id="post-<?php the_ID(); ?>" <?php post_class(); ?> <?php generate_article_schema( 'CreativeWork' ); ?>>
<div class="inside-article">
<?php do_action( 'generate_before_content' ); ?>
<header class="entry-header">
<?php do_action( 'generate_before_entry_title' ); ?>
<?php the_title( sprintf( '<h2 class="entry-title" itemprop="headline"><a href="%s" rel="bookmark">', esc_url( get_permalink() ) ), '</a></h2>' ); ?>
<?php do_action( 'generate_after_entry_title' ); ?>
</header><!-- .entry-header -->
<?php do_action( 'generate_after_entry_header' ); ?>
<?php if ( true == generate_show_excerpt() ) : ?>
<div class="entry-summary" itemprop="text">
<?php the_excerpt(); ?>
</div><!-- .entry-summary -->
<?php else : ?>
<div class="entry-content" itemprop="text">
<?php the_content(); ?>
<?php
wp_link_pages( array(
'before' => '<div class="page-links">' . __( 'Pages:', 'generatepress' ),
'after' => '</div>',
) );
?>
</div><!-- .entry-content -->
<?php endif; ?>
<?php do_action( 'generate_after_entry_content' ); ?>
<?php do_action( 'generate_after_content' ); ?>
</div><!-- .inside-article -->
</article><!-- #post-## -->
Any suggestions?
Thanks!
Craig
UPDATE - OK...this may not have anything to do with 3.0.2
It could be PODS...2.7.22 works, but 2.7.23 doesn't.
Digging deeper and will report results...
Sorry for the late response - i couldn't see any reason why 3.0.2 would cause that. Let us know what you find out - Jim True over at PODs support is the man to ask :)
Hi David...yes, after more digging, I'm 100% sure now it's on the PODS side of things.
Thanks!
Glad to hear you found where the issue is coming from - hope they can resolve it!