- This topic has 3 replies, 2 voices, and was last updated 13 years, 11 months ago by
.
Viewing 4 posts - 1 through 4 (of 4 total)
-
Posts
-
To avoid the future risk of deleting user custom css during plugin upgrades eme could first look for a file named something like ’eme.css’ in the current WordPress theme directory, and, if not found, for backward compatibility could then look for ‘myown.css’ in the plugin directory.
Et voila: implemented in trunk: if present in your theme CSS dir, eme.css is being included. The use of myown.css is being discouraged.
Thanks. That is a nice improvement. Memories fade over time and some people otherwise would be sure to forget about the need to save and restore myown.css.
Viewing 4 posts - 1 through 4 (of 4 total)
- The forum ‘Bug fixed or feature request implemented’ is closed to new topics and replies.