Matias Benedetto

This looks like an interesting and potentially useful idea, thanks for sharing it ??

It looks like a template cache problem. This is supposed to be fixed in the latest version of the plugin. Are you using the latest one?

Hi @jhmonroe the latest plugin version outputs theme.json version 3 when you create a new blank theme.

Hey! good to know. I’ll update the ‘testing to’ version asap. Thanks for testing!

Hi @fabbaigts40 what you describe seems to be related to be related with file permissions on your server and not with how the Create Block Plugin works. If you you a screenshot or better a video featuring the error it would be useful to help you to debug.

Hi @drivingralle, thanks for reporting this issue.
I just tried it and I couldn’t reproduce the error. I think it was already fixed in the latest version of the plugin. I’m closing this thread as resolved, feel free to re-open if the problem persists.

Hi @catalin-stoican, sorry for the late response.

I’m not familiarized with the antivirus you mentioned but I think it’s related to the fact that ‘Export Theme’ option downloads a .zip file containing the exported theme; I think that’s what seems suspicious for the antivirus software you are using.

If you don’t want or you can’t tweak the antivirus config, a workaround is to use the other plugin functionalities that doesn’t require downloading a zip files when creating new themes.

Hi @vytaulla51, which are the changes you are losing?

Export, Clone, and Child should have the same results. Export and Clone create new independent themes and ‘Create Child’ creates a child theme of the base one so it depends on their parent.

You choose the option it’s better for your workflow.

To help you more effectively about this It would be useful to know which are the changes you are loosing, an screencast video of the theme building process when you lost the changes would be useful to figure out what can be failing.

Hi @lancemonotone, thanks for reporting this problem.
Several changeshave been maded since you posted about this issue.Could you pleaseu check again with the latest version of the plugin?If the problem persists,t please report agait.

Hi @vytaulla51

Clones are “copies” of the base theme with changes, right?

Yes, when a theme is cloned all the templates, patterns, styles (theme.json) are copied on a new theme folder and the name and slug of the theme are updated from the old name to the new name. The result is a new fully independent theme. ‘Clone theme’ is a concept introduced by Create Block Plugin to describe that operation (copy and rename) but a cloned themes are not different to a regular block themes.

So when the theme comes out with updates, they’d apply, right?

No, cloned themes are new themes and they do not depend on the base theme. Cloned themes are not child themes so they are unrelated and not dependent on each other. The updates to a base theme used to create a cloned theme dosn’t have an effect on the resulting theme.

Note that this step (– Reset global styles again (just in case you had used the same theme name before)) was not possible as the Reset icon was dimmed, probably because I had not made any changes.

Yep! that’s right. If there are no changes the button is not active.

Success! Thank you so much. I really appreciate the speedy response and your persistence.

Excellent, I’m glad to hear that it’s working!
Thanks for the help debugging.
I’m marking this thread as resolved. Feel free to post a new thread if you have more questions.

I’m concerned that if I clone TT3 instead, that future updates to TT3 won’t be applied to my site.

Future updates, if any, will be only minor style bug fixes. I would not recommend creating a child theme in your case. It’s simpler to have a stand-alone theme and a child theme in this case would not add much value in my opinion.

Re-“clone the theme as a new theme” do you mean:

I suggest this path:
– Activate TT3 theme
– Reset global styles
– Clone TT3 with another name (Clone it as a new theme no need to create a child).
– Upload the zip of the newly created theme.
– Activate the uploaded theme.
– Reset global styles again (just in case you had used the same theme name before).
– Make some changes to the theme as addding a new font using CBT.
– Clone the theme with a new name and upload and activate it to test if it’s working as expected.

That’s all.
If it’s not working please share all the 2 zip files generated in the process suggested to continue debugging the problem.

Thanks!

Hi @darcey1 thanks for the .zip file! Very useful to debug the issue.

I found that the cause of the broken theme is the inclusion of some invalid font definitions coming from Jetpack in your theme.json file that are causing problems. I’m not sure why they are being added to the exported theme.json.

What is the cause of this problem?
I’m not completely sure but it seems that, for some unknown reason, you have some invalid font definitions in your global styles. I think that something useful to fix the problem could be resetting the global styles to the default in the theme you are using as a base.

Here you can see you do that: https://www.youtube.com/watch?v=HQCToOpJIqY

If you reset the global styles of the theme, clone the theme as a new theme, and upload it again I think it should work as expected. Could you try that and upload the resulting theme zip?

As an alternative and as a quick fix that maybe it’s useful for you, I removed the invalid font families definitions from the theme.json file of your theme. You can get the modified version of the theme you shared from this link.

Let me know how it goes.

Hi, @darcey1 I followed the advice from this answer you linked and the font management page worked OK for me.

Is this problem also happening when cloning, uploading, and adding fonts to other themes?

If this is just happening to the theme you created maybe there something else failing. In that case, are you able to share the .zip file of your theme ?

Thanks

Hi @ma_wordpressorg, @eharris, I’m not able to reproduce the issue you are describing. The font management seems to be working OK with 6.3.

To debug this, please try deactivating all other plugins apart from Create Block Theme and try again.

If the problem persists, please, reset your global styles to defaults like in this screencast: https://youtu.be/HQCToOpJIqY
After that try adding the fonts again.