nickpagz

Hmm, this is marked as resolved but it’s not a viable solution. Jooble “crawls” the xml feed every 24 hours (as a default), so a better solution is required since the one presented won’t work.

Nice! Thanks!

Just wondering if this is going to get a response or not? I’m seeing other posts on here getting multiple responses since I posted this. At least an acknowledgement or something that it’s been seen and a response is being formulated?
Thanks.

Sure! #268205

I had a long back and forth email chain with the developers who somehow refused to see this as a bug, so it was never resolved, and I don’t believe they intend to fix it. That’s beyond me – for them to think that changing your entire site’s color scheme to edit content is an acceptable solution, but hey, what do I know!
I ended up changing color schemes anyways, so in the end it was no longer an issue for me.
Too bad really, Astra is a great theme, just sad the developers can’t see this is as an issue.

This was on a local install, so to remove any doubt I did a fresh WordPress install on a server and installed the latest version of the free theme. Not a single plugin is installed on the site – and this issue persists.
To be clear, if I use a box layout, the “boxed” area has a white bg, so the text is not visible at all if it’s white while the bg setting is dark, FE or in the editor. On a full width layout, it works better, but in the editor some blocks still have a white bg making the text not visible – like the shortcode block for example.
In any case, I’ve submitted a ticket per your request.

PS. Even with the Colors & Background Astra Pro module deactivated, it’s still an issue with some blocks, like the shortcode block for example.

And BTW, I would not be willing to pay for this plugin since it has always been free (thanks to the open source WordPress community), and would hate to see it go that way, making it more difficult/expensive for people who want to migrate from Blogger to WordPress.

As it is, I’m not a fan of pipdig’s license they use on their themes, which seems to go against GNU/Open Source principals, and is not inline with the license agreements of the big theme players out there (Genesis, ElegantThemes, etc) that rely on the fact that WordPress IS open source and respect that, IMO. Just sayin’!

@wpusermv I can see what you’re saying, but to be honest, pipdig have inherited these issues (yes, they were always there, including the image href issue) and it’s the only real option compared to the built in blogger importer. I’m sure in time they will address and fix these issues.

FWIW, I ran two test imports of the same site onto separate local WP installs to see which worked better. One site used the standard blogger importer, importing the xml file, and the other used this plugin.

Looking at the results, the built in blogger importer requires more clean-up and work than this plugin. For example, pages aren’t imported, only published/approved comments are imported, and worst of all, the importer created featured images out of PayPal button images (or other random images) on posts where there weren’t featured images.

For me, I would rather live with the image link pointing to blogspot and overcome the issue by using a lighbox to display the image (instead of it redirecting), and then pay someone on Upwork or Fiverr to manually fix them for me – while pipdig works on fixing the issue ??

But that’s just my 2 cents.

@pipdig No worries. And for the record, to fix the broken permalinks after import I’ve been using this plugin.

The issue @wpusermv is mentioning has always been there. On some sites it worked ok, but on most it doesn’t, unfortunately. It’s not all that bad, as long as you don’t close your blogger account. Making it Private is ok. The images are imported to WordPress, at least the smaller versions, and are correctly linked to in the posts and pages (as src=). The issue is basically it comes in with a “link to” (or href) url which links to the full size image on blogspot’s CDN or image server.

To be honest, I believe the plugin works correctly, and the issue is how blogger links to full size versions of the images. The plugin couldn’t possibly know what’s a legitimate “link to”/href external image or other link vs a blogger one. Possibly with some crafty coding it could be modified to recognize what the blogger CDN or image server addresses are, and when it sees these, download the linked images instead, and insert those into the post instead.

Since a bulk removal of the “link to”/href isn’t really possible (that I’ve discovered anyways), another option would be to remove these during the import – if you could figure out which are legitimate vs blogger external links/images. The downside here is that you would only get the lower resolution image imported, which is the case now anyways – except with the added external image link.

I also tried running a few “Import External Images” plugins, but they don’t work since the links href links, and not external src links.

I do have another site to import later this week, so I’ll see if I can get examples and post them here if it happens on this one. I might also do some testing to see what can be done on the blogger site before import to help. I had tried turning off the lightbox setting in the past, but this didn’t help, and hence the reason I think it’s how blogger links to larger versions of the images shown in the posts and pages.

Hi @supportray ,

I tried all that stuff and it didn’t work. It could have been a caching issue with Cloudflare, but I’m not sure. I did get it working though, not sure how, but here were the steps I made.

– Note: I am running Extra theme by Elegant Themes which uses the Divi builder. This is set to only run on Pages.

– I decided to try looking for the block in a new page to make sure it wasn’t just not on posts.
– When adding a new Page, the Divi page builder prompted me asking if I wanted to use the Page builder or stick with the default editor. I chose the default editor.
– At the that point, the TA Image block was then visible and working.
– I then switched back to a post, and the block was now also visible on posts.

Again, seems a bit odd, but it looked like some kind of conflict with the Divi builder – unless it really was just coincidence and the WordPress planets aligned at that moment and it started working. ˉ\_(ツ)_/ˉ

If I get a chance I can run a test setup on another site and see if I can repeat the behavior.

Cheers

Update:
I can see the block on another site I have, so very curious to know why it works on one site and not another?
Are there any known conflicts with other plugins or themes that would block it from showing? Both sites have the same plugins for security and caching, though the one that’s not working is running through cloudflare, and using the Extra theme from Elegant Themes.
The site is blogger2wp.com.
Any thoughts or trouble-shooting tips would be helpful.
Thanks.

Thanks!

Yeah, the module is turned off, so the site loads normally now. But sure, I’ll add this into the support form.

Also, I’ll ask the owner if she’ll allow me to create a staging site where I can turn the module back on and you can test a bit more.

Sure.
The Interviews category had only one post with embeds, so loaded a bit faster.

The home page had two posts, 2 and 4, so this page took the longest to load.