Support Portal

Use isolated support storage when the site already contains public posts, comments, products, pages, or community content. Use WordPress posts and comments when the installation is new or dedicated primarily to customer support, or when you need protected attachment uploads.

No. Dedicated topic and reply tables are created only after isolated support storage is selected and saved.

Yes. Switching modes does not migrate or delete either dataset. The portal begins reading and writing through the selected storage mode while the other dataset remains in place.

Customers can view their own topics. Users with the plugin’s dedicated support capabilities can view and manage the topics permitted by those capabilities. Custom roles can also be granted the relevant capabilities.

Under Settings > Support Portal > Support features, configure new-topic and reply uploads separately, file count (1-20), size per file (1-1024 MB), and allowed file groups (images, videos, ZIP). Effective upload limits are capped by WordPress/PHP. No selected file groups means new uploads are disabled. Attachment controls are unavailable in isolated storage, and native-mode preferences are retained when saving isolated-mode settings.

Configure older-reply collapsing, the number of replies shown initially/per expansion (1-100), topics per page (1-100), and WordPress reply avatars versus initials only. Topic page size also applies to embedded lists and customer profiles. WordPress avatar visibility is still respected.

How are topic replies displayed?

By default, the conversation initially shows the five newest replies in chronological order. A highlighted history panel shows the number of older replies remaining and how many replies are visible. Its button reveals another configured batch (five by default) above them each time, with an immediate busy state and a short reveal animation that respects reduced-motion preferences. The browser gets a paint opportunity for the busy state; there is no artificial timed wait. This expands replies already present on the authorized page, without a separate data request. Direct links to older replies reveal their target. With JavaScript disabled, the full conversation remains readable. The original topic body, total reply count, and reply form stay in place.

Yes. Add a Shortcode block to a regular WordPress page with [yoohw_post_form], [yoohw_login_form], [yoohw_lost_password_form], or [yoohw_support_topics]. Use one copy of each shortcode per page, and put login and lost-password forms on separate pages. Topic details and replies continue to open the dedicated portal.

Exclude all shortcode pages from page, CDN, and fragment caches, including for guests. The plugin sends no-cache signals, but an upstream cache can respond before WordPress runs. Builders must render the shortcodes server-side before footer scripts.

Categories can be restricted by user role or by access code, depending on how the portal is configured.

Protected attachment uploads are currently available only in WordPress posts/comments storage mode. In that mode, support attachments handled by the protected attachment system are stored outside the public uploads path and served through an authorization check. Upgrading from 1.0.0 requires the administrator to secure existing support attachments explicitly. Activation does not move or delete files. See the attachment storage guide included in the plugin and the Upgrade Notice below.

No. Support Portal does not transmit support conversations, attachments, or account data to YoOhw or another external service.

Only if the site administrator explicitly enables the optional footer-credit setting. It is disabled by default.

The plugin removes its settings, scheduled hooks, and custom capabilities. Support conversations, attachments, users, categories, and isolated support tables are intentionally retained to reduce the risk of accidental data loss.