Matias Benedetto

Sorry It seems to be fixed in the latest version. Thank you.

I’m glad to hear that is working fine in the latest version.

It seems like it doesnt create the assets/images folder when overwriting the current theme.

I was able to reproduce the issue using the “Overwrite” option. The other options are working as expected.

I created an issue to work on this later: https://github.com/WordPress/create-block-theme/issues/309

Thanks for reporting this problem @islandscott !

I don’t use WordPress in English but in French maybe it comes from there

Nope, this is not related to WordPress internationalization but a pre-existing bug in the plugin.

The fix for this problem was just released as part of the 1.8.1 version of the plugin. Please, update your plugin version and try again.


I’m marking this as resolved. Feel free to create a new thread if you find other problems.

The fix for the original issue described by @abitofmind was released as part of the 1.8.1 version of the plugin. I’m marking this as solved. Feel free to create new threads if you found other problems with this!

Hi @rakhsh, thanks for reporting the solution you found.

Hi, @btollewp have you solved the problem too?

Hi @andrej_uduc, you need to remove the DISALLOW_FILE_EDIT definition or set it as false.

The plugin checks specifically for that setting to be defined and true to throw the error.

I’ve tried both options and none of them work (in the begining, this setting wasn’t event here).

This is interesting, could you double-check this, please?

Thanks @abitofmind for testing! The fix will be released soon in a new version of the plugin.

Hi ??! Thanks for reporting this.
There is a potential fix proposed for this issue. It would be very useful if you can try the fix and report again if it’s working as expected or not.

You can download the zip with the potential fix here.

Disclaimer: as this change is not tested and released yet, please, don’t use it on production sites. This is only suitable for test environments.

Can I just re-upload my “theme.json” file again, or will that overwrite important updates delivered in 1.1?

Hi @airwhale you can compare your customized theme.json vs the new TT3 theme.json to know what is different between both files.

You can do that with any text editor. If you want visual hints about the parts that are different, you can use a visual diff tool such as Meld.

If I change the?fontFamily?slug in?theme.json?from?Source Serif 4?to?BananaFont?everything works as it should. ?? WTH!!!

I’m glad that you made it work.

Also, note that Source Serif 4 looks like this on my computer:?https://imgur.com/a/alWzpd0, but only in Firefox, not Edge…

It if failing to display in google fonts and it works when you change the font name maybe you have a local copy installed not working as expected. Try adding another font family to see if it works as expected.

After adding the font what do you have in the “Manage fonts section”?

It would be very useful to have a screen recording showing how you add the font and the problems you face (font not appearing or whatever).

Hi @hartsook !

If there is an update of the theme, the changes you made to the theme.json file will be overwritten to get the new updated one.

If you want to avoid this, you can always create a fork of the theme by exporting or cloning it with another name, but in this case, you won’t receive theme updates on your forked theme.

To receive updates in your base theme, you can create a child theme and add your customizations to the child theme. For example: create a child theme of TT3 and add your custom set of fonts to the child theme. In this way, you will be getting the TT3 updates, and your custom configuration will always be there.

Hi @sg23838586 ,
.otf, .ttf, .woff, .woff2 font files are supported.

What error are you getting?
It would be helpful to have screenshots or a screencast of you adding the fonts.

Hi @abitofmind ,
just removing the variation JSON file is enough to remove the style variation. This is not specific about the plugin but about how WordPress works.

When you create a style variation using the plugin, all the style changes stored in the database are dumped into the variation JSON file and, after that, removed. So the variation data no longer lives in the database but in the JSON file. If you remove the file they are gone.

I’m marking this as resolved but feel free to ask if you have further questions.

This plugin is already good to create themes for live production sites.

The disclaimer “The plugin is for development only — it is not intended for use on production websites, but to be used as a tool to create new themes.” means that you don’t need to use the plugin on the production site. The plugin is to edit and export a fully working theme that you can use in your production site.

Let’s see a concrete example of a typical use case:
You are creating a theme for you or a client in you local computer using the WordPress site editor. When the theme is good to go, you export the theme using the plugin. After that, you upload that theme to your live production site and, that’s it. You have you theme working nicely in your live site.

Hi @andreslav

About this item:
” The font in the preview is incorrect.?Photo “

It seems like the font was not loaded correctly by the browser. It can happen for a variety of reasons.

– Is this happening only with Montserrat font?
– Have you try adding other google fonts?
– Are the fonts downloaded to your theme font assets folder (<your-theme-slug>/assets/fonts) ?
– Could you copy the fontFamilies part of your theme.json file?

Thanks!