mcyzyk

I do believe I’ve solved my own issue with a snippet of CSS:

.tax-title a {
    cursor: default;
    pointer-events: none;        
    text-decoration: none;
    color: inherit;
}

Alternatively, is it possible to suppress the hyperlink? So I’d end up with a page of JUST the Terms and their corresponding Descriptions?

Is there any way to get it work in Offline Mode?

Darn. Deleting/reinstalling did not work.

Thanks.

I will Delete, then reinstall, and see if that works.

Right now, I’m just working off a development instance of WordPress, running in a Vagrant box on my workstation.

Much appreciated!

Mark

Much appreciated!

I don’t have Jetpack so I created a category-student-blog.php template:

<?php
/**
 * category-student-blog
 * mcyzyk
 *
 * Force Excerpts
 *
 * BASED ON:
 *
 * The template for displaying Archive pages.
 *
 * Learn more: https://codex.www.ads-software.com/Template_Hierarchy
 *
 * @package Penscratch 2
 */

get_header(); ?>

	<section id="primary" class="content-area">
		<main id="main" class="site-main" role="main">

		<?php if ( have_posts() ) : ?>

			<header class="page-header">
				<?php
					the_archive_title( '<h1 class="page-title">', '</h1>' );
					the_archive_description( '<div class="archive-description">', '</div>' );
				?>
			</header><!-- .page-header -->

			<?php /* Start the Loop */ ?>

				<?php while ( have_posts() ) : the_post(); ?>

					<?php
                        echo the_post_thumbnail();
						echo the_excerpt();
                        echo "<p><hr><p>";
					?>

				<?php endwhile; ?>

				<?php the_posts_navigation(); ?>

		<?php else : ?>

			<?php get_template_part( 'content', 'none' ); ?>

		<?php endif; ?>

		</main><!-- #main -->
	</section><!-- #primary -->

<?php get_sidebar(); ?>
<?php get_footer(); ?>

Is there any way for me to reach into the SQL dump inside the .wpress file and replace all instances of “DEFAULT CHARSET=latin1” with “DEFAULT CHARSET=utf8mb4”???

I.e., some way to open up the .wpress file, edit the SQL dump with a search and replace, then close back up the .wpress file?

Mark

Thanks, George!

That makes sense.

Mark

It definitely looks like the issue here is NOT with this plugin. Rather, the SQL statement coming off the host is setting creation of new tables to DEFAULT CHARSET=latin1

Not good.

Is there any way for me to reach into the SQL dump inside the .wpress file and replace all instances of “DEFAULT CHARSET=latin1” with “DEFAULT CHARSET=utf8mb4”???

Hold the bus!

While I could SEE, e.g., Σωφροσ?νη in the SQL file, there’s this:

`[root@wphost02 my.cnf.d] [DEV] $ strings /opt/wordpress/wp-content/ai1wm-backups/wphost-dev.mse.jhu.edu-symondsproject2-20211216-152123-ld7aj3.wpress | egrep latin1
) ENGINE=InnoDB AUTO_INCREMENT=177 DEFAULT CHARSET=latin1;
) ENGINE=InnoDB AUTO_INCREMENT=282 DEFAULT CHARSET=latin1;
) ENGINE=InnoDB AUTO_INCREMENT=86 DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB AUTO_INCREMENT=11 DEFAULT CHARSET=latin1;
) ENGINE=InnoDB AUTO_INCREMENT=5433 DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB AUTO_INCREMENT=2993 DEFAULT CHARSET=latin1;
) ENGINE=InnoDB AUTO_INCREMENT=2080 DEFAULT CHARSET=latin1;
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB AUTO_INCREMENT=15 DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB AUTO_INCREMENT=66838076 DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
) ENGINE=InnoDB DEFAULT CHARSET=latin1;`

So this backup file IS restoring everything into my new location as “latin1”. It’s baked right into the backup file.

Any way to override this behavior?

Thanks so much!

I used Traktor to open my .wpress file, opened up the .sql file in a text editor, and searched for: Σωφροσ?νη

FOUND!

For all those reading: My issue is not with this plugin.

(And, in fact, I think I’ve determined that my issue is that any new tables in my WP Multisite are NOT being created with UTF-8 encoding. Will investigate, fix….)

Mark

Is there some way for me to unzip the packet and actually SEE whether properly-encoded Greek characters are in its text files?

Thanks!

I am working with custom Taxonomies. Many of my terms have commas in them, e.g.,

disease, causes of

Mark

For what it’s worth, there’s no “taxonomy” archive like there is a “post type archive”. What I mean by that, is no one URL to visit to see ALL posts in the taxonomy, the same way that you can a post type. What there IS available is archives for each term within the taxonomy. For example, if you have a taxonomy of “genre”, and terms of “classic” and “alternative”. The latter two would have their own archives, but not one for just “genre”

Thanks, Michael!

It’s so weird to me that this taxonomy-level “archive” is not built in to the framework itself.

Luckily there is this handy plugin!

https://www.ads-software.com/plugins/taxonomy-list/

Simple, useful, cool.

Thanks for your response, and best regards,

Mark

Waddya know? It worked!

Many thanks,

Mark