Jeremiah

Thanks.. Fixed it for me too.

@evilmc You might want to check your own website:
https://dublue.com/plugins/toc/
Table of contents are also empty there…

• This reply was modified 2 years ago by Jeremiah.
• This reply was modified 2 years ago by Jeremiah.
• This reply was modified 2 years ago by Jeremiah.
• This reply was modified 2 years ago by Jeremiah.

chestile: You have several options here:

Option A: Categories (Easy)

You can separate articles using categories so that all your “whale” articles are displayed in the “whale” category and all your “shark” articles are displayed in the “shark” category.
See: Posts Categories Screen.

Only posts can be assigned categories (pages cannot be assigned to categories).

OR Option B: Multiple Blogs (Beginner)

As kulwant2home suggested, you can setup your “whale” WordPress site in the root of your website (~/public_html/) while setting setting up a separate “shark” WordPress installation in another folder (~/public_html/shark/) and create a subdomain that points to the “shark” WordPress installation.

See: Installing Multiple Blogs.

OR Option C: Multi-site installation (Advanced)

You can create a WordPress Multi-Site (MS) Installation. This usually requires the ability to configure your DNS records and this type of installation is slightly harder to configure and maintain.

See: Create A Network.

WildflowerRamblings: Sorry for the elaborate anecdote about my personal issues with the upgrade to 3.9. The main point I wanted to make is that I experienced the same issues you are describing here when I upgraded my WordPress installation using Softaculous’ auto updater (Softaculous is a plugin provided by many web-based hosting providers). If you have a similar situation, you may want to simply perform a manual upgrade by copying the files in the latest wordpress archive (latest.zip or latest.tar.gz) over your current installation. This solved the problem in my case.

I can confirm that esmi’s advice to re-upload the WordPress files helped in my situation but you should not have to delete any files and folders. Just replace any existing wordpress files from a fresh installation. The latest.zip and latest.tar.gz files do not contain the wp-config.php and .htaccess file anyways so unzipping/untarring them directly to your current wordpress installation (replacing exiting files) should be safe but always backup your wordpress installation (both files and DB) before performing this process.

I can confirm that esmi’s advice helped in my situation except you should not have to delete any folders or files. Just replace any existing wordpress files from a fresh installation. The latest.zip and latest.tar.gz files do not contain the wp-config.php and .htaccess file anyways so unzipping/untarring them directly to your current wordpress installation (replacing exiting files) should be safe but always backup your wordpress installation (both files and DB) before performing this process.

I performed the update from WP 3.8.3 to 3.9 using Softaculous interface in cPanel and after the update some functions of the visual/text editor stopped working. Disabling all plugins and activating the default 2014 theme did not solve the issue.

Turning on script debugging according to the instructions on this page https://codex.www.ads-software.com/Using_Your_Browser_to_Diagnose_JavaScript_Errors seemed to solve the issue but leaving my production WordPress installation with script debugging turned on does not seem ideal.

The problem seems to be that some legacy files are not being updated correctly by the Softaculous update script.

Make sure you create a backup of your original installation before trying to reinstall WordPress

To solve this issue, I installed a fresh wordpress installation to another (test) folder on my website and setup a subdomain to point to the new installation. Then I copied the original wp-content folder from the broken WP installation to the new test folder and exported the database from the broken installation to the new installation (updating the home and site options to point to the new subdomain). The new site worked fine including the editor was working correctly.

After verifying that WordPress was working with a fresh installation on the test site, I simply copied the contents of the fresh (test) installation folder into my original folder, replacing the original files (make sure you backup your wp-config.php file so you don’t accidently replace it with that of the new installation). After copying all the files from the new installation to my original installation folder, everything was working fine! (with all my original plugins and theme still activated).

This leads me to believe that the Softaculous update script missed some files during the upgrade process. I’m not sure if the same issue would occur if I ran the update script in WordPress directly or if I performed a manual update according to the instructions on this page https://codex.www.ads-software.com/Updating_WordPress.

So if you are using Softaculous and you experience this issue, you may want to try to perform a manual update of your WordPress installation (always create a backup before you do this).

I performed the update from WP 3.8.3 to 3.9 using Softaculous interface in cPanel and after the update some functions of the visual/text editor stopped working. Disabling all plugins and activating the default 2014 theme did not solve the issue.

Turning on script debugging according to the instructions on this page https://codex.www.ads-software.com/Using_Your_Browser_to_Diagnose_JavaScript_Errors seemed to solve the issue but leaving my production WordPress installation with script debugging turned on does not seem ideal.

The problem seems to be that some legacy files are not being updated correctly by the Softaculous update script.

Make sure you create a backup of your original installation before trying to reinstall WordPress

To solve this issue, I installed a fresh wordpress installation to another (test) folder on my website and setup a subdomain to point to the new installation. Then I copied the original wp-content folder from the broken WP installation to the new test folder and exported the database from the broken installation to the new installation (updating the home and site options to point to the new subdomain). The new site worked fine including the editor was working correctly.

After verifying that WordPress was working with a fresh installation on the test site, I simply copied the contents of the fresh (test) installation folder into my original folder, replacing the original files (make sure you backup your wp-config.php file so you don’t accidently replace it with that of the new installation). After copying all the files from the new installation to my original installation folder, everything was working fine! (with all my original plugins and theme still activated).

This leads me to believe that the Softaculous update script missed some files during the upgrade process. I’m not sure if the same issue would occur if I ran the update script in WordPress directly or if I performed a manual update according to the instructions on this page https://codex.www.ads-software.com/Updating_WordPress.

So if you are using Softaculous and you experience this issue, you may want to try to perform a manual update of your WordPress installation (always create a backup before you do this).

Any advice on the 2nd issue listed in this post? I am also experiencing the 2nd issue.

I would like to prevent users from changing their e-mail address but without the annoying “please enter an e-mail address” error notification.

Any advice would be appreciated.

Yes, installing the hotfix plugin solved the problem. Thanks!
I’m running in a production environment, but I’m not sure how to change the ‘display_errors’ setting? Can someone explain how to disable this setting. I have never changed it as far as I know so I suppose it must be a default setting that it is on?

I can’t edit the original post? Here is a link to the content of the WordPress post on Pastebin:

https://pastebin.com/F4x8tSS5

Esmi: I’ve tried on my host’s webservers, but I also installed a fresh, clean, install on my own PC at home to test if I had the same problem, and with no plugins and the default theme, the post failed to appear. So I think it is either a PHP bug, or a WordPress bug. I already contacted my Webhost and they didn’t have any idea about it.

Can you try it yourself. It happens even if you don’t have any plugins installed (or all plugins deactivated – doesn’t seem to matter much), and/or you are using the default theme, the post will not show up.

I wish I knew more about debugging this sort of thing, but I am not getting any error messages either. ?? This is super really frustrating – it’s not even a long post.

Is there any way the wp-content directory could become corrupt or perhaps the permissions on the directory have changed preventing wordpress from reading from the directory. Renaming or deleting the wp-content directory will also cause this to happen.

If you remove or rename the “wp-content” directory, then your homepage won’t show up at all. Just a white screen with no data (even the source page is completely blank with absolutely no html tags). You might want to check if this directory is in the wordpress root directory (where your wordpress files are served from).
On another note, I’m not sure this is the same problem, but my post doesn’t show up at all when I exceed a certain number of characters, or words.
I have tried:

1. Deactivating all plugins
2. Testing the same blog posts on different wordpress sites (same webhost, different domains – both using 3.0.4)
3. Installing a fresh version of wordpress on a different server (I installed 3.1-RC3 on a Windows server)
4. Using the default TwentyTen theme
5. everything else I could think of

In all cases, the blog post (just the blog content, but all widgets and sidebars are rendered correctly) doesn’t show up.
I’m wondering if someone can drop the following post into their wordpress site and tell me if it works for them:

[Code moderated as per the Forum Rules. Please use the pastebin]

Can anyone confirm this?