WordPress 3.3.1 is now available! :yipee: Will you update? :67: The last time I updated my to 3.3 I had problems. I saw the update the moment it was released but I didn’t update it yet because I was scared that something might happen to my site. :73: After a few days, I decided to update, voila! I was right! :93: My site was ruined. I struggled fixing and did everything, but in the end, it was my old host that was able to fix it. :4: This time, I have a new host. A more accommodating and knows my needs. I haven’t updated yet and I am planning to wait until I can talk to my host. I don’t want to see the scariest words: FATAL ERROR! NO WAY! :71:
How about you? Are you going to update now? Or have you updated? :9:
I decided to check WordPress.org’s site about WordPress 3.3.1 to find out why there was an update so soon and what’s new with WordPress 3.3.1. :51: I found out that the update was released to fix 15 issues. These were the issues:
wp_print_styles() causing mid-page scripts/styles to bleed into admin
Multi-site Upload Limit Stuck at 50MB
Wrong widget count on dashboard
Multisite: No Database Prefix causes strpos(): Empty delimiter
Never show two flyouts at once
$userdata not populated properly
Toolbar shows a warning on a second call
Unwanted backslash in output
Users list ‘Change role to’ allows for changing logged-in Admin role to Subscriber
current-menu-item and current_page_item classes incorrectly added to custom menu items with no URL value.
Remove .button styling from _default_wp_die_handler()
Press This #message is ugly (3.2 to 3.3 regression)
Quick Edit/Reply missing tabindex causesto miss Update Comment/Reply button
Script Loader dies in 3.3 on no-JSON PHP
read more at: http://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=3.3.1&group=resolution&order=priority
The words used were a little bit techy. :57: I don’t even understand some of them. :38: I mean most of them! Hahaha. They should not have used jargon. Anyway, “Unwanted backslash in output” is one of the words I understood with the issues, and this issue was also my issue last time. I was editing and editing the post and the slash kept on being there. UNWANTED. Hahaha. I decided to disregard it. Glad they were able to fix it now. Unfortunately, I haven’t updated it so I wont enjoy it yet. :cute: Will wait for my host, I don’t want to see the two words again: FATAL ERROR. :argh:
Leave a comment on how was the update. :20:
POST UPDATE!!!!!!
I suddenly remembered! I updated the plugins before the WordPress 3.3 that’s why I had fatal error. Okay… After updating this post, I will now update my WP. I was just advised by my host to update or be hacked! :yipee: Hope everything will turn out okay! :strawb:
Leave a Reply