Muut Archive Legend

Recent posts

• Deploying to Heroku, 500 Error · 11 years ago

  A 500 error always means a problem with the web server configuration. Typically with Apache this means that something in the configuration is not supported in the current Apache setup. With Grav, th

• Deploying to Heroku, 500 Error · 11 years ago

  My most recent build log is here, https://www.dropbox.com/s/h1fakhl2msaaqqm/buildlog.txt?dl=0

• Deploying to Heroku, 500 Error · 11 years ago

  Hi there, I'm trying to get Grav deployed to Heroku, basically I just have the RTFM skeleton with different pages. I'm testing locally in WAMP and have it on GitHub. Heroku goes through the motions,

• Open link in content in new window · 11 years ago

  Alternatively I solved with this piece of JavaScript: $(document.links).filter(function() { return this.hostname != window.location.hostname; }).attr('target', '_blank'); ---

• Open link in content in new window · 11 years ago

  There is an external_links plugin available.

• Open link in content in new window · 11 years ago

  Hi there! I am new to Grav and I love it! I cannot however find a way to make links in content of pages open in new window (target="_blank"). Is there a working solution around? How do you set the lin

• Error since upgrading to 1.07 · 11 years ago

  Many thanks for finding that. It is a backup left by BBEDIT. I suppose as I am using Git I don't really need to save those backups. I'll amend my preferences going forward.

• Error since upgrading to 1.07 · 11 years ago

  @jeremyc Flavio shared the zip with me so I took a look. The error is caused by an extra temp file: user/config/system.yaml~ that must of been generated and left while you edited in VI or Emacs or so

• Error since upgrading to 1.07 · 11 years ago

  Do you have any extra environment configs? These are not setup by default, but you might of created a localhost folder or something, so you could have a localhost/config/system.yaml file. This could

• Error since upgrading to 1.07 · 11 years ago

  I just checked, and the system/config/system.yaml file is the one I downloaded yesterday afternoon with the core update. No changes.