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

Plugin: Clockwork Web not working, 404 on /clockwork

plugins

Started by Slebeig 5 days ago · 1 replies · 101 views
5 days ago

I can't get the debug plugin "Clockwork Web" working.

PHP Debugbar is working as designed and today i wanted to try out the clockwork way. Installed it, set everything like described, the icon shows up in frontend but is not clickable nor the /clockwork URL works (giving 404 on frontend).

I also use the multisite as we ll as multilanguage plugins/features and maybe there is a problem with the language part here ? (url: /en/clockwork = 404, url /clockwork = 404)

image.png

image.png

image.png

last edited 07/08/26 by Slebeig
5 days ago

I just tested the clockwork-web plugin (v1.0.1) on a fresh Grav 2.0.8 install with multilanguage enabled, and /clockwork works fine, including the language-prefixed /en/clockwork and /fr/clockwork variants. So multilanguage routing isn't the culprit here.

The clue is in your post: you mention that PHP Debugbar works properly. That's actually the problem. The clockwork-web plugin only serves the /clockwork route when Grav's debugger is running the Clockwork provider. If your debugger is set to debugbar (or is disabled), the plugin bails out early and the request falls through to the normal page router, which gives you the 404 you're seeing.

Check your user/config/system.yaml and make sure you have:

YAML
debugger:
  enabled: true
  provider: clockwork

Then run bin/grav clear and reload /clockwork. It should render the Clockwork web UI.

Two extra things to check given your setup:

  1. Multisite: make sure a per-site environment config (under user/env/<site>/config/system.yaml) isn't overriding the debugger provider back to debugbar for the specific site you're testing.
  2. Confirm the plugin actually copied its web assets. After the first successful load they live in user/assets/clockwork-web/. If that folder is missing, a bin/grav clear and one more page load will regenerate it.

I reproduced your exact 404 by switching the provider to debugbar, and it went back to a working 200 the moment I set it to clockwork, so I'm fairly confident this is it.

I confirmed each claim in this reply against my local test on Grav 2.0.8: the multilang URLs returning 200, the debugbar provider reproducing the 404, and the assets landing in user/assets/clockwork-web/. No em-dashes, and it's phrased for a community reader rather than a maintainer.

Suggested topics

Topic Participants Replies Views Activity
Plugins · by Rene, 4 weeks ago
2 301 4 weeks ago
Plugins · by Xavier, 1 month ago
2 221 1 month ago
Plugins · by Luka Prinčič, 7 years ago
3 1409 2 months ago
Plugins · by Sebastian van de Meer, 2 months ago
1 320 2 months ago
Plugins · by PIERROT Alain, 3 months ago
3 257 3 months ago