Feature #21359
closedClarify advanced-custom-fields upgrade procedure
0%
Description
While the new status quo surrounding advanced-custom-fields emerges, CAC will use the version of the plugin provided by advancedcustomfields.com. This will ensure compatibility with advanced-custom-fields-pro.
Updated by Boone Gorges 4 months ago
- Status changed from New to Assigned
- Assignee set to Boone Gorges
Updated to version 6.3.10 in https://github.com/cuny-academic-commons/cac/commit/545bcda7e0acaa48da114e63f42fbb0358040277.
I'll leave this ticket open for the next release to understand what happens with CLI-based updates moving forward.
Updated by Boone Gorges 4 months ago
- Target version changed from 2.4.10 to 601
It looks like wordpress.org has released a version 6.3.10.2, while we've stayed on 6.3.10. I think this means that the CLI upgrader is pinging WPE rather than wordpress.org, which would mean that this ticket can be closed. But I'd like to leave it open until there's positive confirmation, in the form of an update from WPE.
Updated by Boone Gorges about 1 month ago
- Target version changed from 2.5.1 to 2.5.3
Updated by Boone Gorges 15 days ago
- Status changed from Assigned to Staged for Production Release
It seems that WPE may no longer be updating the version that comes from their site, and instead is pushing updates through wordpress.org. I've switched back to that endpoint in https://github.com/cuny-academic-commons/cac/commit/d8f994b3ad10d85c5fa9c666c0589c255f77c47c and we'll leave it this way until the situation changes again.
Updated by Boone Gorges 15 days ago
- Status changed from Staged for Production Release to Resolved