bristweb

We discovered Yoast was inserting these indexables as the canonicals and breadcrumbs for our sites we built on a different staging domain. This caused google to index many pages with the wrong canonical.

wp-cli would be fine, but it forces a reindex. we cannot run wp-cli on our production servers, and our local environment does not use the production domain… so that will not work. it would be helpful if wp-cli had an option to just delete the index and we can push the db to the production server and let it re-index there.

the “yoast test helper” plugin is a no-go. it seems ridiculous to install a second yoast plugin to fix a problem caused by the first. is there not an option to disable or at least rebuild the yoast-indexables through the yoast seo plugin.

preferably, we would like to disable indexables entirely. if we want caching to improve speed, there are other very nice tools and plugins for that.

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

Ok. A filetype where unpacking requires:
1) a server with upload capacity greater than the export size
2) purchasing software
3) installing more software that “macOS cannot verify that this app is free from malware.” and the referenced sourcecode has 2 followers on github.
4) Building new software to read the format

I don’t see any benefit to the end user over .tar or other ubiquitous archive filetypes. I think “proprietary” is accurate even if technically open source. I would have loved to pay you for the software; just not when led on a snipe hunt first.

also have this issue

bill

thanks for the response; i figured backwards compatibility would be an issue… i did take some shortcuts in my code

i really don’t want to keep a hacked version of the plugin if the base concept could be integrated.

could you add a second filter which filters the entire output (rather than just the
li)?
ex: display_posts_shortcode_full_output

if the full output could be filtered and the post array sent to the function – that would allow easy customization (you don’t have to keep trying to make changes to accommodate people’s specific requests)

here is at least a temporary option:
https://www.ads-software.com/support/topic/plugin-subpages-navigation-show-same-level-pages?replies=1

yep, i’m glad to have found the answer too ??

be sure to mark as resolved in the top right.

https://www.ads-software.com/extend/plugins/zigwidgetclass/

you can use the plugin or put the code from zigwidgets into your functions.php

as found here:
https://www.ads-software.com/support/topic/adding-class-to-a-widget-similar-to-custom-menus-plugin-for-this?replies=10#post-2132351

zigwidgetclass is compatible with widgetlogic
https://www.ads-software.com/extend/plugins/zigwidgetclass/

+1

anyone find a solution?

+1

You need to call that action in admin_init, not admin_menu

answer

THANK YOU!

it seems as of the latest update to the admin gui the
remove_submenu_page( 'themes.php', 'theme-editor.php' );
does not work. however
remove_submenu_page('plugins.php', 'plugin-editor.php' );
does work

any idea what changed?

ah the answer is here

why isn’t this update committed to the plugin?

any chance this will be resolved soon? have this exact issue on network activate. interestingly… it does not give this error when activated on each site individually