export failures (both app and browser)
-
I’ve been unable to export from the browser I always use (which worked until the latest WP desktop (Linux) app came out. I’m not sure if I had v7.0.5 or v7.0.6, but all was well until your latest (v7.10.0) release.
When I tried to use a browser just now, I got to the export page, specified a full export, and am presented with a flicker (showing the queries for which sections I wanted to download page for less than a second) and an almost-instant return to to the export page.
No export gets sent. How do I get the v7.0.6 deb back? I’d like to backup my content, but the WP site just isn’t co-operating and the latest desktop (Linux) app won’t even run.
(All other pages seem to work fine within the browser.)
Site: (email visible only to moderators and staff).
WP.com: Yes
Correct account: Yes -
Hi, I don’t think the app is related to anything going on in the browser. What browser are you using? Do you have any settings that could be blocking scripts / file downloads? And, if you try another browser, do you run into the same issue?
If you’d like, we can generate a backup here, and you’ll get a link via email when that’s done. Let us know.
-
Hi supernovia; thanks for your reply.
I don’t think there are any concerns linking the browser difficulty and the wpcom app’s crashing either. The latter appears to be something in the last update that requires a different library than the one currently on my system and it crashes on invocation.
The wpcom app’s requirements have obviously changed at v7.1.0, which is why I was hoping I could get I could get a copy of wpcom 7.0.6 (for Linux) – it worked perfectly and v7.1.0 doesn’t crashes consistently when I try to invoke it…
================
wpcom: /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0: no version information available (required by wpcom)
/opt/WordPress.com/wpcom: /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0: no version information available (required by /opt/WordPress.com/wpcom)
/opt/WordPress.com/wpcom: /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0: no version information available (required by /opt/WordPress.com/wpcom)
Fontconfig warning: “/etc/fonts/fonts.conf”, line 86: unknown element “blank”
WordPress.com ran into an error
Please restart the app and try again.
================What I am concerned about is that I can’t back up (and I’ve tried multiple browsers). The browser that used to work no longer does and it did work the week before wpcom v7.1.0 was released. With neither access fully working, I cannot back up my blog.
The simplest solution is doubtless the prior wpcom program (because it may not be as current, but it will let me back up. I can post with the browser, but I can’t back up wit it now.
If I may take you up on your offer to send me a backup link, I’d be very grateful.
*My concern here is that I should be able to back up for myself on one or the other route (browser or app) and wpcom v7.0.6 was the last wpcom app that let me do that for myself.*
-
errata: “wpcom 7.0.6 (for Linux) – it worked perfectly and v7.1.0 doesn’t crashes consistently when I try to invoke it…”
should read:
“wpcom 7.0.6 (for Linux) – it worked perfectly and v7.1.0 doesn’t – it crashes consistently when I try to invoke it…”
Sorry.
-
Just to clarify, it sounds like you’ve got two different issues:
1. The latest WordPress for Linux app isn’t running at all. 7.0.6 worked, and 7.1.0 just crashes on startup
For this, I’ll pass the log info along to the apps team to see what they recommend.
2. You’re not able to make a backup of your WordPress site using a browser
Do you want to just wait to troubleshoot this until after the first issue is resolved, or would you like us to generate a backup for you for now and email it, then we’ll revisit that later?
-
Oh, I almost forgot to ask, what version and flavor of linux are you running? I’ll need to pass that along as well.
-
Hi again, supernovia – I appreciate your thoroughness in this.
Your analyis is accurate. To try to find you further information, I set up a VM (virtual machine) and ran a copy of a wholly different Linux distribution (with a newer version of Firefox) on it.
My original Linux (Trisquel) stopped running the wpcom desktop app above v7.0.6; the test distro (in the VM – Zorin 15.3) will run wpcom v7.1.0, reflecting the age of the Trisquel distro. (The latest IceCat – a Firefox variant – on Trisquel is v64.0 but things have always worked until now.)
The Zorin (VM) Firefox is v80.0.1; both will login to the WP site, but neither will export a backup from https://0ddn1x.wordpress.com/wp-admin/export.php.
This is a recent [mis]behavior; I discovered it only when when wpcom v7.1.0 refused to run on my system. It may have pre-existed on wpcom v7.0.X, but I was using wpcom rather than PaleMoon for weekly backups and cannot verify this without a copy of wpcom v7.0.5/v7.0.6 to test with.
PM (my old WordPress standby, which has always worked for posting and backup before) and multiple generic Firefox variants, Brave (which is Chromium-based, just as WP’s electron ‘apps’ are), Firefox itself, even Librewolf… no joy.
I’ve pared down my /etc/hosts file to a bare minimum (just in case) without any changes in behavior. I do not block scripts (or JS) on PM and I’ve run Brave with JS enabled to text with – but no blog backups are currently possible.
I can post with a browser (PM), but that’s always worked; this [recent] export hiccup is troubling; I take regular (weekly, post-publishing) backups very seriously.
The wpcom v7.1.0 app runs on Zorin (which I expected – it now requires a status response from a specific more recent library that Trisquel lacks), but the exports do not (which seems to preclude that being a simple browser-specific issue).
Any chance I can get a wpcom v7.0.5/v7.0.6 .deb to test with (and [hopefully] mitigate my sudden inability to backup)? I’m willing to use either the WP app or or a browser, but my personal preference is being able to do everything in a browser. Having the wpcom app is nice, but in no way necessary.
-
Another minor errata, my apologies.
“I’ve run Brave with JS enabled to text” should have read “I’ve run Brave with JS enabled to test with”.
-
Hi there,
After taking a look it seems we are replicate your export issue. I have tried in Chrome on my Mac, and if I attempt to create an export, the page reloads for me and no export is initiated so for that specific issue I’m having our engineers take a look and see if we can discover what is going on there. The WordPress app is not at issue here, as the app essentially just loads the web version.
If I can ask, why the need for weekly “backups” as you call them? Here at WordPress.com, we take the security of your site’s data pretty seriously, and this includes a robust system of redundant server-level backups for all the sites we run. From that standpoint, you needn’t worry about backing up your site; we’ve got that covered.
An export is not exactly the same as a true backup, but in any case it should not be necessary if you are just trying to “safekeep” your content. You simply prefer to keep a copy of a recent export on your computer or you have some other purpose in mind?
I’m willing to use either the WP app or or a browser, but my personal preference is being able to do everything in a browser. Having the wpcom app is nice, but in no way necessary.
Since you mentioned this, it does not sound like troubleshooting the app is not your priority here so we’ll focus on your ability to export for now. We can circle back on the app after we sort that out, thanks!
-
Hi @jerry.
I’m pleased to hear you can replicate the export failure issue; what you have just detailed duplicates my experiences.
You are correct – the electron app is of comparatively minor concern to me.
I have exported my postings for well over a dozen years and I am aware of the differences between export data and a true backup.
I also understand WP takes reasonable precautions to keep the site and server safe; I merely appreciate having the ability to keep a current ‘mirror copy’ of my data.
As to the missing export feature, I feel a little lost without it and will be grateful when its function is restored.
-
Hi supernovia. (Cute username, BTW.) :)
To answer your question (much belatedly, sorry), it seems I’m going to have to take you up on your kind offer of generating a full export for me. It’s still not possible to export and I’ve several dozen new postings up every second week.
Since I’m publishing every second week and it’s been at least three publishing weeks since I brought the issue up, exports have been casters-up for over a somewhere a month and odds are there have been at least fifty posts since.
I’d be grateful for your help in getting a current export and TIA.
-
Hi jerrysarcastic.
Exports have been an ex-parrot since virtually forever – over a month at least.
Is there any ETA on a fix? My dentist is expressing concern with all the teeth-gnashing. ;)
-
I have sent an email with the export file attached.
Meanwhile, we’re continuing to look into the root cause.
-
Many thanks for your help, macmanx; I got it here.
I look forward to having export working again. :)
- The topic ‘export failures (both app and browser)’ is closed to new replies.
WordPress.com Forums 