最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

Internal error 500 accessing Theme > Customize

matteradmin9PV0评论

We have created a basic custom theme for WordPress. When trying to access Appearance > Customize from the backend we receive an internal error 500. I have checked the error logs and cannot find anything relating to this.

The website is working fine, the theme is working fine as expected, just accessing the customize section.

Do we need to include anything specific in the functions theme file to be allowed to access this section? Does a part of the theme have to be customizable in some way? I have tried various searches for this, although the basic 500 errors seem to come up a lot. I.e. htaccess, plugin issues.

We have created a basic custom theme for WordPress. When trying to access Appearance > Customize from the backend we receive an internal error 500. I have checked the error logs and cannot find anything relating to this.

The website is working fine, the theme is working fine as expected, just accessing the customize section.

Do we need to include anything specific in the functions theme file to be allowed to access this section? Does a part of the theme have to be customizable in some way? I have tried various searches for this, although the basic 500 errors seem to come up a lot. I.e. htaccess, plugin issues.

Share Improve this question asked Nov 13, 2015 at 16:57 StuartMStuartM 2313 silver badges8 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 1

Just in case anyone else finds this in the future. The issue was that we had an error/warning in our functions file.

When accessing widgets we noticed the error/warning from the file. Resolved this, then the customizer link provided us with an on page error.

The on page error linked to a reimplementation of a method from within a plugin. The plugin was overriding a core method so we removed it and now works as expected.

Post a comment

comment list (0)

  1. No comments so far