umduck

Thanks, without the ability to control the settings networkwide in a multisite we implemented a code solution to automatically collapse the meta boxes by default.

Thanks, we’ll hold out until 6.7.2 has the fix applied. In the meantime is there a way to set the default nature of the SEOPress meta boxes to be collapsed instead of expanded. We have a large multisite and use your Pro version as well and our average user will only see the content area disappear without knowing they have to collapse the meta box area to see their content when editing in tablet & mobile.

Updated, tested, works as expected, thanks!

This was actually through the legacy widgets option. Thanks for the quick fix and release!

No problem, happy to help. Thanks for the prompt reply! We’ll look for the next update.

Thanks, that seems to be working for now. Looking forward to the update!

Whether my session is active or not it logs me out every 10 minutes. Very frustrating, may need to find an alternative solution.

I can confirm after testing on our test server that dismissing the notification does in fact dismiss it on the page you dismissed as well as anywhere else throughout the subsite on a multisite install. We will update our production environment to apply the fix. Thank you Mej!

We are experiencing the same issue as well, in Production and in all 3 of our test & development environments. It is quite infuriating to have to either live with the message because clicking dismiss is not permanent or clicking dismiss 100s of times over the last week on a multisite on every subsite we work on. At least we’ve disabled these nag messages for our regular users and it only shows for Admins otherwise we might have some explaining to do or remove the plugin all together.

I also think the new block options in the editor should be an opt-in feature not an automatic default as this is adding additional confusion for our current blocks as it inserts these options into the meta boxes of our current blocks which we never notified our users that this would show up out of no where.

We like the plugin and it has a lot of great features and I can’t wait to experiment with the block level widgets but until these bugs are fixed I am waiting before looking at the developer license.

• This reply was modified 8 months ago by umduck.

This feature was what set apart this plugin from other code snippet plugins for multisites. Unfortunately this has been broken for us for a very long time. There was an older version where this still worked, but IIRC it was as far back as 3.1 for us, will need to confirm on one of our testing environments. Fortunately we have not had to use it or write our code snippets to use an array of subsites to enable new functions through code instead of through the GUI.

We are still seeing this error happen on our staging & prod multisites and this is the corresponding fatal error 500 log entry:

2023/11/16 16:30:57 [error] 106374#106374: *19746 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught Error: Object of class Code_Snippets\Snippet could not be converted to string in /www/domain/public/wp-content/plugins/code-snippets/php/snippet-ops.php:245
Stack trace: 0 /www/domain/public/wp-content/plugins/code-snippets/php/snippet-ops.php(245): array_diff(Array, Array) 1 /www/domain/public/wp-content/plugins/code-snippets/php/snippet-ops.php(555): Code_Snippets\update_shared_network_snippets(Array) 2 /www/domain/public/wp-content/plugins/code-snippets/php/rest-api/class-snippets-rest-controller.php(270): Code_Snippets\save_snippet(Object(Code_Snippets\Snippet)) 3 /www/domain/public/wp-includes/rest-api/class-wp-rest-server.php(1193): Code_Snippets\REST_API\Snippets_REST_Controller->update_item(Object(WP_REST_Request)) 4 /www/domain/public/wp-includes/rest-api/class-wp-rest-server.php(1041): WP_REST_Server->respond_to_request(Object(WP_REST_Request), '/code-snippets/…', Array, NULL) 5 /www/domain/public/wp-inclu" while reading response header from upstream, client: 141.213.165.186, server: domain.com, request: "POST /wp-json/code-snippets/v1/snippets/1?network=true HTTP/2.0", upstream: "fastcgi://unix:/var/run/php8.1-fpm-rossweb.sock:", host: "domain.com:17905", referrer: "https://domain.com/wp-admin/network/admin.php?page=edit-snippet&id=1"

I am seeing similar behavior as @robaxxx I can now save the snippet, as choosing the Allow snippet to be activated option removes the activation button, however, it does not show the label as the other ones currently working on the network level that say “Shared on Network” and they do not appear on the other subsites to activate. Progress, but still not functioning as before. If we were to acquire licenses for all of our subsites on our multisite will this ensure we get dedicated support to resolve this issue quicker? We haven’t needed this option recently, however, at some point we will again and I really do not want to roll back dozens of versions to find one that still works? If you need access to a non-prod environment I’d be happy to provide.

Here is the behavior using the “Example HTML shortcode” currently deactivated.

1. When attempting to check the option “Allow this snippet to be activated on individual sites on the network” and then save without activating
2. Produces the error message at the top of the page that indicates “Could not update snippet. Request failed with status code 500”

Here is the behavior after activating the “Example HTML shortcode” code snippet.

1. Activation works as expected.
2. Attempting to check the option “Allow this snippet to be activated on individual sites on the network” and saving the currently active snippet
3. Upon saving it produces the same status code 500 message and deactivates the snippet.

This seems like a similar issue since 5.9 to this:
https://core.trac.www.ads-software.com/ticket/55067

When PHP files are accessed that are not intended to be accessed directly it throws an Undefined constant “ABSPATH” error or similar server error 500 issue on the server. It doesn’t sound like it is a big issue and more of an annoyance in the error log files. However, the problem is that it shows as a fatal error which doesn’t seem like a great solution to just ignore or handle at the server level vs properly coding to check & ignore direct non-accessible files.

• This reply was modified 1 year, 1 month ago by umduck.

This is the error that is being produced when you try to save the snippet with the network level option.

2023/09/20 22:32:30 [error] 82144#82144: *58916 FastCGI sent in stderr: “PHP message: WordPress database error Unknown column ‘revision’ in ‘field list’ for query UPDATE wp_ms_snippets SET name = ‘Example HTML shortcode’, description = ‘This is an example snippet for demonstrating how to add an HTML shortcode.\n\nYou can remove it, or edit it to add your own content.’, code = ‘\nadd_shortcode( \’shortcode_name\’, function () {\n\n $out = \’

write your HTML shortcode content here\’;\n\n return $out;\n} );’, tags = ‘shortcode’, scope = ‘global’, priority = ’10’, active = 0, modified = ‘2023-09-20 22:32:30’, revision = ‘2’, cloud_id = NULL WHERE id = 1 made by require(‘wp-blog-header.php’), wp, WP->main, WP->parse_request, do_action_ref_array(‘parse_request’), WP_Hook->do_action, WP_Hook->apply_filters, rest_api_loaded, WP_REST_Server->serve_request, WP_REST_Server->dispatch, WP_REST_Server->respond_to_request, Code_Snippets\REST_API\Snippets_REST_Controller->update_item, Code_Snippets\save_snippet” while reading response header from upstream, client: 76.112.223.179, server: somedomain.org, request: “POST /wp-json/code-snippets/v1/snippets/1?network=true HTTP/2.0”, upstream: “fastcgi://unix:/var/run/php8.1-fpm-rossweb.sock:”, host: “somedomain.org:17905”, referrer: “https://somedomain.org/wp-admin/network/admin.php?page=edit-snippet&id=1”

• This reply was modified 1 year, 2 months ago by umduck.