Fatal error: Allowed memory size of bytes exhausted (tried to allocate 36 bytes)
Fatal error: Allowed memory size of bytes exhausted (tried to allocate 36 bytes)
Fatal error: Allowed memory size of bytes exhausted (tried to allocate 36 bytes)
While static resources “belong” to WordPress or its extensions, it’s not actually involved in serving them to browser. Default WP rewrite rules completely bypass any actual existing file and let web server deal with it. In your case it’s impossible to guess what is going on from outside, but form the looks of it is … Read more
While there can be checks inside page the page itself is added via API call, like add_options_page() (there are several analogous functions that add pages to different parts of admin). This call includes capability argument. In your case either the extension in question is poorly coded and does something strange around there or your user … Read more
Array dereference (accessing array item directly after function result) is only possible since PHP 5.4, I’m guessing your remote server is running a lower version. Just use: $varname_temp = explode( ‘stuff’ ); $varname = $varname_temp[1]; Also on a side note, it’s always best to set your local to use the same PHP version as your … Read more
Possible to hide the search engine indexing disabled prompt/error message?
Try this: <?php if ( isset($theme_global[‘social-twitter’]) && ” != $theme_global[‘social-twitter’] ) { ?> <li><a class=”social-twitter” href=”https://wordpress.stackexchange.com/questions/160322/<?php echo $theme_global[“social-twitter’]; ?>” title=”<?php _e( ‘View Twitter Profile’, ‘lang’ ); ?>” target=”_blank”><i class=”fa fa-twitter”></i><div class=”tooltip”><span> Twitter</span></div></a></li> <?php } ?> First check by isset and then check if that value is empty. If it has value then display it.
Dashboard doesn’t work propertly
How to find which plugin crashes
Url encode the | (pipe characters) in the href attribute (%7C): <link rel=”stylesheet” type=”text/css” href=”http://fonts.googleapis.com/css?family=Open+Sans:400,600,300,800,700,400italic%7CPT+Serif:400,400italic%7CBree+Serif”> https://stackoverflow.com/questions/22466913/google-fonts-url-break-html5-validation-on-w3-orgenter link description here
If you look at the source of add_settings_error(), you will see that the errors are stored in the $wp_settings_errors global. So in your tearDown() function, you can do this: $GLOBALS[‘wp_settings_errors’] = array(); Also, don’t forget to call parent::tearDown(). I sometimes forget, and it can lead to strange behavior. 😉