adam/vscode-front-matter
1
0 Fork 0
mirror of https://github.com/estruyf/vscode-front-matter.git synced 2026-10-30 23:41:57 +01:00
Code Issues 77 Packages Projects Releases Wiki Activity

Issue: The search functionality works in VSCode 1.96.4 but breaks in 1.97 (Incorrect 'index' type error) #715

New Issue
Open
opened 2026-10-05 03:01:52 +02:00 by adam · 2 comments
adam commented 2026-10-05 03:01:52 +02:00
Owner
Copy link
Copy source

After upgrading VSCode from version 1.96.4 to 1.97, the search functionality in the Front Matter CMS plugin stopped working. In VSCode 1.96.4, the search feature works perfectly without any issues. However, in version 1.97, every time I input a search query to search for blog posts, the search fails.

Image

When checking the Runtime Status page of the plugin, I consistently observe the following error message after each search attempt:
Incorrect 'index' type.

Image

This issue appears to be specific to VSCode 1.97, as reverting back to version 1.96.4 resolves the problem, indicating a compatibility issue introduced in the newer VSCode version.

The plugin version I am using is 8.4.0.

After upgrading VSCode from version 1.96.4 to 1.97, the search functionality in the Front Matter CMS plugin stopped working. In VSCode 1.96.4, the search feature works perfectly without any issues. However, in version 1.97, every time I input a search query to search for blog posts, the search fails. ![Image](https://github.com/user-attachments/assets/042510a1-5a4a-440f-a11a-58b343b3cd9e) When checking the Runtime Status page of the plugin, I consistently observe the following error message after each search attempt: `Incorrect 'index' type`. ![Image](https://github.com/user-attachments/assets/54df2c2d-b78d-4790-a2a4-9c278d7eae59) This issue appears to be specific to VSCode 1.97, as reverting back to version 1.96.4 resolves the problem, indicating a compatibility issue introduced in the newer VSCode version. The plugin version I am using is 8.4.0. <!-- github-sync-id:2847296082 -->
adam commented 2026-10-05 03:01:53 +02:00
Author
Owner
Copy link
Copy source

Hi @HareToAme, is there a reason you are still on version 8.4.0? I would recommend to try out the latest version of the extension.

Hi @HareToAme, is there a reason you are still on version 8.4.0? I would recommend to try out the latest version of the extension. <!-- github-comment-id:2653021756 -->
adam commented 2026-10-05 03:01:53 +02:00
Author
Owner
Copy link
Copy source

I'm sorry for the delayed response, and thank you for your previous reply.

I have deployed a Hugo blog locally. I am accustomed to using this plugin to quickly retrieve documents and begin editing. Additionally, this plugin can automatically update the "last modify" field in the markdown front matter when I save.

Those are all the features I need. I don’t require any advanced functionalities, such as building or previewing the blog through the plugin. I usually build, deploy, and view it in a browser myself.

I started using this plugin in the first half of 2023, along with some automatic synchronization tools. However, since version 9.x, there have been some breaking changes—a few configuration files and paths seem to have been altered. Figuring out all the details of these changes and adjusting the exclusion settings in the synchronization tools requires a fair amount of effort, so I haven't updated it further.

To this day, the latest version of VSCode still hasn't fixed this issue, so I've permanently kept my VSCode version at 1.96.4.

I'm sorry for the delayed response, and thank you for your previous reply. I have deployed a Hugo blog locally. I am accustomed to using this plugin to quickly retrieve documents and begin editing. Additionally, this plugin can automatically update the "last modify" field in the markdown front matter when I save. Those are all the features I need. I don’t require any advanced functionalities, such as building or previewing the blog through the plugin. I usually build, deploy, and view it in a browser myself. I started using this plugin in the first half of 2023, along with some automatic synchronization tools. However, since version 9.x, there have been some breaking changes—a few configuration files and paths seem to have been altered. Figuring out all the details of these changes and adjusting the exclusion settings in the synchronization tools requires a fair amount of effort, so I haven't updated it further. To this day, the latest version of VSCode still hasn't fixed this issue, so I've permanently kept my VSCode version at 1.96.4. <!-- github-comment-id:3569367426 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/vscode-front-matter#715