You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The build failures on netlify seem to have been caused by the jekyll-algolia plugin getting empty _geoloc.lat or _geoloc.lng fields on an entry (see bottom of this build log).
3:47:32 AM: [jekyll-algolia] Error:
3:47:32 AM: 400: Cannot POST to https://ITI5JHZJM9.algolia.net/1/indexes/*/batch:
3:47:32 AM: {"message":"_geoloc.lat or _geoloc.lng attributes cannot be null near line:1
3:47:32 AM: column:13786","status":400} (400)
so, going forward, just comment out any empty fields in the yml frontmatter.
good
#BASIC INFOtitle: Cell Elevensubtitle: Democratized Biotechtype-org: startup#LOCATION# address: # street and numbercity: Philadelphiastate: Pennsylvaniapostcode: 19135country: United States# _geoloc: # Geolocation coordinates for mapping# lat: # latitude number# lng: # longitude number
---
bad
---
#BASIC INFOtitle: Cell Elevensubtitle: Democratized Biotechtype-org: startup#LOCATIONaddress:
city: Philadelphiastate: Pennsylvaniapostcode: 19135country: United States_geoloc: # Geolocation coordinates for mappinglat: # WARNING THIS IS BLANK AND WILL BREAK BUILD # latitude numberlng: # WARNING THIS IS BLANK AND WILL BREAK BUILD # longitude number
---
The text was updated successfully, but these errors were encountered:
see #256 (comment)
The build failures on netlify seem to have been caused by the
jekyll-algolia
plugin getting empty_geoloc.lat
or_geoloc.lng
fields on an entry (see bottom of this build log).I think this file was the problem:
I removed the empty fields and the build succeeded:
now lets see if merging
staging
tomaster
results in a good build...I just mreged staging into master #272 and it seems to have worked.
https://app.netlify.com/sites/diybiosphere/deploys/5dad8fefc3371300081a40a1
so, going forward, just comment out any empty fields in the yml frontmatter.
good
bad
The text was updated successfully, but these errors were encountered: