Tessa Watkins

Awesome, thank you! Feel free to close this out. If I see it after updating to 3.2.0 and beyond, I’ll start a new thread.

Cheers!

Boo, okay, thank you! ??

Sorry for the delay! Here are the details for the site that experienced this most recently.

### wp-core ###

version: 6.0.2
site_language: en_US
user_language: en_US
timezone: America/New_York
permalink: /%category%/%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: closed
environment_type: production
user_count: 4
dotorg_communication: true

### wp-paths-sizes ###

wordpress_path: [redacted]
wordpress_size: 325.29 MB (341089056 bytes)
uploads_path: [redacted]/wp-content/uploads
uploads_size: 99.86 MB (104707788 bytes)
themes_path: [redacted]/wp-content/themes
themes_size: 10.80 MB (11329559 bytes)
plugins_path: [redacted]/wp-content/plugins
plugins_size: 104.19 MB (109249162 bytes)
database_size: 23.14 MB (24268436 bytes)
total_size: 563.28 MB (590644001 bytes)

### wp-dropins (1) ###

advanced-cache.php: true

### wp-active-theme ###

name: GeneratePress (generatepress)
version: 3.1.3
author: Tom Usborne
author_website: https://tomusborne.com
parent_theme: none
theme_features: core-block-patterns, widgets-block-editor, automatic-feed-links, post-thumbnails, post-formats, woocommerce, title-tag, html5, customize-selective-refresh-widgets, align-wide, responsive-embeds, editor-color-palette, custom-logo, menus, editor-styles, editor-style, widgets
auto_update: Enabled

### wp-themes-inactive (1) ###

Twenty Twenty-Two: version: 1.2, author: the WordPress team, Auto-updates enabled

### wp-mu-plugins (2) ###

Elementor Safe Mode: version: 1.0.0, author: Elementor.com
ManageWP - Worker Loader: version: 1.0.0, author: GoDaddy

### wp-plugins-active (21) ###

Central Color Palette: version: 1.15.5, author: Daniel Menzies, Auto-updates enabled
Classic Editor: version: 1.6.2, author: WordPress Contributors, Auto-updates enabled
Elementor: version: 3.7.6, author: Elementor.com, Auto-updates enabled
Elementor Pro: version: 3.7.5, author: Elementor.com (latest version: 3.7.6), Auto-updates enabled
GP Premium: version: 2.1.2, author: Tom Usborne, Auto-updates enabled
Health Check & Troubleshooting: version: 1.5.0, author: The www.remarpro.com community, Auto-updates enabled
Image optimization service by Optimole: version: 3.4.6, author: Optimole, Auto-updates enabled
ManageWP - Worker: version: 4.9.14, author: GoDaddy, Auto-updates enabled
Popup Maker: version: 1.16.8, author: Popup Maker, Auto-updates enabled
Rollback Update Failure: version: 3.1.1, author: Andy Fragen, Ari Stathopolous, Colin Stewart, Paul Biron, Auto-updates enabled
SEOPress: version: 5.9.0.3, author: SEOPress, Auto-updates enabled
SEOPress PRO: version: 5.9, author: SEOPress, Auto-updates enabled
ShortPixel Image Optimizer: version: 5.0.9, author: ShortPixel, Auto-updates enabled
Simple CSS: version: 1.1.1, author: Tom Usborne, Auto-updates enabled
Socialized: version: 2.0.3, author: Tessa Watkins LLC, Auto-updates enabled
The Events Calendar: version: 6.0.0.1, author: The Events Calendar, Auto-updates enabled
Wordfence Security: version: 7.6.1, author: Wordfence, Auto-updates enabled
WP AutoTerms: version: 2.4.9, author: WP AutoTerms, Auto-updates enabled
WP Crontrol: version: 1.14.0, author: John Blackbourn & crontributors, Auto-updates disabled
WP Mail SMTP: version: 3.5.2, author: WPForms, Auto-updates enabled
WP Super Cache: version: 1.8, author: Automattic, Auto-updates enabled

### wp-server ###

server_architecture: Linux 4.19.150-76.ELK.el6.x86_64 x86_64
httpd_software: Apache
php_version: 7.4.28 64bit
php_sapi: litespeed
max_input_variables: 4000
time_limit: 300
memory_limit: 512M
max_input_time: 300
upload_max_filesize: 512M
php_post_max_size: 516M
curl_version: 7.81.0 OpenSSL/1.1.1m
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: true

### wp-database ###

extension: mysqli
server_version: 5.6.41-84.1
client_version: mysqlnd 7.4.28
max_allowed_packet: 268435456
max_connections: 150

### wp-constants ###

WP_CONTENT_DIR: [redacted]/wp-content
WP_PLUGIN_DIR: [redacted]/wp-content/plugins
WP_MEMORY_LIMIT: 64M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: false
WP_DEBUG_DISPLAY: false
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: true
CONCATENATE_SCRIPTS: false
COMPRESS_SCRIPTS: true
COMPRESS_CSS: true
WP_ENVIRONMENT_TYPE: production
DB_CHARSET: utf8mb4
DB_COLLATE: undefined

• This reply was modified 2 years, 6 months ago by Tessa Watkins.

I’ve also seen this with Yoast SEO and Wordfence before.

I had assumed it was due to a timeout error because sometimes those plugins can get pretty massive, especially on some of the websites that are upgrading from very old versions to the latest.

Great, thanks!

That gives me a follow-up question and I can make it a separate support ticket if you’d like.

I’m curious then, do you have a hook or something where I could essentially add my own icon library to your block? Whether it be a different version of FontAwesome or some homegrown icon I make, I think it’d be cool to have that flexibility.

So I’m using ACF checkboxes so that I don’t have to always remember the common hashtags I use. In a post, it looks like this.

This is the checkbox field in ACF I created and it’s field name is hashtags

And for the blog article, this is the ACF settings of one that was recently revived.

So for this article, I’m expecting the hashtags to be: #Neurodiversity #Autism #ActuallyAutistic #KarateMama

Now this next bit is a bit hacky because I couldn’t get it to work on the post save hook, so it takes place in the <head> element.

Theme’s functions.php

/**
 * Get Content for <code><header</code>> Tag
 */
function au_head()
{
    get_template_part('template-parts/header', 'head');
}
add_action('wp_head', 'au_head', 1); //Default priority is 10

In the /template-parts/header-head.php file:

<!-- Start AuRise Head -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="HandheldFriendly" content="true" />
<meta name="host" content="AuRise Creative" />
<?php printf(PHP_EOL . '<script id="aurise-analytics" src="%s/assets/scripts/analytics.js" async></script>', get_stylesheet_directory_uri());
if (is_singular('post')) {
    printf(PHP_EOL . '<!-- %s -->', au_get_hashtag_meta(get_the_ID()));
} ?>
<!-- End AuRise Head -->

That calls the au_get_hashtag_meta() function in functions.php which is defined as:

/**
 * Get Custom Hashtag Meta
 *
 * @param int $post_id
 * @return string message
 */
function au_get_hashtag_meta($post_id)
{
    $message = '';
    if (function_exists('au_update_hashtag_meta')) {
        $message = au_update_hashtag_meta($post_id);
    }
    return $message;
}

And the au_update_hashtag_meta() function is defined like this:

if (class_exists('Rop') && class_exists('ACF')) {
    /**
     * Update Hashtag Meta Value
     * 
     * @param int $post_id
     * @return string message
     */
    function au_update_hashtag_meta($post_id)
    {
        $hashtags_acf = get_field('hashtags', $post_id); //Return value is set to "value"
        if (is_array($hashtags_acf) && count($hashtags_acf)) {
            $hashtags = implode(' #', array_unique(array_filter($hashtags_acf))); //Remove blank and duplicate values
        } else {
            $hashtags = '#ActuallyAutistic #Autism #Neurodiversity #AutisticSelfAdvocate'; //Default hashtags
        }
        //Documentation says to add a space before the first hashtag https://docs.revive.social/article/480-how-to-use-custom-fields-content-url-hashtags-in-revive-old-post
        $hashtags = ' ' . $hashtags;
        $meta_key = sanitize_key('au_hashtags-for-revive-social');
        $updated = update_post_meta($post_id, $meta_key, $hashtags);
        $message = 'Updated [' . $meta_key . '] for post ID [' . $post_id . '] with value [' . $hashtags . ']';
        return $message;
    }
}

As you can see, this is saving my hashtags as a string in the meta field with the meta key au_hashtags-for-revive-social

The documentation comment is referring to this note.

Now when I save the page and view it’s source code on the front end, I can see the comment in the <head> element and it’s still using the proper camel casing that I want.

Now that I can see that my meta field for ROP is being properly updated, I just update the ROP settings in the backend like so.

I figure, at this point, I’m done with the setup and can let it run. However, when it was shared, the hashtags were converted to lowercase as seen here.

Thanks for any help you can provide!

Sorry, I must’ve missed the email notification from 2 weeks ago. I’ll get you those screenshots now.

I also was facing the same issue and it was indeed cache-related.

Using Google Chrome with the page editor open, I pressed F12 on the keyboard to open the debugger, right clicked on the reload icon, and then chose “Empty Cache and Hard Reload” and that resolved it for me.

No messing around with incognito, different browsers, or reloading the page a billion and a half times.

Sure, I can send an email to at least open the ticket but since my last comment, I’ve talked with my client and they no longer use the CoSchedule service so we have no need for this plugin anymore.

I’m having the same exact issue. All actions using wp_ajax_nopriv aren’t even hitting the function it’s hooked to and is instead returning the login page. Logged-in users haven’t been affected but this needs to be fixed ASAP or I can’t use this plugin.

Same here. I really hope the author did not abandon it.

Same. I am so annoyed because now a bunch of my websites that were using the pipe as the separator and they have all been automatically changed to using the default dash.

I am currently remedying this with this code snippet (placed in your theme’s functions.php file), as it puts the “|” back into the list of options to choose from courtesy of Yoast SEO’s documentation. It’s still annoying because I have a bunch of websites that use this and now I have to manually update all of them.

/**
 * Return Pipe to Yoast SEO Title Separators
 * 
 * Adds the Pipe (|) character to the List of title separators in 
 * Yoast SEO that was removed in version 17.1. 
 * 
 * @param array $separator_options Yoast's list of separators
 * @return array Modified list of separators
 */
function tw_wpseo_separator_options( $separator_options ) {
    $custom_options = array('|');	
    if( is_array($separator_options) ) { $separator_options = array_merge( $separator_options, $custom_options ); }
    else { $separator_options = $custom_options; }
    return $separator_options;
}
add_filter( 'wpseo_separator_options', 'tw_wpseo_separator_options', 10, 1 );

• This reply was modified 3 years, 6 months ago by Tessa Watkins.

Okay, thank you. I assumed it was Yoast since it was between the HTML comments for your plugin. Perhaps it was modified by JetPack or WP Fastest Cache because it’s changing the URL to use a CDN link…

For quick reference, is there a PHP hook or filter that either plugin would use to modify that meta tag’s output that I should look for? Thanks!

Sure this is an article on my websites where it’s happening and this is a link to the Facebook sharer debugger where you can see Facebook is pointing out the error.

I think I found a solution. Your last response gave me an idea. I went into Wordfence’s firewall settings and I saw that there were some whitelisted URLs back when it was in learning mode in September.

To test before making my change, I attempted to save the page with both plugins activated as they were and got the security error as I expected.

I then went into Wordfence’s firewall settings and put it back into “Learning Mode” and saved those changes.

I went back to the page and saved, and it worked! I refreshed the firewall settings in Wordfence and saw that a new URL was whitelisted. Specifically /wp-admin/admin-ajax.php for URL, and request.body[settings] under Param. The created date was today and the source says “Whitelisted while in Learning Mode.”

To double-check that the action was indeed fixed, I put the firewall back in “Enabled and Protecting” mode and then went to go edit and save that page again. It still worked.

Glad we could find this fix! I just wanted to post my solution here in case anyone else came across it.