This is my bucket list for WordCamp Brighton 2016; things to achieve before I depart at the end of the Contributor day.
It appears that my problem with this site was not a one-off. Quite a few of the sites that I have hosted with TSOhost were affected by the server switch. For some reason during the migration the level of PHP that was chosen was 5.4.45, with memory_limit set to 25M.
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
To recover from this problem I used ftp to rename Jetpack to Jetpack-f.
I was then able to access the site.
- 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
- 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
- It’s WordPress that sets this limit, depending on the site. For WPMS it’s
I’ve yet to track down the specific plugin/module combination that causes WP to exceed the 4OM limit.
- 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.5.1. PHP: 7.3.23. 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.
For a while now, I’ve been developing a replacement for my WP-a2z Dynamic API Reference.
Today, just over two years after wp-a2z.org was first revealed, I’ve switched over to the new version.
Here are some notes about the new version.
I’ve been porting a site from Drupal to WordPress recently but it wasn’t until I loaded it onto hosting with 1&1 that I noticed some problems with my [bw_show_googlemap] shortcode.
I’ve fixed the problem in oik v3.0.2. The new solution requires you to obtain a Google Maps API key, and enter it in oik options.
If you’re running PHP 7 on Windows and you want to use the Imagick PHP extension then you may want to refer to this post for some download and installation instructions.
Marmalade the cat.
With the Genesis Theme Framework, on the “blog” page (Content Archives), what you get to see depends on the values for the Content Archives fields in Genesis > Theme Settings.
For the Display field the choices are
Entry content or
Here we’re looking at whether or not a [Read more…] link will be shown.
In 2015 I wrote a bucket list of things to achieve before leaving WordCamp London; bucket list – post WordCamp London 2015.
After the event it was much longer; bucket list – WordCamp London: 20-22 March 2015 (#wcldn).
This year I’ve volunteered my services to help with the running of the event. Will I have more or less opportunity to work on my bucket list? It’s a bigger list than ever.
If you happen to know an answer, just come to find me, let me know, and then after a few more questions you can go on your way.
I’ll be wearing a blue “localhost” T-shirt, just like the other volunteers. If you can’t find me just tell another volunteer and they can either pass it on through Group Me, or look utterly bemused.
Here’s my list, in no particular order.
Just recently something went terribly wrong and I lost some recently made source code updates that, even though they’d been checked into version control had not been pushed anywhere. So there was no backup. It’s my own stupid fault; I let WordPress make an update that it shouldn’t have.