herb miller
WordPress plugin specialist
-
Show and tell – What’s going on?
Yesterday, the Cheltenham WordPress Meetup was a series of Show and Tell talks. Along the lines of Lightning talks, these are talks of approximately 10 minutes, where individuals share something they’ve been working on. There were 7 talks planned:
- Richard Bell @Rich Bell demoed Ray and Background WordPress processing,
- Mark Wilkinson @wpmark demoed his Just In Time CSS,
- Elliott Richmond @erichmond showed us how to run Xdebug using Visual Code Studio, setting breakpoints, watching variables and changing values on the fly,
- Ross Wintle @magicroundabout demoed his new CSS and PHP based spam pixel plugin to block spam bots
- Keith Devon @keithdevon showed us his work on CSS grid for block based themes
- We ran out of time before @Jonnyauk had a chance to show his latest work with template parts ( PHP version not FSE ).
- and somewhere in the middle of it I talked about 3 plugins I’ve written to help visualise my server side performance: oik-bwtrace sb-chart-block and slog.
This post is the annotated version of the slides.
Published:
Last updated:
April 20, 2021 -
Jetpack photo cache issue #2752333
Attempting to demonstrate the need for being able to clear Jetpack’s photon cache.
Published:
Last updated:
July 26, 2016 -
Site recovered – sorry for the inconvenience
Sometime on the 12th my site started to produce a series of PHP Fatal errors saying “Allowed memory size of 41943040 bytes exhausted.”. This was a bit of a surprise. It means that my memory limit was 40M, a lot lower than the expected value of 256M. Other times the response was
[13-Jul-2016 02:54:59 UTC] PHP Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0
Problem recovery
To recover from this problem I used ftp to rename Jetpack to Jetpack-f. I was then able to access the site.Problem explanation
- The site was migrated from one host to another.
- The PHP version on the new host was 5.4.45.
- The memory_limit was set to
25M. - For PHP 5.3, 5.5 and 5.6 the memory_limit would have been
256M; a much nicer number. - By the time WordPress started up the memory limit became
40M. - It’s WordPress that sets this limit, depending on the site. For WPMS it’s
64M. See wp_initial_constants().
Other notes
- My oik-bwtrace plugin reports the memory limit on its admin page.
- This is 256M, since WordPress sets it higher in admin pages. Using admin_memory_limit in wp-admin/admin.php.
- I’ve changed my [wp] shortcode to display the memory limit on the front-end.
- For this site the memory_limit has already been set by the hosting company to a high value.
WordPress 5.8.1. PHP: 7.3.31. Memory limit: 768M - I’m also experimenting with code that displays the current memory_limit in trace records produced by oik-bwtrace. They already optionally display current and peak memory usage, so adding the current memory limit is no big deal.
Published:
Last updated:
July 18, 2016 -
Jetpack Photon image stretch in responsive Artisteer theme
I recently noticed that when Jetpack’s Photon module is activated strange things may start happening in Safari on my iPad.
Published:
Last updated:
May 14, 2015 -
DIY-oik v1.4 fixes problems with Add-To-Any and Jetpack Related Posts
DIY-oik v1.4 fixes some problems with unexpected output from other plugins.
Published:
Last updated:
January 13, 2015
Recent Posts
Recent Comments
Categories
Gutenberg version:11.7.0