Broken Theme on Sublime Text about vsc-material-theme

[FichteFoll]

As an immediate action to mitigate user setups breaking, I have removed the "Material Theme" from the Package Control package index (see wbond/package_control_channel#8646). It will be gone from the cache within the next hour and won't be updated for any users anymore.

To this date, the package is the 12th most installed package on Sublime Text despite it not being maintained for 6 years because it supposedly never broke (since ST aims to maintain backwards compatibility for quite some time) and is probably recommended in many places such as articles. Removing a working package "just because it's not maintained" is outright rude to say the least. There would have been better ways to handle this, such as archiving the repository instead. It's not like people looking for a Sublime Text theme would be happy when they instead were redirected to a VS Code theme and vice versa.

[raphaelsk]

My quick read is that the repository with the Material Theme for Sublime Text has been deleted (or made private), and Package Control was updated to point to this VS Code theme repository. Package Control then auto-generated a zip/sublime-package from this VS Code repo, and all our machines auto updated.
Sadly, VS Code themes do not (generally) work in Sublime Text.

[lxShaDoWxl]

Тоже столкнулся с этой проблемой =(
Решил её с помощью ручной установки пакета в subl, скачать пакет можно тут
https://github.com/lxShaDoWxl/material-theme/releases/tag/v4.1.5

[vanyamil]

For those interested in restoring it:
First, go to Sublime and disable auto-updates and install-missing options in Package Control settings

	// If packages should be automatically upgraded when ST starts
	"auto_upgrade": false,

	// If missing packages should be automatically installed when ST starts
	"install_missing": true,

Then, put the file linked above in the location of your packages. On Windows, it's in %appdata%/Sublime Text/Installed Packages

[open-collective-bot]

Hey @vanyamil 👋,

Thank you for opening an issue. We will get back to you as soon as we can. Have you seen our Open Collective page? Please consider contributing financially to our project. This will help us involve more contributors and get to issues like yours faster.

https://opencollective.com/material-theme

We offer priority support for all financial contributors. Don't forget to add priority label once you become one! 😄

[ADDISON74]

@mallowigi - I do not in any way force the author to continue the work. On the contrary, I respect it but the approach was totally wrong. To start ST today and have error messages, deleted files, to be asked to make changes, was not ethical at all. Was it difficult to publish a message and leave the package in unmaintained? I think he had more to gain, he would have received many thanks.

However, let's not forget that the success of Material Theme was also due to Sublime Text users. There are tons of articles about Sublime Text where this package is mentioned. I did not like the statement of the author from today on Twitter "Is enough". Maybe the programmers should also take communication courses.

[Aldaviva]

For those interested in restoring it: First, go to Sublime and disable auto-updates and install-missing options in Package Control settings

	// If packages should be automatically upgraded when ST starts
	"auto_upgrade": false,

	// If missing packages should be automatically installed when ST starts
	"install_missing": true,

Then, put the file linked above in the location of your packages. On Windows, it's in %appdata%/Sublime Text/Installed Packages

Alternatively, if you want to prevent Package Control from auto-upgrading just this package instead of all your packages, you can set auto_upgrade_ignore in %appdata%\Sublime Text 3\Packages\User\Package Control.sublime-settings:

"auto_upgrade_ignore": [
    "Material Theme"
],

[ADDISON74]

I confirm the issue. Reinstall in vain because Package Control no longer gets all the files necessary to run. It is inadmissible under the pretext of lack of maintenance to generate errors in use based on deleting files. There are tons of ST3 packages that are no longer maintained, but no developer has acted like the Material Theme team. even if it is a proprietary code, what happened today is not ethical towards all users of this package. I will uninstall it and I will stop using it in other IDEs even if it is maintained (Visual Code, Phpstorm).

[kevnk]

Here's what worked for me (combining a couple of the comments above, plus I'm adding some details from the old README.md):

1. Add Package Control settings to not auto-update this package (see this comment)
2. Download https://github.com/lxShaDoWxl/material-theme/releases/tag/v4.1.5 (thanks to this comment)
3. Unzip and Rename folder to "Material Theme" and place in "Packages" folder (Readme instructions)
4. Open command panel and type "Material Theme: Activate Theme" (Readme instructions)

[ergonomicus]

Nobody is blaming the author for not wanting to continue managing a plugin, it was a case for years now, but he could just leave it as it was yesterday, right? We are here to rant, so either join or move along. :)

[ergonomicus]

Here's what worked for me (combining a couple of the comments above, plus I'm adding some details from the old README.md):

1. Add Package Control settings to not auto-update this package (see this comment)
2. Download https://github.com/lxShaDoWxl/material-theme/releases/tag/v4.1.5 (thanks to this comment)
3. Unzip and Rename folder to "Material Theme" and place in "Packages" folder (Readme instructions)
4. Open Package Control panel and type "Material Theme: Activate Theme" (Readme instructions)

Exactly what I did, everything is back to normal now.

[Gerst20051]

You can update to use the Materialize package instead! Enjoy!! 🕺 🚀 🔥

https://github.com/saadq/Materialize
https://github.com/saadq/Materialize-Appbar

Package Control.sublime-settings

{
	"installed_packages":
	[
		"Materialize",
		"Materialize-Appbar"
	]
}

Preferences.sublime-settings

{
	"color_scheme": "Packages/Materialize/schemes/Material Oceanic Next.tmTheme",
	"theme": "Material Oceanic Next.sublime-theme"
}

[DroidFreak32]

Тоже столкнулся с этой проблемой =( Решил её с помощью ручной установки пакета в subl, скачать пакет можно тут https://github.com/lxShaDoWxl/material-theme/releases/tag/v4.1.5

Gotta love Open Source for this very reason! Theme is now restored, thanks!

[mallowigi]

I too believe that he could have better communication with his users but you have to know one thing: he, or me for that matter, have no obligations towards other people. It was always clear that this project or any open source project, could stop anytime. It would be bad for the reputation of the author, yes, but if it's something he is ok with, there's nothing you can do about that.

Fortunately you can fork the project and build your own version, especially if the author cannot provide his own alternative. That's what people did in vsc and provided a "community theme" to fork from the author's theme.

It's a difficult day, I'm also a user of the MT for the days I use Sublime and I will always be grateful to Mattia for what he did. But all things come to an end and you have to respect that.

[colethorsen]

I'm having the same issue. I'm guessing an auto update happened, there was an error message that flashed up, and then the color scheme reverted tot he default. The material theme is removable and re-installable but the themes are no longer listed.

[User123698745]

Also stopped working for me on Sublime Text 3. I got this error message:

The package containing your active theme was just upgraded, however the .sublime-theme file no longer exists. Sublime Text has been configured use the default theme instead.

[Atdit]

Also stopped working for me on Sublime Text 3. I got this error message:

The package containing your active theme was just upgraded, however the .sublime-theme file no longer exists. Sublime Text has been configured use the default theme instead.

I also got the same error on Sublime Text 4 on Arch Linux, installed via the AUR package. Reinstalling the theme or the whole Sublime Text package didn't help.

[ervilsoft]

Same issue here.

[Brugman]

Same issue. Please undo this.

[lexakimov]

Got same issue.

[Krukar]

They won't be fixing this: https://twitter.com/materialtheme/status/1598567199756656640

[yangchen5710]

Same issue. Please undo this.

[mallowigi]

The JetBrains versions of the plugin is not affiliated with this theme or the author in any way.

Besides, plugin depreciation is a thing. Don't blame the author for not wanting to continue managing a dead plugin. Either fork it or move along. There are plenty of other themes available.

[karolyi]

@FichteFoll, thanks for the quick fix.

I was also totally surprised by my theme breaking today when getting the "autoupdate". This is not a way to deal with open source development. The old package should have stayed untouched, with an end-of-life notice added to it.

[karolyi]

Materialize, as mentioned in #1256 (comment), seems to be working nicely though. I encourage everyone to just start using the themes available therein.

[audetcameron]

I too woke up to a broken theme in sublime text build 4142

[equinusocio]

We never saw so much feedback and user activity during the whole life of the project (10 years).

Seven years ago, we deprecated the project, informed everyone, and since then, we have been focused on the vsc version. Deprecation means moving away from it asap; we think seven years are enough, and we don't want to provide harmful software anymore (many dependencies of that project had/and still have security issues).

Then, open source doesn't mean work for free, and since we get paid and supported by the extension for VsCode we want to focus on that as the main project.

Material Theme for sublime is not a package. ST plugin system relies on repositories. So even if we just renamed the repo or picked another git service would have been the same.

Lastly, we just transferred the popularity of the original theme to the main one for vs code.

That’s all, folks. Gently remind don’t use recovered repositories since that project includes vulnerabilities.

I am closing this since it is not a bug or the right place. For questions, there is the discussions page.