ats (2017)

Dear Kirky Toolkit group, I need your help:

I have a couple of sites in which in previous I installed the Advanced TwentySeventenn Child Theme.

Now, for some my reasons, I need to uninstall all and make my own child theme.

For this reason I started a preparation study to understand the exact interactions between your enormous number of php kirki classes, to see where and which ones of them are used in my DOM.

I must tell you that they are just few, because our sites are fully customized by us, but, given the complexity of your ats structure, it is taking extremely long time to pinpoint exactly which snippets are applied to our sites.

I’ve done some in depth analysis about your “Advanced TwentySeventeen Child” theme:
actually the child is just the “door” of your plugin called “Advanced TwentySeventeen”, and all is managed by it.

In wp-content:

themes folder:

advanced-twenty-seventeen-child is composed with:
– style.css (where all is based on classes identified with prefix ats-xxx, and from where I used just 5 statements)
– functions.php (which is empty, apart the ABSPART instruction to prevent public user access via URL)
– footer.php (with a pretty small layout for footer in DOM, which I’m using)
– and two folders (“header” and “footer”) with 3 php of which I use few lines

plugins folder:

here there is the “managing base” of the theme (I have to say that I find this method quite strange, but it is your choice: I understand that your intention is (was at that time) to manage all by a toolkit).

However, here come my complications, because all of the child-theme is related to this plugin

As any toolkit, it is really implemented: articulated in 352 files in 74 folders, where the main sections are two:
– an “admin” folder, which is not used and that only installs the child theme tree

– a folder of “libraries”, subdivided in:

– “assets”, with some codes which I don’t use (note that main css’s are blank files)

– “includes” library with 114 php (recalling the “kirki class” for Kirki Toolkit) which is managed by an autoloader, and that affects the DOM in several arguments …

and here in “inc” comes my problem, because my DOM uses just two or three of those scripts, but it appears that all function scripts, even if not used, interact one each other, so if I delete them might be that also the php which I use stop working properly.

Since, as told previously, some of my sites are totally redone by us, out of standards of wp and of your child theme, I need to understand and find which of them influence the few codes snippets used by our DOM: surely no more than 2 or 3 functions or filters, but to quickly detect which ones I need your kind help,

because with development tools that I use it is no possible to test which php are ahead the loaded css and js (repeat they affect, just few code snippets, but the kirky classes php that manage this are approx 200) …

to manually read all functions and take note of the eventual interactions between them would need some weeks if not more, a crazy job to be absolutely avoided.

I started to test, breaking the flow of groups of php’s.

I can tell you that they affect something in header and in footer widgets.

So I have some questions for which I kindly ask you to reply:

1) which ones of the php kirky classes affect the header and the footer widgets? 2) … rest of questions follow (thank you)

• This topic was modified 1 year, 8 months ago by Mauro Vicariotto.