Repository navigation
[Bug]: Old snippets typed as text instead of plain text #632
Description
Describe the bug
Some snippets created with older versions of massCode have their language field set to text instead of plain text.
When this happens, the language selector button is not visible in the editor.
To reproduce
- Open the local massCode database file (
masscode.db). - Find a snippet record.
- Manually edit the
languagefield to the valuetext. - Notice that the language selector does not appear in the editor.
App Version and Architecture
v4.2.2
System info
Windows 11Validations
- Follow our Code of Conduct
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion.
Activity
antonreshetov commentedon Nov 5, 2025
Which version did you upgrade from?
github-actions commentedon Nov 5, 2025
Hello @Mralexandresys. Please describe in detail the sequence of actions that leads to the bug (skip it if it's already there). Add screenshots of errors from the console. If possible add a video. Issues marked with
need reproductionwill be closed if they have no activity within 3 days.antonreshetov commentedon Nov 5, 2025
Manual database editing is not reproduction.
Mralexandresys commentedon Nov 6, 2025
I forgot to mention earlier that the application needs to be restarted between steps 3 and 4.
I’m also attaching a short video to demonstrate the test.
test.mp4
I’ve been using massCode for quite a while, and my snippet database dates back to when it was still using the JSON format (I was on version 3.x before upgrading to 4.2.2).
This might explain why, in my database, the defaultLanguage field in the folders table was stored as text.
Because of that, even after recreating a page, I couldn’t see the option to change the snippet language.
antonreshetov commentedon Nov 7, 2025
As I mentioned earlier, editing the database is a direct intervention in the application's operation and is not a valid way to reproduce an issue.
Version 4 uses the same list of supported languages as Version 3, which did not include text but rather used plain_text.
To resolve your issue, you can either manually set the required language or edit the database directly, since you have the ability to do so.
So I don't consider this a bug and am closing the issue.