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
I updated Ghost from 0.7 to 0.10 today, and I can no longer access the admin through /ghost/. Trying to access that url results only in a blank page.
In the process to update I stepped through each major version 0.7->0.8->0.9->0.10 to avoid the issues in #7297. The public facing blog is appears to be working correctly.
Steps to Reproduce
Visit the /ghost/ path
I am getting the following console error when accessing the page.
vendor.min.js?v=df2cd1cda0:12 Error while processing route: posts.index Unexpected token u in JSON at position 0 SyntaxError: Unexpected token u in JSON at position 0
Technical details:
Ghost Version: 0.10
Node Version: 4.5.0
Browser/OS: Chrome on OSX
Database: PostgreSQL
The text was updated successfully, but these errors were encountered:
Turns out adding 'www.' to the url allowed access to the admin. I am not sure how to explain that change, but it solved my issue, and allows me to access the admin.
Some additional information in case it is useful in the future, the admin was accessible with without the 'www.' in the url in the previous version, it worked in Firefox without the 'www.', and it worked in Chrome's Incognito Mode without 'www.'
Issue Summary
I updated Ghost from 0.7 to 0.10 today, and I can no longer access the admin through /ghost/. Trying to access that url results only in a blank page.
In the process to update I stepped through each major version 0.7->0.8->0.9->0.10 to avoid the issues in #7297. The public facing blog is appears to be working correctly.
Steps to Reproduce
I am getting the following console error when accessing the page.
vendor.min.js?v=df2cd1cda0:12 Error while processing route: posts.index Unexpected token u in JSON at position 0 SyntaxError: Unexpected token u in JSON at position 0
Technical details:
The text was updated successfully, but these errors were encountered: