Gideon So Posted August 6, 2016 Share Posted August 6, 2016 Hi, I tried the UTF8 page name function. It is indeed very good but it seems limit the number of Chinese Character to 16. If the page name is more than 16 Chinese Characters, the whole backend become a blank page. I enabled the debug mode and found this error: ( ! ) Fatal error: Maximum function nesting level of '256' reached, aborting! in /home2/web/testserver/WireCore-3.0/core/Sanitizer.php on line 551 Any hints to fix it?? Gideon So Link to comment Share on other sites More sharing options...
LostKobrakai Posted August 6, 2016 Share Posted August 6, 2016 Just change the xdebug max_nesting config to something higher. Also in production xdebug shouldn't be installed anyways. Link to comment Share on other sites More sharing options...
SiNNuT Posted August 6, 2016 Share Posted August 6, 2016 Link to comment Share on other sites More sharing options...
Gideon So Posted August 7, 2016 Author Share Posted August 7, 2016 21 hours ago, LostKobrakai said: Just change the xdebug max_nesting config to something higher. Also in production xdebug shouldn't be installed anyways. Hi, Still get the same error nomatter how high the max_nestibg_level set. I have 5000 Chinese characters whitelisted in the config.php file. Is it possible the problem? If I disable xdebug, the connection just get reset and show a blank page when save. Any more ideas to fix it?? Attached last two lines of the error message from xdebug. Gideon Link to comment Share on other sites More sharing options...
Gideon So Posted August 9, 2016 Author Share Posted August 9, 2016 I think this is a bug that not ready for long whitelist. I make a bug report here: https://github.com/ryancramerdesign/ProcessWire/issues/1968 Gideon So Link to comment Share on other sites More sharing options...
Gideon So Posted August 17, 2016 Author Share Posted August 17, 2016 Thanks for Ryan's quick work. This bugs has been fixed. Gideon 2 Link to comment Share on other sites More sharing options...
bernhard Posted August 17, 2016 Share Posted August 17, 2016 dont forget to close the issue 1 Link to comment Share on other sites More sharing options...
Gideon So Posted August 18, 2016 Author Share Posted August 18, 2016 Hi, Thanks for reminding me. Just closed it. Gideon Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now