Error: Whoops. Looks like this page doesn't exist.
See original GitHub issueAnytime one tries Edit in the Actions button on a page that is not the page referenced to in the URL, you get this exception :
Error: Whoops. Looks like this page doesn't exist.
It happens on the root of the web site for example, where list of the md files is displayed on the center :
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Error: Whoops. Looks like this page doesn't exist #293 - GitHub
Just downloaded the latest release (v0.16.2) and entered npm install and npm run start_win into Powershell (on Windows). Looking at the error ......
Read more >“Whoops, looks like something went wrong”, | WordPress.org
Hi I wanted to reconnect my Woocomerce-Shop to my FB/Insta-Shop because of some sync issues. Know I'm getting the error message “Whoops, ...
Read more >Custom 'Whoops, looks like something went wrong'-Page
Hey there, I don't find any trick to customize this error page. I created a 500 view under the errors folder but nothing...
Read more >500 Whoops, looks like something went wrong - Joomla! Forum
I get an error both in user and administrator mode. ... The server returned a "500 Whoops, looks like something went wrong.". Something...
Read more >Blizzard CS - Twitter
Getting BB8 "Whoops! Looks like something broke" errors when trying to update a game or the #Bnet app? This error is often caused...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The example needs to be updated to
0.17.0
and the issue is resolved. It had an older version. Also gulp needs to be added to dev dependencies in order to get npm install to complete. so package.json for the example should beI’d close this but I didn’t open it so I can’t.
Thank you for investigating @dkebler Closing issue to cleanup