| @@ -64,11 +64,11 @@ | ||
| 64 | 64 | $platform_labels = ModelRegistry::platforms(); |
| 65 | 65 | $model_labels = ModelRegistry::models( $active_platform ); |
| 66 | 66 | |
| 67 | 67 | // Glossary suggestions are existing-terms-only, and the glossaries taxonomy is only |
| 68 | - // registered for Pro (see Core\PostType::register_glossaries_taxonomy). So the "Suggest | |
| 69 | - // glossaries" control must require, on top of the two settings, that Pro is active AND at | |
| 70 | - // least one glossary term exists — otherwise the modal advertises an offer that can never | |
| 68 | + // registered by Pro (see BetterDocsPro\Core\GlossaryTaxonomy::register_glossaries_taxonomy). | |
| 69 | + // So the "Suggest glossaries" control must require, on top of the two settings, that Pro is | |
| 70 | + // active AND at least one glossary term exists — otherwise the modal advertises an offer that can never | |
| 71 | 71 | // return anything. Mirrors the Docs-AI-suite availability check in Core\DocsAISuite. |
| 72 | 72 | $glossary_count = wp_count_terms( array( 'taxonomy' => 'glossaries', 'hide_empty' => false ) ); |
| 73 | 73 | $has_glossary_terms = ! is_wp_error( $glossary_count ) && (int) $glossary_count > 0; |
| 74 | 74 | $glossary_suggestions_enabled = (bool) $this->settings->get( 'enable_glossaries', false ) |
