Thread Starter
cwh45
(@cwh45)
I have figured it out. I activated the twentytwelve theme instead of my child theme and that worked with mobile devices so I figured it must be a child theme issue.
I went through the files of my child theme: I left .css and .rtf as they were and images file as it was.
Renamed functions.php to -functions.php and footer to -footer.php and hey presto it worked.
I have looked up a lot of stuff on this and suggestions range from deactivating plug-ins to cache issues. I am not techy but thinking about it, all the problems I have had with the site (previously not able to log-in), have been caused by the functions.php file in my child theme: it appears you do not need this for the child theme to work. Leave the parent functions.php exactly as it is and get rid of functions.php altogether, even if its got no code in it seems to screw things up.
I would be happy if someone could explain why the functions.php in the child theme seems so troublesome!?
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
What did you have in your functions.php file of your Child Theme?
Thread Starter
cwh45
(@cwh45)
nothing at all!
That’s what I don’t understand?
By having a functions.php in your child theme folder, you are preventing the parent theme’s functions.php from being included in the site. You are replacing it with your own version, even if your child theme’s functions.php is a blank file. Your situation tells me that your parent theme’s functions.php has some code that your site needs to run, and the blank version in the child theme prevented that code from executing.
