dcbuffalo

I just used “Check Conflicts” to try to get it to work, and it doesn’t – switched themes, turned everything off, doesn’t work. I had turned off any custom CSS I had on these accordion elements, and it still didn’t work.

I was able to identify that for some reason, the class “on” is not getting added to the .bt_bb_accordion_item when you click on it. Is this a Bold Builder version issue? I doubt it, because I have another site also at v5.0.4, and the accordions work. See the very bottom of the homepage on this development site.

https://2024.saratogaeagle.com

• This reply was modified 3 months, 1 week ago by dcbuffalo.

I finally figured out what is going on. ANY separator (“|” or “-“) that is used within the “og:title” is causing issues, whether they are generated inline or using snippets. Once I removed them from everywhere – site title, Facebook OG and Twitter OG – everything worked perfectly. Parentheses even work fine.

I will be recoding ALL OG data on ALL of my sites now. Even if this gets fixed, I won’t take a chance anymore.

• This reply was modified 1 year, 6 months ago by dcbuffalo.

I put in a ticket with Webkit. We’ll see what that brings up.

I think I now understand what may be happening.

We discovered that Androids and PCs (not just Apple devices) are having the same problem, but displaying even different metadata than iPhones and Macs.

From what I have gathered from numerous support chats and articles, text/SMS message programs and email client programs are supposed to grab “og:title” and “og:image” from the code. The problem I’m seeing now is that the Yoast plugin is no longer generating that specific code. I also tested this with the All-In-One SEO plugin, and the same thing happened. I found some plugins that claim to automatically generate the og: code, but it is impossible to control or configure.

This is all a very new problem for us. I’m wondering if Yoast somehow stopped supporting that, or if this is functionality that has moved to the premium plugin. I would gladly get the premium plugin if it solved this specific problem.

That code didn’t work (nothing happened), but thank you for pointing out the cause. I’m going to advocate on behalf of turning that plugin off – I have trained the client to pre-compress images anyway, so I doubt it is doing much of anything.

I looked on another site that we use this for (saratogaeagle.com) and it’s definitely just overriding the src=”” URL and adding a “data:image” code.

I also tried a .jpg file, that doesn’t show up either.

HA! I only found it because I had to update the text. The campaign went well, but the political chains stopped moving. We sent LOTS of emails, though, so thank you for this plugin!

Here’s a screenshot of what I’m referring to: https://snipboard.io/1uEclV.jpg

This is STILL happening. Had to do a restore of the site because your plugin update broke the site.

PLEASE FIX THIS ISSUE. I can’t believe I’m still asking.

So FYI – I re-did your steps from above, and it works again:

STEP 1:
Go to Plugins > Plugin editor and select Responsive Accordion and Collapse plugin and go to front > style.php on line number 151 replace the below code with another code.

<?php echo esc_attr($custom_css); ?>
to
<?php echo $custom_css; ?>

STEP 2
Go to plugins > plugin editor and select Responsive Accordion and go to lib folder > admin
> data-post > ac-settings-save-data.php file on line number 23 and replace the below code with the new code.

$custom_css = sanitize_textarea_field($_POST[‘custom_css’]);
to
$custom_css = stripslashes($_POST[‘custom_css’]);

Still trying to understand why you don’t just include this in the update.

THIS IS HAPPENING AGAIN IN v.2.3.4.

Please fix.

Or was I still expected to change the other code on my own? Why wouldn’t you just update the code in the plugin?

• This reply was modified 2 years, 5 months ago by dcbuffalo.

You’re welcome.

Right, so it’s affecting other people. My guess is lots of people just delete your plugin and use another one. That wouldn’t be a practical solution in our case. If I have to, I will update and continue to make these two changes to the template files. But obviously, if your solution fixes it AND doesn’t break it for other people, not sure why you wouldn’t put that bug fix into your release cycle.

I don’t want to avoid plugin updates. That can cause other problems.

Does this solution for me cause problems for other people? If not, why not just push these changes to the next update?

If you can’t push these changes to the next version, will these two changes solve the problem in future updates?

I honestly don’t understand why you would not fix an issue that is impacting core functionality like this, even if it’s rare.