Docs

[nillamary]

Just installed and activated X (Parent) and X (Child) with the displayed successfully ‘installed and activated messages’. However, my Child folders are empty (see screenshot). The only files I have in the Child root are: framework, functions.php, screenshot.png, style.css (see screenshot). I would have expected to see all the Parent files and folders replicated in the Child theme. Has my Child installed correctly? My Host is InMotion.
Many thanks!

[Paul R]

Hi,

Yes, that’s correct, the child theme is basically empty.

You only need to copy the file that you want to modify, not all.

Kindly review the link below.

https://community.theme.co/kb/customization-best-practices/

Thanks

[nillamary]

Sorry, I’m new and completely green so when you say “copy file you want to modify”, are you talking about Stacks and do I copy all files within the Stack’s folder?

[nillamary]

I’ve read your above link. So is there an issue if I copy the whole stack across to my Child? How do I import a Stacks demo into my Child?

Also, when X is updated in the future and I want to include some of the new features in my own website, do I copy those files across?

[Joao]

Hi There,

You don´t need to do anything beside what you have done unless you want to make changes to your theme that require template changes, that is not unusual, but also not a rule, I personally never even use a Child Theme since I don´t do this types of modifications often and I believe you probably won´t require that as well.

Let us know if you need further help.

Joao

[nillamary]

Thanks but you haven’t answered my questions:
1. Do I copy all of a Stack’s file from my Parent to my Child?
2. How do I import a Stack’s demo into my Child?
3. When X has a future update, how do I update my Child if I need to? Just copy specific new files across from Parent to Child?

I believe I will need a Child theme as I will be making some template changes and I do not want my site overwritten with any future X theme updates.

[Joao]

Hi There,

1- You copy a specific file in case you want to make modifications to your theme that cannot be made trough the dashboard, other wise you do not and should not copy anything.

2- There is no relation between those things, Once you activate your child theme it will use the files of the parent theme so there no need, you simply go to WP Admin Dashboard > Addons and choose any demo.

3- The function of a Child theme is that when X has a future update it won´t overwrite your change.

Please take a look at :

https://www.youtube.com/watch?v=s09SIxyO4ho

Note that X is highly customizable without the need of changing “template files”(.php files that you find inside your X Theme)

There is no harm on using a Child Theme. But if you installed it and actiaved on your WordPress Dashboard, you are already good to go, and you will just need to copy files there in case you want to make changes that are not possible to be made trough WordPress Dashboard.

The most common functionality is people to use the style.css in the child theme to write css code, I personally use Appereance > Customizer > Custom > CSS to write my CSS code.

Let us know if you have further questions,

Joao

[nillamary]

Excellent! Thank you for answering my questions and the video link.

After an hour’s searching, I did find this link and imported the demo successfully: https://community.theme.co/kb/demo-content/

Now that the demo is imported, is it best practise to:
1. Import all plugins I think I’ll need (Woocommerce, etc.) up front and then start customising the design
or
2. Start customisation the Demo then import plugins as I need them?
Thanks again

[Joao]

Hi There,

Don´t import all the plugins, it will make your site heavier and there is plugins that don´t have use together, for example you need to choose to use Ubermenu or Superfly, you cannot use both…you also don´t need to use them at all.

If this is your first website, first of all, I would recommend you looking for example around the internet of what you want to build, defining a layout and “copying” or getting inspired by a layout, it is much easier than create everything out of the box and usually will bring you better results at the end.

Thank on our knowledge base you could check what the plugins we offer do and if they suit you, some plugins are really easy to use, some other, like any tools, demand you understanding how they work and it can be time consuming, so it is important to decide if you actually you want to use them before trying to master them.

Another good way to have a look on the plugins is to put their name in google, go to their original page and see the live preview.

This is my personal tip: less is more 🙂 classic isn´t? But well, it works, I guess the most important thing when building a website with X is to master the Customizer, customizer is not a plugin you will find at WP Admin Dasboard > Appereance > Customizer, over there you will setup the general style of your website, colors spacing etc..

Regarding WooCommerce, if you would like to have a webshop it is the way to go, specially if you plan to sell things.

If you want to have a virtual showroom is also a good option, but you could also do with X Portofolio + The Grid Plugin(Which looks beautifuuuul 🙂

Let us know if you have further questions and sorry for the long answer.

Thanks

Joao

[nillamary]

Hi,

Thanks for your response. Sorry, I didn’t mean import ‘all’ plugins literally, just the ones I need like WooCommerce, so all the containers are there before I start customising my site.

I am replacing my live photography site, which I built almost 6 years ago and quite dated now. That theme offered an integral cart system with the option for manual or self-fulfilment orders. There were no plugins, etc., to deal with, although for self-fulfilment orders, I had to use the Host’s Printing company, the process went smoothly.

I also have a WordPress.com site for my travel blog so whilst I am familiar with the WP Dashboard, working with a Child theme is what’s throwing me a little. You say that X comes with a built in WooCommerce Plugin, so, all I need to do is go to my Dashboard>Plugins and search for WooCommerce then install this? Reason I ask is that when I’m in Customiser for the Child, it’s just the theme and no plugins – think this is where I’m getting confused.

I know what I want and need for my replacement site; I’m just having difficulties starting with X.

Is that WPB Filterable Portfolio grid you mention? If not, can you please provide a link?

Many thanks.

[Rue Nel]

Hello There,

Thank you for the clarifications! Do you need to have WooCommerce installed? If that is the case, yes please go to Dashboard > Plugins and hit the Add New plugins. You’ll need to search for WooCommerce and install it. Once installed, all the WooCommerce support in X theme will get activated. For example, you may go to the customizer, Appearance > Customize > WooCommerce and set the layouts, columns and other options.

If you are having some difficulties in setting up X, the forum and the knowledge base (https://community.theme.co/kb/) should help you. If you need anything else we can help you with, please let us know.

Best Regards.

[nillamary]

I installed WooCommerce successfully and previous to when I received your support instructions above. I checked my files and I can see WooCommerce folders in the Parent; however, I do not see these folders replicated in Child. Is this correct?
(I can also see WooCommerce in my Dashboard.) I’m not sure if these folders should also be sitting in Child?
Many thanks.

[Joao]

Hi There,

That is correct.

All your changes will be stored at the database, and unless you need to make changes to your WooCommerce files that will require changing the original code of the plugin you won´t need to copy any files to your child theme.

So, to try to clarify, let´s imagine you want to achieve something on WooCommerce that you cannot do on your Dashboard, like changing the position of some element or adding an extra element that there is no option on the dashboard, in that case you would need to make changes to a php file of your woocommerce. Since you are changing the plugin, you would need to copy that file in your child theme, so when the plugin gets updated you don´t lose that modification. This is not the standard procedure, it is used in very specific cases, usually you will be able to achieve everything just on the dashboard so there is no need to save things on the child theme, all your changes made via the dashboard are stored on the database and won´t be lost once the plugin or your theme gets updated.

Hope that clarifies,

Thanks

Joao

[nillamary]

Thanks Joao for the clarification!

[Joao]

You are welcome,

Let us know if you need help with anything else.

Joao

[Author]

Posts