fooplugins /
foogallery
| Conditions | 4 |
| Paths | 4 |
| Total Lines | 18 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
| 1 | <?php |
||
| 27 | function attach_gallery_to_post( $post_id, $post ) { |
||
| 28 | if ( !class_exists( 'WP_Block_Parser' ) ) { |
||
| 29 | return; |
||
| 30 | } |
||
| 31 | |||
| 32 | $parser = new WP_Block_Parser(); |
||
| 33 | $blocks = $parser->parse( $post->post_content ); |
||
| 34 | |||
| 35 | foreach ( $blocks as $block ) { |
||
| 36 | if ( array_key_exists( 'id', $block['attrs'] ) ) { |
||
| 37 | $gallery_id = $block['attrs']['id']; |
||
| 38 | |||
| 39 | add_post_meta( $post_id, FOOGALLERY_META_POST_USAGE, $gallery_id, false ); |
||
| 40 | |||
| 41 | do_action( 'foogallery_attach_gallery_to_post', $post_id, $gallery_id ); |
||
| 42 | } |
||
| 43 | } |
||
| 44 | } |
||
| 45 | } |
||
| 46 | } |
Loading history...
The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.
The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.
To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.