AI Chatbot & Semantic Search: ChatGPT Answers From Your Content
| 开发者 | webdigit |
|---|---|
| 更新时间 | 2026年10月2日 17:16 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
标签
下载
1.1.4
1.1.8
1.1.8.2
1.1.8.3
1.1.8.4
2.2.0
2.3.1
2.7.2
2.4.11
2.5.5
1.1.1
2.6.1
2.6.2
2.5.6
2.8.12
1.1.2
2.4.12
2.8.1
2.8.3
1.0.0
1.0.3
1.1.3
1.1.6
1.1.7
1.9.0
2.1.0
2.3.0
2.4.5
2.4.2
2.5.0
2.4.1
2.4.7
1.0.2
2.4.3
2.4.10
2.4.8
2.4.9
1.1.0
2.0.0
2.5.2
2.2.1
2.4.6
2.5.3
2.5.4
1.0.1
1.1.5
1.1.7.1
1.1.8.1
2.3.2
2.4.0
2.4.4
2.6.0
2.6.4
2.7.0
2.7.3
2.7.5
2.8.0
2.8.2
2.8.4
2.8.5
2.6.3
2.7.1
2.8.6
2.8.8
2.8.9
2.8.10
2.5.1
2.8.13
2.8.14
2.7.4
2.8.15
详情介绍:
Answers your visitors can trust, drawn only from your own content. SmartSearchWP turns your WordPress site into an AI assistant that replies from YOUR posts and pages, grounded in your data instead of generic ChatGPT answers. It pairs an AI chatbot with a semantic search engine (RAG) that retrieves the right passages from your content before it answers. It runs on your own site, with your own OpenAI key.
Premium: unlock all 10 premium add-ons (WooCommerce, PDF, custom post types & ACF, lead capture, analytics, usage control, prompt override, and more) for €49.99/year. Get SmartSearchWP Premium »
Whether you run an eCommerce store, corporate site, blog, or documentation platform, SmartSearchWP improves engagement, reduces support workload, and enhances content discovery.
What makes SmartSearchWP different
Most AI chatbot plugins simply forward your visitors to OpenAI. SmartSearchWP is built around three ideas:
- Grounded in YOUR content. Answers are retrieved from your own posts and pages using embeddings (RAG), so replies stay on topic and reflect what you actually published, not the open web.
- Self-hosted, your key. The plugin runs on your WordPress install and calls OpenAI with your own API key. Your content and your keys stay under your control, which helps with GDPR compliance.
- Modular, not bloated. A complete free core, extended by dedicated premium add-ons you install only if you need them.
- Fewer repetitive support requests: visitors get instant, content-based answers.
- Better content discovery: semantic search surfaces the right page instead of keyword guesses.
- Answers you can stand behind: responses are drawn from your published content, not invented.
- Full ownership: your site, your OpenAI key, your data.
- WooCommerce Integration (premium addon): use your products, with SKU and price, as a content source.
- PDF (premium addon): add the content of your media-library PDFs to the answers.
- Custom Type Manager (premium addon): index custom post types and ACF fields (the free core indexes posts and pages).
- Prompt Override (premium addon): replace the system prompt to control tone and scope.
- Usage Control (premium addon): restrict access by role, page, device, schedule, or question budget.
- RAG Auto Sync (premium addon): automatically re-index new content (uses your OpenAI key).
- Lead Capture (premium addon): collect visitor emails in-chat with a GDPR form and CSV export.
- Analytics & Insights (premium addon): a KPI dashboard over your chat logs (top questions, charts, CSV, weekly email).
- RAG Debugger (premium addon): test questions and inspect the retrieved contexts.
- Customization (premium addon): adjust the chatbot appearance (colors, position).
- Site owners, agencies, and developers who want answers grounded in their own content.
- Teams that prefer a self-hosted tool using their own OpenAI account rather than a SaaS black box.
- eCommerce, corporate, blog, and documentation sites that want to reduce support load and improve discovery.
- Anyone who does not want to use their own OpenAI API key (the plugin needs one to answer).
- Sites looking for a fully managed, hosted chatbot with no setup: SmartSearchWP runs on your server.
- Live human-agent chat: SmartSearchWP answers from your content, it is not a live-chat helpdesk.
- Lightweight architecture
- API-based processing via OpenAI
- No unnecessary front-end bloat
- Full administrative control
- Easy activation and deactivation
- eCommerce stores providing instant product assistance
- Corporate websites reducing support requests
- Blogs with large content libraries improving discoverability
- Technical documentation sites offering intelligent Q&A
- Agencies deploying scalable AI solutions for clients
安装:
- Upload the plugin files to the
/wp-content/plugins/smartsearchwpdirectory, or install the plugin through the WordPress Plugins screen. - Activate the plugin through the 'Plugins' screen in WordPress.
- Enter your OpenAI API key in the SmartSearchWP settings panel.
- Configure indexing and chatbot behavior.
- In SmartSearchWP > Summaries, generate embeddings for at least one page or post, then click Activate. The chatbot will not appear on the front end until at least one context is active - without this step, the plugin may be enabled in settings but no content has been selected for the chatbot to use.
- Display the chatbot using the provided interface or shortcode.
屏幕截图:
常见问题:
Does this AI chatbot answer only from my own content?
SmartSearchWP grounds its answers in the pages and posts you choose to activate on your own site, so replies stay tied to what you actually publish rather than to generic web knowledge. You decide which content is indexed and can update or remove it at any time. Answers are generated by OpenAI from those retrieved snippets, using your own API key.
What makes SmartSearchWP different from hosted AI chatbot plugins?
It runs entirely inside your own WordPress install and connects to OpenAI with your own API key, so there is no third-party SaaS service sitting between your visitors and your site to store your content or conversations, and there is no per-seat pricing. Optional usage statistics are off by default and carry no personal data or visitor tracking (see "Does SmartSearchWP send data off-site?" below).
Does SmartSearchWP slow down my site?
No. Processing is handled through the OpenAI API. The plugin remains lightweight and modular.
Can I control AI responses?
Yes. You can customize prompts, restrict usage, define content sources, and manage behavior precisely.
How are OpenAI API costs managed?
You use your own OpenAI API key and can restrict usage by role, page, or quota limits to control costs.
Is WooCommerce supported?
Yes. With the WooCommerce integration addon, product data can be included in contextual AI responses.
Can I disable the chatbot easily?
Yes. The plugin can be deactivated at any time without affecting your website content.
The chatbot shows "Forbidden" or a raw error page
Some hosts (Wordfence, ModSecurity, OVH CDN Basic, etc.) block POST requests to /wp-json/wdgpt/v1/retrieve-prompt. Since version 2.7.4, SmartSearchWP retries automatically, falls back to admin-ajax.php, and shows a friendly message instead of raw error HTML. If issues persist, whitelist that REST route or exclude it from your CDN/WAF rules.
WooCommerce: search by SKU or product reference
With the WooCommerce Integration addon (1.4.0+) and SmartSearchWP 2.8.0+, the chatbot can match exact product references (SKU, ref_xxx) before semantic search and uses grounded numeric prices in the AI context to reduce wrong amounts (e.g. 83,46€ vs 8346€). Regenerate product embeddings after upgrading so SKU and price are indexed.
How do I activate the bot?
The bot will not appear on your website until you have activated it. To activate the bot, you need to generate and activate the embeddings for the pages and posts you want to use, as well as the general settings. General settings:
- Go to the SmartSearchWP settings page.
- Enter your ChatGPT API key.
- Modify the settings to your needs.
- Save the settings.
How do I customize the chatbot's context?
Generate and activate pages:
- Go to the SmartSearchWP 'Summaries' page.
- Click on the 'Generate Embeddings' button under the page or post you want to use.
- Once their embeddings have been generated, click on the 'Activate' button under the page or post you want to use.
- Repeat steps 2 and 3 for all the pages and posts you want to use.
Does SmartSearchWP send data off-site?
Yes, in two cases:
- OpenAI (required for answers): questions and retrieved content snippets are sent to OpenAI using your own API key. See OpenAI's terms.
- Optional usage statistics (off by default): only if you enable Usage statistics in SmartSearchWP settings. Then the plugin sends a hashed site identifier, plugin version, license type, and five admin event counters to smartsearchwp.com. No personal data, no visitor tracking. See our privacy policy.
Will I see extra notices in wp-admin?
A setup reminder can appear on SmartSearchWP screens only, if the chatbot is not configured yet (missing API key or no active content). It is dismissible, capped, and never shown on the rest of the dashboard. It does not promote premium features.
How do I get help?
Browse our FAQ at https://www.smartsearchwp.com/faq/ for answers about setup, addons, licensing, and technical topics. If you cannot find what you need there, contact us at hello@smartsearchwp.com.
更新日志:
2.8.15
- Optional usage statistics: a one-time, dismissible prompt on SmartSearchWP admin screens now invites you to turn on anonymous usage statistics. Still off by default and opt-in only; shown once, and choosing "Not now" or closing it never asks again. No new data is collected beyond what 2.8.12 already described.
- Housekeeping: minor readme formatting cleanup. No functional change.
- Admin labels: contexts menu uses a proper translatable string; add-on names on the Addons screen follow the site language. French and other bundled locales updated. Not a claim that every add-on screen is complete in six languages.
- Review reminder now appears after realistic usage on smaller sites (eligibility threshold lowered). Still admin-only, dismissible, sentiment-routed, and shown only when the chatbot has a configured context and no recent errors. No incentives.
- Add a setup reminder on SmartSearchWP screens only (API key + content). Admin-only, dismissible, capped, no external calls, no premium upsell.
- Optional usage statistics (off by default): hashed site identifier, plugin version, license type, and 5 admin event counters sent to smartsearchwp.com. No personal data, no visitor tracking. Documented in this readme and the privacy policy.
- Security: admin REST permission checks for log purge/export now require the manage_options capability (previously a broken role check could allow unauthenticated access)
- Fix: Error Logs and Chat Logs "Purge Logs" now deletes entries older than the selected period (operator was inverted); nested purge markup cleaned up; admin purge requests send a REST nonce
- Fix: embedding API errors that are not rate limits no longer trigger false "temporary 429 / rate limit" email alerts (logged correctly; emails stay quiet for invalid JSON request bodies)
- Fix: weekly reporting cron is restored more reliably after plugin deactivate/reactivate, and auto-heals when Reporting is ON but the schedule hook is missing
- Addons manager Buy buttons now open the matching add-on page (one Premium license still unlocks all 10 add-ons)
- Quiet reminders on the Addons screen: renew if your license expires soon or has expired (installed features keep working), and a thank-you note after 6 months on the free core
- Reminders are dismissible except the expired-license status; nothing is sent off-site
- If a required runtime file is missing after an incomplete update, the plugin shows an admin notice instead of taking the site down
- More reliable premium add-on install from the Addons screen (download then install from a local zip)
- Fix (important): resolves a fatal error some sites could hit on 2.8.7 (a required runtime file was missing from the package). Updating to 2.8.8 restores normal operation; your settings and data are kept.
- Addons manager: clearer, benefit-first descriptions of premium addons (including Analytics) and a short value intro at the top of the catalog.
- Expired Premium license message now states that installed addons keep working; renew for addon updates, new addons, and priority support.
- Fix: removed the extra generic "rate this plugin" notice on General Settings (it showed on every visit, unnamed). The named SmartSearchWP review notice from 2.8.6 is unchanged.
- The in-plugin review notice now uses the same capability as the plugin menu and is never shown on Error Logs.
- Housekeeping: removed an unused compiled JavaScript file that the plugin no longer loads.
- New: Optional admin notice asking for a WordPress.org review after real chatbot usage (conversations over several days) - never shown on a fresh install
- The notice is dismissible and snoozable, capped, and skipped when the chatbot has recent API errors or many unanswered questions
- Satisfied admins are pointed to the public review form; unhappy admins are pointed to support and the FAQ - the review link stays available (no incentives)
- Readme: clarified which capabilities are premium addons (Usage Control, Prompt Override, WooCommerce, PDF)
- Readme: refreshed screenshots and compatibility (tested up to WordPress 7.1)
- Developer: filter
wdgpt_can_send_promptbefore OpenAI generation (addons can deny a prompt with a service message) - Developer: action
wdgpt_prompt_acceptedafter a prompt is accepted (usage counters / quotas)
- New: Email alerts on Error Logs - configure recipients and alert types (quota, invalid API key, rate limit, server errors) with 6-hour anti-spam throttle
- New: Test alert email and last-sent banner on the Logs tab
- New: Optional setting to hide the front chatbot when OpenAI reports insufficient quota / billing (default off; auto-restore after TTL or successful API / key validation)
- Developer: action
wdgpt_error_loggedafter chatbot errors are persisted
- Fix: Contexts admin page no longer appears blank when OpenAI returns temporary API errors (5xx, rate limits, connectivity issues)
- Fix: OpenAI API validation distinguishes invalid keys from transient server errors instead of treating every non-200 response as an invalid key
- Fix: Settings page shows the correct warning during OpenAI outages; validation results are cached briefly to avoid repeated live checks on each admin load
- Developer: read-only filter
wdgpt_rag_debug_retrieval_resultafter retrieval selection (including empty contexts); Chat Logs row link to RAG Debugger addon when active
- New read-only
WDGPT_Logs_Repositoryfor aggregated chat log metrics (conversations, messages, daily series, top pages, top first questions, no-answer patterns) - Action
wdgpt_conversation_loggedfired after each persisted conversation turn (for Analytics addon cache invalidation)
- Front-end hooks for premium addons: filter
wdgpt_chatbot_front_config(extendswdChatbotData) and actionwdgpt_chatbot_ui_before_inputwith UI slot#wdgpt-addon-ui-slotfor in-chat addon UI (e.g. Lead Capture) - Plugins page: contextual license notice under active SmartSearchWP addon rows (links to the matching addon in Addons manager or License settings)
- RAG grounding: detect product identifiers (SKU, ref_xxx) and allow addons to force matching products into context before semantic ranking
- Prompt guardrails against inventing prices or statistics not present in the provided context
- Filters
wdgpt_retrieval_product_identifiers,wdgpt_retrieval_force_contexts,wdgpt_answer_after_streamfor WooCommerce and extensions - Debug retrieval logging when SmartSearchWP debug mode is enabled
- Fix: Contexts (embeddings) admin tooltip no longer claims automatic generation on save - manual Generate Embeddings + Activate remains the default workflow
- Contexts page notice pointing to the premium RAG Auto Sync addon for automated indexing (with API cost awareness)
- New
wdgpt_generate_embeddings_for_post()helper andwdgpt_before_generate_embeddingsfilter for addon integration
- Fix: proper handling of network/WAF errors on chatbot retrieve-prompt requests (no more raw Forbidden/error page displayed in the chat bubble)
- Automatic retry with backoff, admin-ajax.php fallback when /wp-json/ is blocked, localized user message, and console diagnostic logging
- FAQ note for hosts that must whitelist
/wp-json/wdgpt/v1/retrieve-prompt
- Fix truncated or garbled assistant text in admin chat logs and scheduled PDF/email reports when using Chat Completions streaming (e.g. gpt-4.1-mini): buffer incomplete SSE lines server-side before JSON decode - cURL can split
data:events mid-line, which previously dropped delta chunks while the live chat still looked correct - Log storage: assistant messages use
wp_kses_post()(safe HTML such as<br>and links); user messages usesanitize_textarea_field()for longer questions and UTF-8 text
- Fix chatbot response truncated or overwritten during streaming (only end of message displayed)
- More robust SSE parsing: use proper JSON.parse instead of fragile string extraction for stream chunks
- Simplified streaming display: single content span to avoid overwrites and duplication when links appear
- Safety net: on stream completion [DONE], re-render full answer to ensure correct display even if streaming glitched
- Cleanup of chunk queue and writing state on completion to prevent memory leaks
- Add "Download discussion" link in chat logs page to export a single conversation as .txt file (questions and answers)
- Fix multi-encoded HTML entities in streamed chatbot responses (&... on special chars, paths, code blocks)
- Use raw text buffer during streaming instead of re-processing rendered HTML through markdown (prevents cascading encoding)
- Fix gpt-5-nano stuck without response: use text.verbosity for OpenAI Responses API (parameter moved from root level in 2025)
- Added support for all available ChatGPT models (Chat, Reasoning, Frontier) depending on API key and OpenAI account
- New model selection with optgroups: "Recommended for chatbot" and "Other models"
- Model characteristics: recommendations, warnings, estimated cost level (Low/Medium/High)
- Icons and visual indicators for each model's suitability
- Support for reasoning models (gpt-5, o3, o4-mini, o3-mini, gpt-5.4, gpt-5-mini, gpt-5-nano) via Responses API
- Updated plugin description and readme content for WordPress.org
- Fix multi-encoded HTML entities in chatbot responses (paths, code, special chars displayed as &...)
- Add decodeHtmlEntities to restore readable display of over-encoded content in streamed responses and localStorage messages
- 100% compatibility with WordPress 6.9.1
- Fix undefined property and variable in answer generator (OpenAI client, error handling)
- Fix cosine similarity when embedding vectors have non-sequential keys (prevents PHP notices)
- Added export all conversations feature in chat logs page
- Fixed undefined array key error in logs table
- Fix welcome and greeting messages display issue
- Improve JavaScript handling for chat bubble text retrieval
- Add "Purge Transients" button in general settings to clear addons cache
- Improve error handling in API calls with try-catch blocks
- Enhanced stability when OpenAI API calls fail
- Corrected formatting of the URL for the 'get a free licence' button in the actions menu
- Official support for the Usage Control addon: restrict chatbot access by user role, page, post type, and device (mobile/desktop).
- Improved extensibility for future addons.
- Various fixes and optimisations.
- Support for the Prompt Override addon: ability to customise the prompt sent to the AI.
- Improved addon integration.
- Various fixes and optimisations.
- Modification of OpenAI API key verification.
- Debugging functionality
- Added the option of displaying the licence key in plain text in the back office
- Added new logs for licence management
- Better licence cache management
- New debugging functionality added to the plugin
- Better management of licence renewal dates
- Added identification of private pages in the list of pages and posts
- Improving contexts that are too long, mainly for pdf files
- Improved compatibility for version php8.1
- Update translations for all existing languages
- Improved licence key management for back office performance
- Add plugin version to general settings
- Update translations for all existing languages
- Add German (de_DE) translations
- Add Spanish (es_ES) translations
- Add bulk action to generate embeddings, activate or deactivate pages and posts
- Fix bug with 0 & 1 replacement in answers (Thanks to Robert Grygier)
- Update translations for all existing languages
- Add Italian (it_IT) translation
- Fix translation display and warnings in POT files
- Fixed default clause in switch statements
- Change deprecated function FILTER_SANITIZE to FILTER_SANITIZE_FULL_SPECIAL_CHARS
- Add norwegian langage (thanks to Robert Grygier)
- Fix embeddings generation if context is too big
- Add compatibility for generating context with pdf file (add-on with pdf compatibility will be required, soon available)
- Resolved an issue which might expose openAI key.
- Resolved an issue to SQL & XSS injection in the chatbot interface and user restriction to purge logs.
- Resolved an issue where the answer stream was truncate.
- Resolved an issue where the answer couldn't be written in the interface due to empty chunks.
- Resolved a problem where the Text-to-Speech function was incorrectly processing HTML and Markdown tags in the speech.
- Introduced notifications within the admin panel to alert users about pending updates for addons.
- Corrected a glitch causing the chat interface to scroll to the top upon submitting a prompt.
- Addressed an issue encountered when viewing the chatbot on a WooCommerce product page.
- Resolved a visual inconsistency issue with the Text-to-Speech (TTS) button on specific websites.
- Introduced a feature that allows users to halt the Text-to-Speech function by clicking the button a second time after it has been activated.
- Implemented a prevention mechanism to avoid the accumulation of Text-to-Speech tasks in the queue, enhancing the overall user experience.
- The chat now includes built-in Text-to-Speech and speech recognition features! A new button, located to the left of the input field, has been introduced to capture and transcribe user's spoken input. Additionally, each message can be audibly read out using the Text-to-Speech option.
- Resolved an issue where existing CSS rules on a WordPress site could potentially override the visual style of the chatbot plugin.
- The small notification bubble above the chat icon has been reinstated! It's now compatible with the customization addon and will display correctly based on the position set within the addon.
- We've eliminated the random number that used to appear on top of the chatbot icon, as the notification bubble now serves the same function.
- The greeting message is now customizable! If you don't alter them in the settings, it will default to the standard translations. This feature has also been implemented for the chatbot bubble.
- Cleaned up contexts' embeddings generation.
- Prevent the user from regenerating embeddings when there is no need to.
- Fixed a pagination issue inside the contexts' interface, and only show contexts based on the current language if the user is using WPML.
- Upgraded to gpt4-o from gpt-4 for faster answer generation and reduced token cost. This change is automatically applied within your plugin.
- With gpt4-o, the generated answers can be up to three times longer compared to gpt4 and gpt-3.5-turbo.
- Resolved an intermittent issue where the addons' catalog was not properly receiving data from the website.
- Fixed a problem with the premium license verification. It should now renew itself correctly. This issue did not affect your license but was not properly automated.
- Added a clickable permalink next to the context's title in the contexts' interface for easy page access.
- Integrated WPML support in the contexts' interface to identify the page language, useful when dealing with pages of the same name in different languages.
- Resolved an issue where Markdown was not always correctly applied when generating answers. This fix is also applied to the logs.
- Introduced a filter in the context's interface to display only posts or pages with the selected status, such as active or having embeddings.
- Fixed an issue where the search box was not functioning correctly under certain conditions.
- Corrected an issue where translations were not properly applied in the addons manager during premium license verification.
- Rectified a situation wherein the image and title of an addon within the catalog were mistakenly perceived as buttons, rather than directing to the appropriate addon.
- Resolved an issue occurring when the user's API key lacked credit, resulting in improper verification of results.
- Presenting a fresh look! The chat interface now boasts an enhanced default appearance compared to its predecessor.
- Addressed an issue where the disclaimer occasionally extended beyond the confines of the chat frame, subsequently augmenting its size.
- Implemented spacing between the input field and the send button for improved user experience.
- Enhanced aesthetics and space efficiency by substituting the chat's name with its icon when generating responses.
- Optimized the ellipsis used as a loading indicator for improved functionality.
- Premium addons are now available! You can access them via the "Addons" submenu within the admin page. There's also a free license available for any potential free addons.
- We've resolved an issue where the chatbot container would occasionally hide behind other elements. The container will now consistently maintain its priority.
- Fixed an issue that could sometimes prevent the user from deactivating the plugin.
- Added a verification for the required 'allow_url_fopen' server setting.
- Added a new disclaimer below the chat interface to inform users that artificial intelligence can occasionally make mistakes. Users are advised to verify critical information.
- Improved answer generation for a more seamless reading experience for users.
- Fixed an issue that prevented links from being clickable while the chatbot was generating a response.
- Resolved an issue where certain segments of words could be omitted during answer generation, leading to potential problems in the output.
- Addressed an issue where certain characters were displayed as their HTML codes instead of their readable forms (e.g., € was displayed as €).
- Corrected a problem where the general settings sliders did not update their values correctly upon page reload.
- Enhanced visual appeal! The answers now support markdown and parse them for users to enjoy a better experience, such as bold or italics. This is also in effect inside the chat logs and the reporting.
- Fixed an issue that could occur if the posts had a special encoding.
- Fixed an issue with the counting of tokens when using GPT-4.
- Added a verification for users that had updated to 1.1.8 before.
- Fixed an issue that prevented some users from correctly updating the database.
- Added a new validation inside the admin page to verify that the API key is valid.
- Added a new validation inside the admin page to verify if your current API key is able to use gpt-4.
- Added a reporting that the current API key has insufficient credits to be used.
- Added a new validation inside the admin page to let the user know if the OpenAI API is having issues.
- Added a toggle to enable/disable the chatbot on the front-end.
- Fixed an issue with translations not being loaded correctly in the administration page.
- Added a new color inside the administration interface for contexts that have been activated, but their embeddings are not "up to date" with the content of the page.
- Added a legend on top of the contexts table to explain the different colors.
- Added a new chat bubble next to the interface to better show the chatbot to the users. This bubble can be hidden directly, or 5 seconds after the page has been loaded.
- Added an option to hide the chat bubble completely.
- Added a new feature to receive, by mails, a PDF that will contain the conversations made by users in the last day or week. This report will run through a cron every day.
- Fixed an issue with error reporting.
- Fixed an issue with error reporting on some PHP versions.
- Fixed an issue with the answer generation with bad formatting of posts.
- Fixed an issue with bigger contexts using the wrong model.
- Added missing vendor files.
- Added a new feature to have the chatbot answer "word by word" instead of waiting for the full answer to be generated.
- The new feature will also make the chatbot answer faster, especially on long answers.
- The chatbot will no longer automatically scroll to the bottom when a new answer is generated. This allows the user to start reading the answer while it is being generated.
- Further fixed the clickable links in the chatbot interface to prevent them from not being interpreted correctly.
- Fixed an issue with the chatbot logs delete function on some PHP versions.
- Fixed an issue with the chatbot interface in some resolutions.
- Fixed an issue when holding a conversation with the chatbot for a long time.
- Fixed an issue with the chatbot interface when the user is typing a message while the chatbot is generating an answer.
- Fixed an issue when trying to find the most relevant page to answer a question on certain posts.
- Fixed an issue when using the previous messages in the conversation when trying to generate an answer.
- Fixed an issue with previous versions of PHP.
- Updated minimum PHP version to 7.4.
- Fix an issue with some model versions for retrieving the chatbot's answer.
- Fix issue with some PHP versions.
- Answer time should now be faster.
- Optimized the chatbot interface for better performance.
- Improved the answer generation algorithm for better quality, especially with longer answers.
- Added a new "reset conversation" button to the chatbot interface.
- Introduced an "Expand/Compress" button to adjust the width of the chatbot interface.
- Added colour to better differentiate activated and deactivated pages in the summaries page.
- Fixed display issues with certain links and line breaks in the chatbot interface.
- Fixed display issues with certain links and line breaks inside the chatbot logs admin page.
- Fix issue on the chatbot interface on certain sites.
- Add link to the SmartSearchWP website in the description of the plugin.
- Add chatgpt Model selection in settings (chatgtp3.5-turbo or chatgpt-4)
- Some CSS fixe
- Initial release.