HTTP 500 Error when activating child theme
- This topic has 3 replies, 3 voices, and was last updated 7 years, 10 months ago by .
Viewing 3 reply threads
Viewing 3 reply threads
- You must be logged in to reply to this topic.
Home › Forums › GovIntranetters › HTTP 500 Error when activating child theme
Tagged: child theme, server error
I’m wanting to create a child theme for our GovIntranet installation. I have set up the minimum WordPress requirements for a child theme (folder created, style.css file with requisite comment). I can see it as an available theme in the WordPress Manage Themes page. When I activate the child theme in the WordPress Manage Themes page I get an internal server 500 error on any page of the site. I tried adding a blank functions.php file. Same error message. I am able to fix it by using a MySQL GUI to change the theme back to the original. I have tried enqueuing the parent style.css and the style.css from my child theme in functions.php and get the error as well. Is there something else I need to enqueue?
I am running GovIntranet Theme Version 4.27.4 and WordPress version 4.6. PHP 7.05 on Windows Server 2008R2 using IIS 7.5.
following with interest, as we’re looking to do the same
V4.28 should now support child themes!
I’ve tested this with just a style.css file in the child theme.
Please let me know how you get on with this.
I updated to V4.30.1 and was able to activate a child them with only a blank style.css file in the child theme. Thank you! Interesting to me is that I was expecting with a blank style.css file in the child theme that it would only use the default browser stylesheets. But it pulled in the parent styles without having to enqueue them or do an @import in the child theme style.css. That works for me!
Sorry that it has taken so long to reply to the thread. In the US here we’ve had a holiday and I’ve been trying to catch up on all my duties.
Cookie | Duration | Description |
---|---|---|
comment_author_email_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
comment_author_url_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
comment_author_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
wordpress_logged_in_[hash] | Indicates when you’re logged in, and who you are, for most interface use. | |
wp-settings-{time}-[UID] | This is used to customize your view of admin interface, and possibly also the main site interface. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | Used to distinguish users. |
_gat | 1 minute | Used to throttle request rate. |
_gid | 24 hours | Used to distinguish users. |