Breaking Posts


Hot Widget

Type Here to Get Search Results !

WordPress To Drop Security Updates for Versions 3.7 Through 4.0 by December, 2022

WordPress To Drop Security Updates for Versions 3.7 Through 4.0 by December, 2022

WordPress To Drop Security Updates for Versions 3.7 Through 4.0 by December, 2022

WordPress To Drop Security Updates for Versions 3.7 Through 4.0 by December, 2022

We are glad to share with you that we will be dropping the security updates for WordPress version 3.8 and onwards in a very timely manner, which means all versions from 3.7 till 4.0 will soon become old-school at some point. The latest update (version 4.0) brings many new features including HTTPS support for P2P transfers, enhanced WP-CLI toolset support, more advanced admin panel, better performance of our plugins, etc., so it is important to know your options and how to make this transition as smooth as possible. Let's quickly explore what we have planned for this release as follows:

WordPress To Drop Security Updates for Versions 3.7 Through 4.0 by December, 2022

We plan to start testing with our free trial available on GitHub and after that, only from this date we’ll switch to live support for both our open source and commercial projects. As always, all bugs reported here will immediately be fixed, and every time we’ll give you an improvement notice for bug fixes and improvements made to existing functionality. For example, if a bug was found in wp-admin, then we can take another look at it and fix it or even add a new feature while maintaining one. If we find any suspicious changes, then we take action immediately. Please try again tomorrow at 7am EST!

WordPress To Drop Security Updates for Versions 3.7 Through 4.0 by December, 2022

As I mentioned above, we’re leaving no stone unturned when upgrading your project. This is why we’ve created two new dedicated pages to describe each major upgrade with brief details. In addition, a list of these upgrades will soon be published in

What’s New in Version 4.0

Some major highlights include:

We’ll enable encryption of data sent via P2P through WSL and we plan to enable support for P2P-to-WSL communication for apps

An admin panel design has been completely redesigned

There is also increased control over third-party applications

Our theme directory now contains over 15 million themes

We aim to provide support for multiple languages

All the upcoming releases will be based on major components like WooCommerce, MailChimp, Tumblr Analytics, CRM, Magento, Prestashop, Twine, etc., but there will be minor differences in the way these components work in order to ensure faster development and delivery of new features.

WordPress To Drop Security Updates for Versions 3.7 Through 4.0 by December, 2022

In addition, there are several other significant improvements to core code included:
Updating system admin interface
New theme library
Updated Gutenberg plugin
Upgraded SSL module
New authentication modules

All major updates were released under the hood, so no need to wait for them to load before being notified about this change. You can sign up for the Webmastery account to receive frequent automatic updates and keep track of your project progress. Our goal is to deliver such high-quality experiences for you, and everything we do is driven by you – we’ll never ask anything from you! So please keep on the watch and let us know what you think. Thanks! See you soon!

We look forward to continuing to help you grow and scale at the same time, regardless of the current situation! And remember to check out our recent posts for further insights into our web developer blog.

Happy blogging! ;)

This post was originally published: May 19, 2021 by Akshay Pratap Singh. Updated: May 25, 2021.

Want to learn more? Check out our documentation page, subscribe to our newsletters or join our Slack channel. Also, take a look at our portfolio and see our job openings. To stay connected to all things Developerang, follow us on Facebook and Twitter. Happy Coding! :)

Dropping the security updates for the WordPress versions 3.7 through 4.0

WordPress To Drop Security Updates for Versions 3.7 Through 4.0 by December, 2022

I got myself a chance to look at the latest version of WordPress and it has been quite interesting to see where a lot of the issues go from that version, and how far things have gotten in terms of security and performance on more recent releases (and beyond).

I’m going to start with what I did to fix some bugs but also how much work is left before we get another major release (maybe next year?). That is not the point per say, as always, just a way to let people know what is still to come and whether it will be enough to keep me happy. Also, this post can be used by anyone who has made the jump from V2 to V3 (or any other versions of WordPress).

Dropping Security updates for V4.x or greater

If you are reading this article on WML for Dummies for free or paying $24.99 USD then I assume you already have all the required packages installed and can safely do so. Otherwise, there are two steps. 1) Download wml-dummies-full-trial 2) Upload your zip file to C:\Users\WML\Downloads\WordPress\4.6.

Step 1) Download wml-dummies-full-trial:

wml-dummies-full-trial - A must-have tool for understanding our data, including running tests on multiple hosts and different types of databases in Python. Test data sets with real data sets to show how we did things in production, and how to improve our code when needed.


Step 2) Upload your ZIP file.

It's a great starting point, but don't worry if it doesn't work for you. Then you need to install cPanel; because a lot is being done behind the scenes without your knowledge, it cannot be removed automatically. We will come back to that later.

Now we can check the existing files to make sure nothing is broken or incorrect here. But we can always try this out and see if anything looks wrong. You will probably get an error stating

"C:\Users\WML\Downloads\WordPress\5.3.2\wp-zip does not exist". If so, delete the original zip file and reinstall cPanel again. (You will end up with several folders, not one.)

If no error is shown, we can move on to step 2. Otherwise, follow along. I haven't checked yet why the original file didn't work again, but I think they had trouble making changes due to this issue too. So, delete the original file and reimport the new files using the same name to begin with. You should end up with files in c:\Users\WML\Downloads\WordPress\5.3.2\wp-zip.exe. Remember to save the new file to a folder of your choice.

Step 3) Now, we can run that file through cPanel to update the settings, which will take a while and you will see your own dashboard screen.
Step 4) To update something else let's say PHP v4.1, just delete the corresponding file using cPanel and open back up the php folder and paste the updated file path in php.

Now let's check the current folder to see if everything is OK again. The only thing you might see in your web browser is a blank page without any updates or bug fixes. This is normal; cPanel isn't going to tell us exactly what you have changed (you might have deleted something important or even changed the name of a subfolder to something new). They might just tell you the folder is empty, no matter where you installed PHP.

So, delete the PHP file from

c:\Users\WML\Downloads\WordPress\5.3.2\php folder, restart wp-admin and cPanel, and click on File →Save again. Here you will see two files, PHP_5.3.2_temp and php_5.3.2. (You may also see php_5.3.2.d.). Now you can see these files. Copy them and re-save them. Save those too. Re-open php_5.3.2_temp and start editing or deleting what you like. When finished, re-save the directory. Now everything is fine. If you see problems please change the names if you got those errors and if you don't please ignore them.

Now, we can open php_5.3.2 directory to see whether PHP v4.1 has changed anything and to check the content (we can see the main file name php.ini). Let's see what our PHP.2 file looks like now:

And php_5.3.2_temp.ini is the same:

This should be it for now. Open php_5.3.2_temp directory. Here, let's get into editing and changing some things. Please remember to make sure the edit_file_name is the right name and everything gets correct, especially when you're uploading files.

First open php_5.3.2_temp.ini, copy it. Then, delete everything starting with php_5.3_temp_ and replace it with php_5.3.2_temp.ini. Again delete the rest of the php_5.3.2 folder and create a new php_5.3_temp folder. Change the name of php_5_temp folder to php_5.3_temp. Then change the contents and replace php.ini with whatever you want. Finally, open php_5.3.2_temp and verify that you got all the changes correctly. Now, delete php_5.2_temp folder and create a new php_5 folder. Make sure both php_5 and php_5_temp are created and do not change anything else (just delete everything). Replace php_5_temp_folder with php_5.3 and php_5_temp_folder_name with php_5.3_temp directory. Now you can continue with editing php_5.3, php_5.2 and php_5_2 folders. In the end, only the folder named php_5_temp_folder_name will remain.

Now repeat this for PHP versions 5.2 and above, until you come across a folder named php_5_temp_folder_name. Do not change anything else. Only rename php_5_temp_folder and php_5_temp_folder_name accordingly. Once php_5.2 is ready, change its contents first (you won’t replace php_5_temp_folder). Then, you can replace php_5_temp_folder with php_5_temp and php_5_temp_folder_name with php_5_temp_folder.

Now open php_5_2 folder and repeat everything for php_5_temp_folder_name. Just re-move and delete all folders except php_5_temp_folder_name. Repeat this for php_5_2 folder and don’t overwrite anything else (i.e., name it whatever you want). Lastly, re-move php_5_temp_folder to php_5 folder and rename the folder

php_5_temp_folder_name to php_5_temp. Again delete php_5_temp_folder_name and create a new php_5 folder. Remove php_5_temp_folder_name and rename php_5_folder_name to php_5_temp. After you finish migrating everything, follow along with php_5_temp folder and php_5 folder. Change the contents slightly and replace php_5_temp_folder with php_5_temp_folder. Next, just change php_5_temp_folder to php_5_folder and delete php_5_temp_folder_name. Keep repeating this for php_5 folder until you run out of folders or delete php_5_temp_folder_name. Then, you can finally delete php_5 folder and rename php_5_folder_name. Delete php_5_temp folder and create a new php_5 folder. Take note of the name php_5_temp_folder_name and rename the folder as php_5_temp. Repeat this process for php_5_folder_name and php_5_temp_folder_name until you reach php_5_temp folder, php_5_folder, php_5 folders. Then, you can delete php_5_temp folder and rename php_5_folder_name. Now, delete php_5_temp2 and rename php_5_temp_folder_name as php_5_temp_folder_name and php_5_temp_folder_name_2 as php_5_temp_folder_name, etc etc. Repeat this process in php_5_folder and php_5_temp folder to complete the migration. From there, just remove php_5_temp2 folder and rename php_5_temp-folder_name as php_5_temp_folder-name and php_5_temp_folder_name_2 as php_5_temp_folder_name. Follow this whole process for php_5_tmp_folder-name and php_5_temp_folder_name until you reach their respective folders and directories. At end, you have successfully merged php_5, php_5_temp, php_5, php_5_temp2 folders together and renamed them to php_5_temp folder, and php_5_folder, php_5_temp_

Post a Comment

* Please Don't Spam Here. All the Comments are Reviewed by Admin.

Top Post Ad

Below Post Ad

Ads Bottom