updating the theme overwrites even the png files i had replace like the logo, also it delete all files in the directory like logo.png.original, also if i set non writeble permission the them wont update. Question: why don’t you update just the needed files? Question: A tutorial to make a child theme for the default DOWNLOAD THEME, i have modified some .php files and i wont re edit after every update.
Hello Nicola, Yes, unfortunately, updates do remove the previous directory.
Remember that it’s a good idea to use a child theme and avoid changing core files when possible, unless you’re comfortable trying to keep track and keep up with the changes.
If you need to use the built-in default theme without worrying about changing original files then try the attached plugin. I use it to clone an installed theme. Note: It is in beta since I haven’t finished adding the downloading of the saved archive.
Hopefully this topic will be worth of discussion:
According to WordPress rewrite in version 5 and up this comment comes from Codinwp:
How to Use the New WordPress Block Editor – Your WordPress Gutenberg Guide
Related to Themes in General, this is an excerpt from that report:
“Do you need a special theme to use the new Gutenberg block editor? Because it’s now the default WordPress editor, the block editor is built to work with any WordPress theme. However, choosing a theme that specifically offers Gutenberg compatibility will offer some very real benefits.
First, themes can offer built-in styling for all those new blocks. Better yet, themes can actually load these styles inside the editor. That means you can see the real styling for your blocks as you build your content for a better WYSIWYG experience (see a basic version of this in action here)
Gutenberg themes will also be able to offer pre-made templates comprised of various blocks so that all you need to do is plug your content into the existing blocks and hit Publish.
Additionally, there are some other small benefits like full-width image alignments. So – you can use whatever theme you want, but it is worth double checking to make sure that your theme’s developer is planning to add support.
If you just want to use a theme for testing, all of these themes have support for the new block editor:
Neve – Neve is our new theme that’s specifically built to work with the Gutenberg block editor. Zakra – a nice lightweight option from ThemeGrill. Atomic Blocks – available for free from Array/WP Engine. Hestia Lite – a flexible theme that follows material design principles. For more options, check out our collection of the best Gutenberg-compatible WordPress themes.”
We have been advised to use a Child Theme to make changes rather than using an actual Theme unless you are good at “coding”. We chose Theme and Child Theme models as a design featured framework where we could either use as default or make changes.
There are some of us that do NOT wish to make custom code changes to a Theme. We felt that by changing a Theme itself, that those changes would lock us in to having to rewrite code changes each time updates occur when needed. So, for those of us who chose to use a Child Theme to make changes in styling design by using custom meta data, we found that choice would serve us best. Zarko assisted us and was very helpful. He is now gone.
So here we are on the cusp of “Block” architecture requiring a total re-write to make Bootstrap Themes compatible vs. WordPress Gutenberg Block editor at our doorstep. Because of comments in PP forums concerning waiting for the Bootstrap Framework rewrite updates and ev there is No Schedule for CHILD Theme updates. Is that because there are not enough resources in PP to complete all of the updates needed?
We depend on the “Vacation Time” CHILD THEME being updated as one example, and Mark as said to us in response to our support ticket,that it will take “some time” for Child Themes to be updated. How long is “some time”?
This has given us the impression that because we had chosen to use Child Themes to modify that we will be waiting for “some time” down the road before we can update our site to take advantage of new WordPress 5 changes and therefore we must remain in PP’s v8 framework rather than keeping up with WordPress updates.
Hopefully some of the forum participants may feel that this should be discussed, and shed some light on our take, right or wrong, and try to confirm why it is worth the wait.
What if any particular Child Theme, such as ours, is not considered worthy enough for a v9 compatibility update? Then what would replace our present Child Theme? How much extra work will be needed to obtain the Child Theme Styling we already utilize in a particular Child Theme if ours is not updated?
@Nicola You’re welcome.
Thanks for sharing James 🙂
what about the plugin
Hello one 1, Info can be found here:
There are several options ,but the only input required is just the name for the created child theme.
Start your new website today!