jon

The best place to start is with your hosting. They should have a recent backup that you can restore. You will need to restore both the files in the WordPress directory (and all subdirectories) and the WordPress database.

All good advice. Every WSOD I’ve ever experienced suddenly became a lot easier to fix once I turned on WP_DEBUG and WP_DEBUG_LOG with statements like define( 'WP_DEBUG', true ); in wp-config.php. The log appears in /wp-content/.

Official Codex doc. on WSOD is here: https://codex.wordpress.org/Common_WordPress_Errors#The_White_Screen_of_Death

To simplify the /wordpress/ to look at root of domain problem, this works the best: section “Using a pre-existing subdirectory install” at https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install though obviously not until you have WSOD fixed. You may even want to get WordPress initially working by setting its URLs to include the /wordpress/ subdirectory and switch later to make all the hard-coded URLs on Pages and Posts work. Change URL is described here: https://codex.wordpress.org/Changing_The_Site_URL

As with all things computer-related, Backup is the key to addressing your fears. Backup both the files and database used by WordPress.

Then you can try the Updates and restore from backup if they don’t work out.

But, people do updates all the time and don’t lose data from their site.

This is an issue with Encoding, which phpmyadmin refers to as “Character set of the file”.

You must export and import with the same Encoding. You can also run into problems if the database tables do not correctly specify the “Collation” as phpmyadmin calls it. WordPress prefers Collation to be utf8mb4_unicode_ci

Admittedly, I have no experience with non-English character sets, so there may be other issues, but I would start with re-doing the export and import, making sure that the Encoding matches.

First, I will admit that I never use Caching in WordPress, which would likely make my past problems less of an issue. With that said…

In my experience you need at least 1.5GB of RAM, and possibly 2GB, to run even a medium traffic WordPress web site with more than a few plugins.

You specifically mention Admin panel slowness. Admin panels take about twice the RAM of public parts of a WordPress web site.

And, yes, all of my VPS experience has been Ubuntu.

ref. – https://codex.wordpress.org/Shortcode_API

What you have displayed is not incorrect, just unnecessary. It is the function for [shortcode-activate] that needs to handle nested Shortcodes. It would become something like this:

add_shortcode(‘your_initials_shortcode_activate’, ‘your_initials_shortcode_activate’);
function your_initials_shortcode_activate( $att, $content ) {
    $content = do_shortcodes( $content );

• This reply was modified 9 years, 7 months ago by jon.