| 开发者 | siteaudithub |
|---|---|
| 更新时间 | 2026年11月15日 23:19 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[sahcs_grid limit="6" category="shopify" columns="3" filters="yes"][sahcs_card id="12"][sahcs_section id="12" section="results"] (sections: hero, glance, facts, results, gallery, testimonial, team, faq, cta, overview, challenges, solutions, approach, conclusion)Yes. With block themes SiteAuditHub Case Studies adds templates you can edit in Appearance → Editor. With classic themes it uses your theme's header and footer. Theme developers can override the templates by copying them to your-theme/sahcs/.
Yes, choose the short address in Settings → General. It needs the "Post name" permalink structure. If a page or post already uses the same slug, SiteAuditHub Case Studies adds -2 to the case study so nothing breaks.
No. A section with no content is hidden automatically, so you can keep the full layout and fill only what you need.
The FAQ section always adds FAQPage data. Article and breadcrumb data and a meta description are added only if no SEO plugin is active.
When a shortcode has a wrong id, category or section name, people who can edit the site see a short note explaining what to fix. Visitors never see this note.
Yes. The author's name and photo appear under the introduction ("Written by …"); turn it off or change the wording in Settings → General, or hide it for one case study in the Hero section. Add the Project Team section to credit the people who built the project. Team members are also added to the page's structured data as contributors, including when Rank Math or Yoast SEO is active.
Yes. Case study sections are made in the block editor, so SiteAuditHub Case Studies keeps the block editor on for case studies only, even when the Classic Editor or Disable Gutenberg plugin is active. Your posts and pages keep the editor you chose. Developers can turn this off with add_filter( 'sahcs_use_block_editor', '__return_false' );. Case studies written in the classic editor still get the title, author, table of contents and page layout.
Yes. With WPML, case studies, categories, the texts in every section and the texts in Settings can be translated (a wpml-config.xml file is included). With Polylang, turn on "Case Studies" under Languages → Settings → Custom post types; the Settings texts appear under Languages → Translations. Case studies you pick in blocks and shortcodes automatically switch to the page's language. The plugin itself is translation-ready (languages/sahcs.pot) and supports right-to-left languages.
Yes. Add case studies anywhere with the shortcodes (grid, single card or a single section), for example in Elementor's Shortcode widget or Divi's Code module; the styles load in the page head, also inside the builder's editor. If you design a case study itself with a page builder (or pick a page template such as Elementor Canvas), SiteAuditHub Case Studies leaves that page alone so the builder's design shows exactly as you made it.
In Case Studies → Settings → Shortcodes, pick "Hand-picked case studies", tick them in the order you want and copy the shortcode, for example [sahcs_grid ids="245,312,418"]. In the block editor, the Case Studies block has the same "Choose myself" option.
Yes. Each case study page has one H1 (its title), sections use H2 and their parts H3, with no skipped levels; an H1 typed into the text is shown as H2. It adds Article, FAQ and breadcrumb structured data when no SEO plugin is active, and works alongside Rank Math and Yoast SEO.
Current versions of Chrome, Edge, Safari (16.2 and newer, including iPhone and iPad) and Firefox. Layouts adapt to phones, tablets and desktops.
No. SiteAuditHub Case Studies does not send any data anywhere, does not track visitors and loads no files from other websites. All styles, scripts and icons are included in the plugin. (Author photos in the "Written by" line come from WordPress itself, which uses Gravatar unless you turn avatars off in Settings → Discussion.)
Everything the plugin adds (functions, settings, CSS classes, blocks, shortcodes) starts with "sahcs", and its styles only apply inside its own sections, so it does not change the rest of your site. Styles and scripts load only on pages that show case studies. The small script that measures your header and background is marked so caching and optimisation plugins (WP Rocket, LiteSpeed Cache, Autoptimize, SiteGround Optimizer, Cloudflare) do not delay it. After updating, clear your cache plugin's cache once.
No. If a case study has no Hero section, SiteAuditHub Case Studies shows the title, categories and featured image at the top automatically.
Yes. Colours meet WCAG AA contrast, the table of contents, FAQ and image lightbox work with a keyboard, and the layout supports right-to-left languages.
Your case studies stay in the database. Deleting the plugin removes only its settings.