Pavel Web Design LLC
Forum Replies Created
-
Forum: Plugins
In reply to: [Ask My Content - AI Q&A Chatbot] floating chat widgetI just added the X button on the dialog top bar, it should be enough. Version 1.2.1
Forum: Plugins
In reply to: [Ask My Content - AI Q&A Chatbot] floating chat widgetThat’s strange. Pressing the
Escapekey should also close it.Forum: Plugins
In reply to: [Ask My Content - AI Q&A Chatbot] floating chat widgetJust click on the same oval “AI Chat” which is on the top left of the open dialog. I will also add a close cross icon…
Hi @sarahsas,
Quick update — support for additional post types has just been added.
Version 1.1.0
The plugin can now index other public post types (including WooCommerce products) in addition to pages and posts. There’s a simple setting to enable this, so you can include custom content types when needed.
That said, behavior may still vary depending on how a specific plugin stores its data. If the main content is in the standard post content field (as you described), it should work well. More complex setups (custom fields, special structures, etc.) may need further tuning over time.
If you decide to revisit this for another project, feel free to reach out — happy to help test specific post types.
Thanks again for your feedback and interest.
Hi @sarahsas,
Can you tell me which post types you want to support?
FYI, WP CLI command to show public post types:wp post-type list --field=name --public=1
Do you use some specific public plugin(s) to create your CPTs, or just custom-made?
Feel free to email to: info@pavelweb.com- This reply was modified 1 month, 3 weeks ago by Pavel Web Design LLC.
May be in March we can get to it. The main question is where custom posts store data which require indexing. Currently this plugin extracts data from WP_Post->post_content
Hi Lewis, thanks for the review, appreciate it!
Regarding having clickable links in the chat responses – the newly released 0.8.3 version has this feature.
Regarding “re-indexing must also be triggered manually” – automatic re-indexing was in the draft, but for now I decided against it due to performance. Say a 15000-token page has 5 small edits, this would cause re-indexing (re-embedding) of 75000 tokens, and removing/inserting of 150 DB rows. But we’ll see…