bobbingwide / wp-a2z Goto Github PK

WordPress 4.7.3, a Security and Maintenance Release, was released on 6th March 2017

wp-a2z.org should be updated to reflect the changes.

The reference should be re-built by extracting the latest source from the 4.7.3 ZIP file.

Notes

At the same time take the opportunity to:

• Rebuild all the sites with support for https as well as http
• Add A to Z pagination
• Update plugins and themes to the latest versions
• Rebuild the API ref for the plugins and themes

WordPress 4.8.1 was released on 3rd August 2017. We will need to update to the latest level and re-index.
The reference should be re-built by extracting the latest source from the 4.8.1 ZIP file.

• wp-a2z.org should be updated to reflect the changes.
• write blog posts

Notes

At the same time take the opportunity to:

• Update plugins and themes to the latest versions
• Rebuild the API ref for the plugins and themes

WordPress 4.8.2 was released on 19th September 2017. We will need to update to the latest level and re-index.
The reference should be re-built by extracting the latest source from the 4.8.2 ZIP file.

• wp-a2z.org should be updated to reflect the changes.
• write blog posts

Notes

At the same time take the opportunity to:

• Update plugins and themes to the latest versions
• Rebuild the API ref for the plugins and themes

WordPress 4.7.1, a Security and Maintenance Release, was released on 11th January 2017.

wp-a2z.org should be updated to reflect the changes.
The reference should be re-built by extracting the latest source from the 4.7.1 ZIP file.

WordPress 4.7.4 was released on 2017/04/20. We need to update to the latest version and re-index.

See #6

WordPress 5.2 was released on 7th May 2019. We will need to update to the latest level and re-index.

• wp-a2z.org should be updated to reflect the changes.
• write blog posts

Notes

At the same time take the opportunity to:

• Update plugins and themes to the latest versions
• Rebuild the API ref for the plugins and themes
• Check which blocks are supported

While WP-a2z.org already appears to be 4.5.3, it wasn't through the approved process.
The process expects WordPress core to be updated from Git, not automatically, which is what happened at the end of June. Akismet, Hello Dolly and the themes will also need updating.

Hi when trying to hit https://woocommerce.wp-a2z.org/oik_api/wc_order/add_order_note/ there was a fatal error:

Fatal error: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given in /home/customer/www/bobbingwide.org.uk/public_html/wp-includes/block-supports/align.php:48

Hope that helps or at least to turn off error reporting.

Best,
Atanas

WordPress 5.3 "Kirk" was released on 12th November 2019.
We need to update wp-a2z.org with the new version and re-parse it.
Trouble is, there are a couple of outstanding problems:

1. The parse has got confused and can't get/set its status
2. So we have to start it by passing a Git commit point e.g.

oikwp oik-shortcodes.php wordpress 7d3e363 url=core.wp-a2z.org

3. If it fails then we have to start again, which restarts at the beginning.
4. It's failing when attempting to parse core.

Processing: prepare_item_for_database,WP_REST_Posts_Controller::prepare_item_for_database,
wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php

mmap() failed: [12] Cannot allocate memory

Fatal error: Out of memory (allocated 1046478848) (tried to allocate 1052672 bytes) in
/home/bworguk/public_html/wp-content/plugins/oik-shortcodes/classes/oik-listapis2.php
 on line 204

As with other releases I need to update the API reference for WordPress core, the bundled plugins and themes and the other plugins and themes in subdomains.

I'm sure I did this for WordPress 5.7!
Anyway, it's 5.7.1 now. So time to do it again.

See table below.

WordPress 4.8, code name "Evans" was released on 8th June 2017. We will need to update to the latest version and re-index.

As with other major releases I need to update the API reference for WordPress core, the bundled plugins and themes and the other plugins and themes in subdomains.
I started doing this today. See table below.
I found problems when I tried to update Akismet.
It appears that in June I managed to install new versions of Akismet and Hello Dolly over the top of the git repos.

As for previous releases.
WordPress 4.7 was released on 6 Dec 2016.

wp-a2z.org should be updated to reflect the changes.
The reference should be re-built by extracting the latest source from either SVN or the 4.7 ZIP file.

WordPress 4.7.5 was released on 2017/05/16.
We need to update and re-index.
The reference should be re-built by extracting the latest source from the 4.7.5 ZIP file.
See #7

WordPress 4.6 was released on 17th August 2016, and 4.6.1 on 7th September 2016.

wp-a2z.org should be updated to reflect the changes.

WordPress 5.1 is due on 21st February 2019. We will need to update to the latest level and re-index.

• wp-a2z.org should be updated to reflect the changes.
• write blog posts

Notes

At the same time take the opportunity to:

• Update plugins and themes to the latest versions
• Rebuild the API ref for the plugins and themes

WordPress 4.7.2, a Security Release, was released on 26th January 2017.

wp-a2z.org should be updated to reflect the changes.
The reference should be re-built by extracting the latest source from the 4.7.2 ZIP file.

WordPress 4.9.1 was released on 29th November 2017. We will need to update to the latest level and re-index.
The reference should be re-built by extracting the latest source from the 4.9.1 ZIP file.

• wp-a2z.org should be updated to reflect the changes.
• write blog posts

Notes

At the same time take the opportunity to:

• Update plugins and themes to the latest versions
• Rebuild the API ref for the plugins and themes

As with other major/minor releases I need to update the API reference for WordPress core, the bundled plugins and themes and the other plugins and themes in subdomains.

I started doing this yesterday. See table below.

There was one problem with Jetpack.

Also, a number of files have accidentally become part of the repo. These need to be .gitignored and/or removed

See bobbingwide/oik-shortcodes/issues/53 and bobbingwide/oik-batch/issues/23.