Do we need a home on GitHub for these MU plugins?
We’ve got this one for restoring the generator tag and also the one for hiding twentyfifteen
, twentysixteen
and twentyseventeen
theme update notifications:
<?php
function cp_disable_theme_update_notification( $value ) {
if ( ! empty( $value ) && is_object( $value ) && is_array( $value->response ) ) {
unset( $value->response['twentyfifteen'] );
unset( $value->response['twentysixteen'] );
unset( $value->response['twentyseventeen'] );
}
return $value;
}
add_filter( 'site_transient_update_themes', 'cp_disable_theme_update_notification' );
1 Like
timkaye
February 10, 2020, 6:34pm
2
Should we develop a directory of gists as well as regular plugins?
2 Likes
james
February 10, 2020, 7:02pm
3
A GitHub repository should do for now.
We’ve already got enough on our plate for v2, but this could be something to consider for the future, probably starting as a plugin.
There’s also a related petition: Issues · ClassicPress/ClassicPress · GitHub
1 Like
I have done something along these lines with Classic Commerce snippets here, Snippets – Classic Commerce
It is just a simple categorized list that links to Gist code snippets. I do think that having them presented in some form of list or index makes them much more accessible. Note also that I have tested them all with Classic Commerce, so there is the added confidence factor over using something you just “find on the net”.
2 Likes