Paddy Duncan

@zemledelie – I just tried your link and the PDF loaded just fine for me in Chrome, Firefox Developer and Safari on a Mac. So I think maybe it’s a caching problem on your end.

Did you completely uninstall it from the Code Snippets SETTINGS page? If not, then do that – uninstalling using the WP plugin page apparently leaves the snippets behind in your database. (wp_snippets table if you look at the database in phpMyAdmin – the name of the table will vary, depending on what you named the database, but it will end with “snippets”)

Thanks – the postal code fix worked (just picked “English” instead of “auto” and that did it). Canadians do NOT generally like being confused with Americans. We know what zip codes are – but we, like the UK, don’t call them that. ?? We’re not collecting donations, but the terminology is important too, particularly as this is a petition (letter) re: a very local issue and absolutely nothing to do with the US.

As I noted, it would really be great if you could add in the ability to change the Call to Action text in a future release, as my clients didn’t really want to call this a “petition.”

• This reply was modified 2 years, 9 months ago by Paddy Duncan.

I’m seeing this same issue with the CSS showing a 404 – didn’t notice it until got Mobile Usability notices from Google and realized that a few clients’ sites were broken.

I do NOT have serve stale selected. Purging the cache resolved the issue and I haven’t seen it return (yet) – and have tried several sites in incognito mode just in case.

I am, in most cases, using CSS and JS minified and combined. Not using Quic Cloud. On shared hosting – these sites are all on Crocweb. Not all of my sites have done this, either; though many run a lot of the same plugins and all are custom-built GeneratePress sites, if that helps. If I find it happens again or with any other site, I’ll check back in here – unfortunately I’ve fixed all the sites where it was happening, as they were live client sites and the clients wouldn’t have been too happy to have them left that way. ?? I have a number of sites under development, but don’t usually turn the caching on until just before going live, so haven’t seen it there.

So I installed the code snippet – and now it leaves out everything in the email body. Plus it opens a small window in the browser when you click on the email icon (similar to what it does with Twitter or FB – but those are useable windows). It says “untitled” at the top, then a mailto: with the subject line – otherwise blank.

Tried uninstalling the plugin and reinstalling – no difference. Still no email content. Try it at https://urbanneighbourhoods.ca/phasing-out-ontarios-gas-fired-power-plants/ to see this behaviour.

And – I had a look at another site where I haven’t made any modifications, and discovered the email function isn’t working there either; in that case it does put a short text excerpt (first line from the post) in the email body, but there is no link. And it, for whatever reason, doesn’t say “check out this awesome post” – it has no additional text (which is what I’d prefer to have!!), even though it’s in the PHP when I look. Both of these sites are using v. 2.2 – so it’s rather odd that they’re outputting different results, especially as I didn’t make any changes in the second site. https://leasideresidents.ca/canadian-tire-on-lake-leaside/

On a third site, it creates the extra little window in the browser, adds the “awesome” bit (not as bad on a camp website…) adds the author name (not wanted at all – same as other site, it’s hidden on the posts) and adds the link in the email.
https://camphurontario.com/2021/03/18/registration-update/

—————-

On the second issue, given that the Twitter link doesn’t work if there is HTML inserted in Twitter meta field, then yes – it should strip out the HTML. There is no point in leaving it if it breaks it. And for those of us who use custom excerpts, it’s nice not to have yet another thing to remember to do.

• This reply was modified 3 years, 6 months ago by Paddy Duncan.

Further note: Twitter link goes sideways if you have a custom excerpt with HTML and don’t remove it from the metabox. (code shows up on the rendered page – not the Twitter icon)

Email leaves out the link if you have a custom excerpt in the metabox, with or without HTML. You can see this second issue on this page: https://leasideresidents.ca/mid-rise-consultations/ – no linky-link in the email. The only way to get it there is to remove everything from the metabox.

Note: there is actually no longer any need for this plugin, as the most recent version of GeneratePress Premium has added the Elements to the top menu in the admin dashboard with the most recent release. Given that, and the fact that it causes a fatal error with GPP, it should be removed from the WP repository.

dfactory was acquired by hu-manity. See: https://www.crunchbase.com/acquisition/hu-manity-co-acquires-digital-factory–c7f08e0d

Hu-manity is a relatively new company formed in 2018 in NJ. More info here: https://www.businesswire.com/news/home/20180605005581/en/New-Company-Hu-manity.co-Uses-Blockchain-to-Declare-a-31st-Human-Right-Empowering-All-Humans-to-Claim-Legal-Ownership-of-Inherent-Human-Data

Ziskov16, if you can’t even log into your site, can you log into Cpanel or whatever the control panel is for the backend of your website? If you can do that, you should be able to locate the plugins folder, and rename the old RLG plugin, which will deactivate it. Then try logging into WordPress again.

Instructions here: https://www.inmotionhosting.com/support/edu/wordpress/disable-wordpress-plugins/ (doesn’t matter who the host is – if it’s Cpanel it will look pretty much like this).

Hope that helps.

You should read the changelings. ??

For 14.04, in the bug fix section:

“In order to purge the wrong data, we need to truncate our tables again. This means you will have to go through the indexing process again. We’re very sorry.”

This 14.x release seems extremely buggy – 5 versions in 2 days. Luckily, none of my sites have exhibited any of the fatal errors others have experienced. (touch wood).

Boro, et al, I suggest you fix this right away. You’re wasting a lot of people’s time at the moment, as we have to drop everything to investigate the issue and (in my case) reassure clients that their sites are still working ok. <_<

Varun, 3.10 does resolve the problems caused by 3.9, so I’m not sure what is happening with your site. I would suggest that you clear your browser cache – and also try going to the site with a different browser/device, just to be sure that it’s not something persisting on your computer.

If that doesn’t work, then you will need to do one of two things:

Log in to your site via the hosting control panel (Cpanel? Plesk?) or via FTP and manually remove the plugin. The path: /wp-content/plugins/backupwordpress. You can probably just remove the entire folder – then reinstall 3.10. The backups themselves reside in another folder in wp-content.

If you really aren’t sure about any of this, it’s possible that your host tech support will be able to help you out. In my experience, a good host will do something relatively quick and simple like this if you’re not up to doing it yourself, but since managing a WordPress install usually isn’t part of normal hosting (ie: not managed WordPress) plans, it may be that they’ll say “no.” However, as long as you have access via FTP or cPanel, you should be able to do this yourself.

• This reply was modified 5 years, 5 months ago by Paddy Duncan.

3.10 has now been issued and it resolves all the problems caused by 3.9. Let’s hope the developer is a tad more careful about TESTING updates before releasing them in the future!!

I’m in the same boat, Harrison Ortega – and thought I’d gotten them all done, but one just came up now. Right now I’ve deactivated it on all sites, and am considering the alternatives. REALLY disappointed in the lack of response from the (new) developer and do not understand why WP hasn’t forced them to withdraw this update. Please come back, HumanMade…(and @xibodevelopment, if you’re not going to stand behind statements like “So we will be been actively providing support to users of BackupWordPress, and will be maintaining it as it’s an excellent and well-loved plugin.” then why make them? False promises…) ??

• This reply was modified 5 years, 5 months ago by Paddy Duncan.

Same here – have deactivated pending a fix.