Ben Greeley

If you only have a handful of posts, then moving them over to each post individually would be fine. However, if you have many posts with many images, manually copying the wp-content/uploads folder would likely be quicker. If you have access to FTP with your hosting company, you could download the folder from site A, then upload to site B. Either way will get the job done!

@tabytharourke Your best bet is to ask in a support forum for the SSO plugin you’re using since it may be a configuration issue or bug. However, to add my own experience using an SSO plugin, I had a similar issue where users were created in WordPress from SSO and added invalid characters in the username. (eg, firstname.lastname) . Though it was saved, it created issues in other functionality, and I needed to create a fix for the issue so the user accounts would work properly.

I’m wondering if something similar is happening with email addresses. I’d recommend comparing the email address that should have been added with the user accounts that weren’t added properly and see if anything stands out, such as common characters or spacing that could be problematic. Again, it’s probably something specific to the SSO plugin, but I wanted to mention my experience.

@stephrookie You may want to ask in the Gutenberg support forum, but from what I can tell from reading the code, there isn’t a way you’d be able to do this without adjusting the block in a significant way.

I do want to point out that there is an ‘exclude’ parameter when you switch to the code editor and you can hardcode a list of post IDs to exclude from the list. I know it’s not dynamic or based on a tag, but it might help exclude specific content from your block.

It sounds like it would be a great feature request, I encourage you to make a recommendation to the Gutenberg support forum!

OK, assuming you have a custom screen you are adding the button to (instead of creating a block), you should be able to take the following steps to add some custom logic for your button:

1) When the button submits, I assume you want it to submit a form. Make sure your button has a unique name and implements a nonce for security.
2) Add a custom function into a hook that has the appropriate timing of when you want to fire your custom logic. For example, if you want to run your custom logic when WordPress is initialized, you’d set up something along the following:

function maybe_process_button(){
    // Check for the form field, either in $_POST or $_GET, depending on how it was set up
    // Check for valid nonce
    // If that field exists and has the expected value, then run your custom logic
}

add_action( 'init', 'maybe_process_button' );

3) That should do what you need to do for processing custom logic. If you’re trying to hook into existing admin hooks, you’d take the logic described and replace it with the specific action you are trying to target.

I hope that helps clarify how you’d be able to set the button up to work as you desire.

@stirdigital You may have luck asking your question in the Gutenberg support forum at https://wordpress.org/support/plugin/gutenberg/.

You could always update your custom CSS to work with the new structure (not ideal, I know). Another possibility is upgrading WordPress but installing an older version of the Gutenberg plugin from https://wordpress.org/plugins/gutenberg/advanced/ (scroll to the bottom of the page). This will let you lock into a specific version of Gutenberg while the rest of WordPress can be updated. Again, this is not an ideal solution, but it could buy you time to update your CSS to work with the new markup.

I wish I had more insightful news, good luck, and hopefully, the Gutenberg threads can point you in the right direction.

@hansvmourik Looking through your code, it doesn’t appear that you’re setting the metadata for the new posts (unless I’m missing something). You’re creating an array of $my_post for wp_update_post() which is good, but the metadata from the original post isn’t being set anywhere. When you use get_post() to get the original post data, it’s not grabbing the post metadata, as that function will only return a WP_Post object, which doesn’t include metadata.

I’d recommend to create a new variable on the line under $new_post = which does something like $new_post_metadata = get_post_meta( $post_id );. https://developer.wordpress.org/reference/functions/get_post_meta/ This will get all the post meta keys set for the original post and set them in a variable. Then any time you run wp_update_post() or wp_insert_post() you can either set an array element to $my_post that has meta_input set (as described in the comments section here or you can loop through the $new_post_metadata array elements and run update_post_meta() for each one. The former is likely more efficient.

I hope that helps!

Your best route is to carefully follow this guide. When you’re done, you may want to implement some (if not all) of the recommended security measures and start backing up your site.

I hope you’re able to get the site restored quickly.

@cynicalwebsite I’m sorry to hear your host was hacked and it affected your website. That can be very frustrating.

There’s a great explanation of recommended steps to take after a hack occurs at https://wordpress.org/support/article/faq-my-site-was-hacked/. You may have seen it already, but there may be some pointers there to get you up and running again.

I would think that getting your host to restore the directory and get things back in order would be the easiest. If you feel confident about troubleshooting, you could set your wp-config.php file to display errors since you aren’t able to access your error logs. That may give you more insight to what’s going on (though be sure to revert the changes once it’s resolved). You can add the following lines to your wp-config.php file to view the errors instead of outputting to a log:

define( 'WP_DEBUG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', true );

Good luck and I wish you a speedy site recovery!