None of the links do anything (i.e the gray boxes: Activation & reactivation, Registration, Contact etc)
I’ve tried Chrome, Firefox, Edge.
Looking at the page source, there’s no href in the links, so I guess there’s supposed to be some JS handling it (why??).
In lieu of that, I have a project file that seems to have been corrupted. I opened it today and get “Invalid project file!”.
The same project’s previous save file is fine, but I don’t really want to have to redo the lost work.
The .bak files for the most recent save are also corrupt.
The previous working save is on the same disk, same directory etc.
Restoring that particular file from remote backup is also corrupt.
Was hoping to ask support if there’s a way to revive them. Any ideas or assistance appreciated.
I fear I cannot be of big help here, but I can confirm that the helpcenter reacts the same for me - on clicking on an area the whole page flashes, nothing else.
Just to make sure, I’ve tried Firefox, Vivaldi, Edge on Windows; Chrome, Safari and Firefox on Mac. Javascript on in all of them.
I’ve tried in Incognito windows and with all plugins/ad blocking disabled.
None of them work.
Looking at the page source reveals there’s no href in those links, so they won’t work regardless of browser (unless the intention was to use some janky Javascript, but I don’t get any JS errors in the console at least).
If there’s a network issue between you and SB, certainly we can’t troubleshoot here on a user forum, if you cleared your browser cache and the symptom persists, there’s not much else to say here.
Autosave is not what I referred to. I mean doing frequent backups, such as Windows File History, or new version saving from the Cubase File menu.
If you want more answers to the actual question you wanted to ask, I would suggest editing the title of this topic or starting a new one with a meaningful title.
The hrefs in the help center response body are missing, even though the rest of the page content is there. That only really points to a backend issue or some a bad server side cache/CDN issue or something like that (and wayback machine would suggest they should be there, and have been before).
