Skip to content
Grav 2.0 is officially stable. Read the announcement →

Muut Archive Legend

@Muut · Joined 9 years ago · 18337 posts · 3878 topics · 137 reputation

Badges

✏️ First Post 💬 Conversation Starter ❤️ Well Liked

Recent posts

  • Returning specific status codes (e.g., 410 GONE) · 10 years ago

    According to bin/gpm version I am. I double checked my version of that file and then went back to the markdown and realized that routable was still set to false from when I copied it from the graveyar

  • Returning specific status codes (e.g., 410 GONE) · 10 years ago

    Do you have Grav v1.1.5 installed? We actually made a change/fix in this release to ensure that onPageNotFound is fired after onPageInitialized. Before this version, a not found was often fired befor

  • Returning specific status codes (e.g., 410 GONE) · 10 years ago

    Then why might the following code still be giving me a 404? public function handleMinimal() { dump("I'm here"); $route = $this->grav['config']->get('plugins.webmention.receiv

  • Returning specific status codes (e.g., 410 GONE) · 10 years ago

    Lots of examples of this in existing plugins. For example in login plugin we commonly replace the current page with one from the plugin: public function addRegisterPage() { $route = $

  • Returning specific status codes (e.g., 410 GONE) · 10 years ago

    I'm going slightly crazy. Following the Error plugin model, I was able to get the Graveyard plugin working. Now I'm back to Webmention. All I'm trying to do right now is get a GET to the /mentions rou

  • Returning specific status codes (e.g., 410 GONE) · 10 years ago

    So I'm just going to follow the error plugin and create separate page files, using the http_response_code header. I'm just used to dumping some text, setting the code, and getting out. But if this is

  • Returning specific status codes (e.g., 410 GONE) · 10 years ago

    At least it does when I throw it from my code. On my actual blog, if I go to a bad URL I do indeed get a 404. I'm so confused :/

  • Returning specific status codes (e.g., 410 GONE) · 10 years ago

    There's a few places where you throw a \RuntimeException('message' 404), but that doesn't actually return a 404. The actual status code returned is still 500.

  • Returning specific status codes (e.g., 410 GONE) · 10 years ago

    I'm sorry for the string of plugin questions, but I'm struggling to find the information I need. Once I finish this batch of plugins, I'll make some suggestions for the documentation. Anyway, I can't

  • Route discovery · 10 years ago

    But pages and routes aren't available within the CLI itself. The precache plugin uses the CLI to trigger a GET that then triggers the onShutdown event. In my case, I was hoping to have a standalone C