-
Posts
-
P.S.
What is the “Fancybox” folder? What is it’s purpose? Do I need it? Is it something the web design firm added that I no longer need?Also – there are two other files in the child theme folder: custom.css and functions.php. I’m familiar with what these files are designed to do. But the design firm apparently did a little custom coding in these files.
Do I need what they’ve done in these files – or can it just be deleted?thanks!
Hi there,
Sounds like your site files are messed up and we won’t know what was actually changed. You should use a fresh copy of X and never should change anything on the theme files. If you need customization, you need to use Child Theme in case you need to change the templates. In your current situation, we can’t help much as this is out of our support realm. You can consult with a professional to get them sorted.
Thanks!
HI Rupok,
I explained in detail what was changed.
It’s quite simple:The original coders duplicated the “themes” folder, and put it inside the existing “themes” folder, and renamed the child theme.
So now, instead of
public_html > wp-content > themes > x-child
I have
public_html > wp-content > themes > themes > x-flightwave.MY QUESTIONS ARE SIMPLE:
1. I’ve been building the site fine with things like this. Will this altered file structure cause any issues though going forward?
2. Should I set it back to the way it originally was?
(By renaming x-flightwave to x-child, and copying the contents of the second (inner) themes folder to the primary (outer) themes folder – overwriting “x” and “x-child”)3. If you recommend leaving it as is, will that pose any difficulties when cloning the dev site to the primary domain when we’re ready to go live?
- <script> jQuery(function($){ $("#no-reply-1378883 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
