On Wed, Feb 1, 2017 at 6:20 PM, Jesse Bright <je...@abrightfamily.com>
wrote:

> The error occurs with both "Save & Continue" and "Save & View", though if
> I choose "Save & Continue" first it allows me to keep going after the error
> so I can then press "Save & View" without generating the error since the
> page now exists.
>
> I checked the dev tools and it generated two errors.
>
> 1) SCRIPT1010: Expected identifier
> 2) SCRIPT7002: XMLHttpRequest: Error 0x8007005, Access is denied.
>
> The first seems unrelated but the second seems to be the issue. The
> Microsoft docs on this error mention API JSONP vs CORS support and calls to
> the REST API but unfortunately I am reaching the limit of my current
> technical skills. Thanks for your help so far, do you have any guidance for
> my next step?
>

Do you use HTTPS? Check if the protocol of the XMLHttpRequest matches the
protocol of the current page (i.e. both should be either HTTP or HTTPS).
You can also check the domain that appears in the URL of the
XMLHttpRequest. Does it match the domain from the current page URL?


>
> Regards,
>
> Jesse
>
> > On Jan 31, 2017, at 9:53 PM, Marius Dumitru Florea <
> mariusdumitru.flo...@xwiki.com> wrote:
> >
> > How do you save the class? "Save and Continue" or "Save and View"? You
> can
> > check using the browser's dev tools to see if there are any JavaScript
> > exceptions (in the JavaScript Console) or if there is any failed (XHR)
> HTTP
> > request in the Network tab.
> >
> > On Wed, Feb 1, 2017 at 2:14 AM, Jesse Bright <je...@abrightfamily.com>
> > wrote:
> >
> >> Whenever I save a new class (app?) based wiki page (blog, FAQ or custom
> >> app) I get a red error at the bottom of the page that reads: "Failed to
> >> save the page. Reason: Server not responding" The strange thing is the
> page
> >> did save. Other than the error message nothing appears to be wrong.
> >>
> >> Any thoughts on what could be causing this or where I should begin
> >> troubleshooting?
> >>
> >>
> >> Regards,
> >>
> >> Jesse
> >>
> >>
>
>
>

Reply via email to