whistlerdan

You misunderstand me. This has nothing to do with the plugin. It just so happened that while I was doing that, I went into PHPMyAdmin and that’s when I discovered the Oembed caching in two places.

It is not specific to the plugin.

That’s great to hear!

I’m using Generatepress. This isn’t on a live site right now, so I can’t send you a link. GP is a popular theme, though. You might want to download it and test this out. For now, I’m going to move away from this plugin until more of the kind are worked out. I don’t have time for this much troubleshooting.

I can confirm permalink issue is now fixed with the new update. Excellent!

Regarding the glossary home page, I see what you are saying now. I didn’t realise it created the glossary home page itself automatically with the /glossary/ URL.

May I make a suggestion about the availability of the option regarding the inclusion of the letter in the permalink structure…

My first thought with that was “what an SEO/redirection nightmare”. If you were to make a glossary with hundreds of terms, and then later change that option, you would have to implement a bulk redirect for every entry. This means that if someone decided to upgrade to pro at a later date to get that feature, they will have to deal with this.

If you offered that feature in the free version and put the option clearly in the settings page, not hidden on the permalink page, then people can make that decision at the beginning of using the plugin, and then stick with that decision. I think overall, this would create a better experience with the plugin.

Also, if the default option if for “use initial character in URL” to be ON, I think you need to change the visuals of it. To me, that switch looks to be in the OFF position, so it looks confusing.

So you should either change the switch to the right-hand ON position, or re-word the label to say “remove initial character in URL” which would actually make more sense as a feature.

• This reply was modified 3 years, 10 months ago by whistlerdan.
• This reply was modified 3 years, 10 months ago by whistlerdan.
• This reply was modified 3 years, 10 months ago by whistlerdan.
• This reply was modified 3 years, 10 months ago by whistlerdan.

Great! Thank you.

This doesn’t make sense to me. As I said, I tried the Pro demo on your website and looking at the module page there are now many items on there, such as Redirections, which now say PRO next to them. Seemingly indicating that you need PRO version to enable these modules.

Are you saying this is not the case?

Unfortunately, I think they are going to remove a ton of the features from the free version.

I tried the demo version of Pro on their site, and add-ons such as Redirection, are now labelled as Pro features.

I guess this was the plan all along, but I think there is going to be a lot of backlash coming their way.

• This reply was modified 4 years, 4 months ago by whistlerdan.

“Having said this, as a workaround, we encourage you to build your homepage content as a page”

Yes, this is what I have done as the workaround. But this removes literally all of the features of the Extra theme. While the theme is built around their Divi builder, the Extra theme also has additional functions for magazine style websites and these are only available using an additional builder that is only part of the Extra theme. You cannot implement these additional functions using the regular Divi builder when building a regular page.

You can see the functions on their page here: https://www.elegantthemes.com/gallery/extra/

All of those magazine features, the entire point of the theme, are unavailable to me if I use the workaround to simply set the homepage as a page. It makes the use of the theme completely pointless.

What also should surely be concerning you is that your users that have this theme, have got a dire problem with their site after updating to V14, and many, probably most, don’t even know it. I was lucky because Google Search Console told me about the problem, but the Yoast plugin did not offer any warning that the homepage was now noindexed.

I’m also struggling to understand why any page would be noindexed by default when the site default is to index everything. Surely to noindex a page should require some sort of positive action somewhere? I accept that without the Yoast meta box I can’t make changes on that page, but surely it should at least behave with default behaviour?

And also, perhaps to point out the obvious… this was all totally fine with Yoast 13.xxx. So there must be a way to get this to work because it has been just fine for years.

I’m not able to edit the meta robots setting because there is no Yoast meta Box when creating page layouts with the Elegant Themes layout builder.

As I said in my previous reply, these layouts that you create in this theme do not show up in the Custom Post Type section, so I cannot go to SEO > Search Appearance > Content Types and check whether it says “show”

“Check if Yoast SEO is ticked in Screen Options on the upper right-hand side when editing a post or page (classic editor)”

Yes, I already checked this and Yoast does not even appear in the screen options section.

Note to Yoast Devs. At this time I have implemented a (hopefully) temporary workaround by changing the entire front page design of our site so that I can get Google to re-index it again. In order to do this I’m having to give up the majority of my theme’s functionality, but at the moment I just need to get it indexed again because it is causing a slump in traffic.

I’m happy to help you guys troubleshoot this issue further if you need more help from my end by accessing my dev site or something like that.

Like I said, what I have done in the short term is not a solution. And I’m sure there are other who maybe have this issue and don’t even know about it. I’m just glad I was connected to Google Search Console to they emailed me to tell me about the problem.

No the type of page that it creates with the builder does not show up in in the Taxonomies section. It also doesn’t show up in the section where custom post types would show up. Therefore I’m not able to change it to index in that way.

By the way, I spoke to tech support at Elegant Themes who make the theme. They say that they are also aware of this issue… so it’s not just me. I’m hoping you guys can get a fix for this ASAP because my site has been loosing traffic for the last two weeks and I could not figure out why. Now I know!

This doesn’t solve the issue because my homepage is created using the Divi category builder and on the page where you design that, there are no meta boxes for Yoast options. So there is no way to change the robot behaviour for pages that use that specific builder layout.

Additionally, in the Reading settings for WordPress, the problem also occurs if the homepage setting is set to “Your homepage displays: Your latest posts” because the theme is designed to use another builder design by default if you use this setting.

The only way I can currently get the homepage to index is to define a specific page as the homepage, because this then gives me the Yoast Metabox where I can specifically ensure that this page is indexed.

For some reason it’s as if Yoast 14’s default behaviour is simply to noindex any page that it doesn’t understand?

• This reply was modified 4 years, 9 months ago by whistlerdan.
• This reply was modified 4 years, 9 months ago by whistlerdan.

@digitalsmithy Ahh that’s another great tip. That’s handy when you have grouped elements. I wonder why it’s hidden so small at the bottom.

THANK YOU for posting the answer. This was also driving me nuts!

What an odd UI fail to slip through the cracks.

• This reply was modified 4 years, 12 months ago by whistlerdan.