Twentig
Forum Replies Created
-
Hi Mario,
You can create your custom header template by overriding the Twenty Twenty-One files inside your child theme. In your case, you can copy the
twentytwentyone/templates/header/site-header.phpandtwentytwentyone/templates/header/site-branding.phpfiles (with the same folder structure) into your child theme folder. Then you can make your changes.Concerning the CSS, you should add it inside your child theme
style.cssfile or theCustomizer > Additional CSSpanel. You shouldn’t make any changes directly inside the Twentig files (PHP and CSS); the plugin updates would override your changes.Hope that helps,
TomHi,
Thanks for your feedback. I can’t replicate this issue, and this is the first time we encounter this issue. Unfortunately, as it’s forbidden for us to ask for any access to provide support, it’s difficult to diagnose the issue.
You said there’s a “compatibility issue between the plugin and Twenty Twenty (parent and child).”
Does it mean you are using a child theme? If so, please deactivate it, deactivate all your plugins, and use only the Twenty Twenty theme with Twentig to see if the issue is still there.Could you please send us your “Site Health Info”:
WordPress dashboard > Tools > Site Health > Info Tab > Copy site info to clipboardThanks,
TomThanks a lot! For the moment, there is no premium version of the Twentig plugin.
Glad it works! Thanks again for the feedback.
If you enjoy Twentig, please rate it. It would really help me out π
TomWe’ve just released Twentig 1.3.4, which includes the fix. The plugin will auto-update if you have enabled auto-update: https://wordpress.org/support/article/plugins-themes-auto-updates/#enable-auto-updates-for-plugins
The error message only appears when
WP_DEBUGis set to true. We’ll release the update in a few hours. In the meantime, you can set theWP_DEBUGconstant to false to make the error go away.Hi,
Thanks for the feedback.
We’re aware of this issue. We’ll publish a release today to fix it.
Have a nice day,
TomHi,
First of all, it’s always recommended to back up your database and files before changing your theme or updating WordPress. It will ensure that you can recover your website if anything goes wrong.
To be sure, you can try the theme switch on a local installation to avoid any problem on your live website.
Changing a theme shouldn’t make you lose your site data (posts, pages, images). However, if you’re using custom page templates or widgets in your old theme, they won’t exist with the new theme.
To use one of Twentig starter websites, you first need to change your theme to Twenty Twenty-One. Before activating the new theme, you can open the Theme Customizer to preview it with your content to see how it goes.
When loading a Twentig starter website, you can preview it in the Customizer. No changes appear on your live site until you click “Publish”.
You have different import types:
– If you select “All”, it will load the content (pages, posts, menus, widgets) and the Customizer style of the starter website. It will replace (replace and not delete) your old menu, so you’ll have to select your old menu as the primary.
– Or you can select “Customizer Style” as the Import Type to only import the style and not the content.
Hope that helps,
TomHi Arun,
To be sure, have you tested to deactivate Twentig to see if there’s no issue when using Generate Blocks Pro with the Twenty Twenty-One theme?
Twentig 1.3.1 had an issue with third-party block plugins, but it was only an issue within the block editor, not the front-end. So I don’t think that 1.3.3 will solve your issue.
Unfortunately, you can’t give us the pro plugin & access keys as it’s not allowed. WordPress forum rules only allow sharing an URL.
Thanks,
TomHi,
For some reason, WooCommerce overrides the theme’s CSS and removes the content top padding. To restore it on the “Twentig – No title” template, you can add the following CSS (Customizer > Additional CSS):
.tw-no-title #site-content .post-inner { padding-top: 5rem; } @media (min-width: 700px) { .tw-no-title #site-content .post-inner { padding-top: 8rem; } }Hope that helps,
TomHi,
Thanks for the kind words. Glad you like Twentig.
I don’t have the Generate Blocks Pro plugin, so I can’t replicate the issue. If possible, could you please share your page’s URL?
You said there is a conflict with Twentig 1.3.2. Does it mean there is no issue with Twentig 1.3.1? Could you please deactivate Twentig to see if there is no issue with Generate Blocks Pro and Twenty Twenty-One?
Thanks,
TomHi,
With Twenty Twenty-One, you can easily change the fonts using some custom CSS (Customizer > Additional CSS):
:root { --font-base: Arial; --font-headings: Georgia; }Hope that helps,
TomThanks for the feedback. After investigating, there was indeed a compiling issue. Weβve released Twentig 1.3.2, which includes the fix.
Have a nice day,
YannHi,
The cover template is a feature integrated inside the Twenty Twenty theme, it’s not a Twentig’s feature. Unfortunately, the blog page doesn’t act like a standard page, and you can’t apply a template on this page.
Have a nice day,
TomHi @ms416
Did you manage to edit βPowered by WordPressβ on the Twenty Twenty-One theme with Twentig?
Have a nice day,
Tom