Comments on: Custom CSS

By: PubSubHubBub — Matt Mullenweg

PubSubHubBub — Matt Mullenweg — Wed, 03 Mar 2010 22:15:38 +0000

[…] line well with WP.com’s goal of all its useful code being available to everyone, for example the custom CSS release. ¶ « OS Enemy of […]

By: ria

ria — Wed, 13 Jan 2010 07:11:26 +0000

This is great! I uploaded the plugin in one of my installations of WPMU.

By: Frederick

Frederick — Wed, 13 Jan 2010 01:08:22 +0000

A quick shameless plug for an old plugin I released: Simpler CSS enables similar functionality for older WordPress versions unsupported by the WordPress.com custom CSS plugin.

By: Ryan

Ryan — Wed, 13 Jan 2010 00:59:04 +0000

In reply to Matt. Lol. I thought that was a great idea of Jeff's :p

By: Jeffro

Jeffro — Wed, 13 Jan 2010 00:11:43 +0000

In reply to Matt. Wow that was quick. I'll stop bringing it up then :)

By: Matt

Matt — Wed, 13 Jan 2010 00:10:35 +0000

In reply to Jeffro. I think that's a terrible idea.

By: Jeffro

Jeffro — Wed, 13 Jan 2010 00:10:20 +0000

In reply to Matt. One last question, I promise. Do you think that taking the code editors out of WordPress and turning them into a 'Core Plugin' would be a good idea if the Core Plugin experiment is a success? The core plugin could be called CodePress and then have focused functionality built on top of it.

By: Matt

Matt — Wed, 13 Jan 2010 00:08:14 +0000

In reply to Jeffro. For theme files, probably, for plugins probably not.

By: Jeffro

Jeffro — Wed, 13 Jan 2010 00:02:04 +0000

In reply to Matt.

This is one step closer to your vision of not being able to break WordPress from within. At least with CSS, end users are protected and has revisions. Are revisions part of your long term scope for the plugin and theme editor when it comes to editing php files inside of WordPress?

Sounds like that would be the the holy grail of not breaking WordPress by accidentally editing files or making a mistake. However, I wonder how the php file editors would tackle the problem of restoring a revision if after you click the save button, you generate an error page. Common sense would dictate that an error would be detected and the last known good revision would be put into action.

Is anything I mentioned have a chance at becoming a reality at some point in the future?

By: Matt

Matt — Tue, 12 Jan 2010 23:51:51 +0000

In reply to Jeffro. Exactly. It's been out a few weeks I just forgot to blog it.

By: Jeffro

Jeffro — Tue, 12 Jan 2010 22:29:14 +0000

Better late than never but of course, you again held true to your word on making that feature on WordPress.com available to all as a plugin.

Loving the fact that I see the word revision being used. Does this mean that with this plugin installed, I could edit a CSS file, not like the changes and go back to a previous version easily just like I can with post revisions?