James Jones

Thanks for the reply! Yes I already noticed through searching that nobody else is having this issue. It’s easily in the top 5 of strangest bugs I’ve ever encountered.

The issue is replicated on my local dev machine too, which is a simple LAMP setup on Ubuntu 24.04.

The 4 measures you suggested I’ve already checked with judicious use of print_r(), class_exists() and get_included_files() calls. The relevant files are definitely being loaded and seemingly in the correct order determined by your plugin’s init process. I’ve deactivated caching and on my local dev machine never had any caching in the first place. The staging site doesn’t use a CDN. What’s really odd is that I can confirm the class with correct namespace exists right before the class is declared with class_exists() but it throws the fatal error anyway.

The only thing I can suggest on your end would be to refactor the namespace tree a bit. Mostly I mean eliminate “plugin_core” for the high level classes so the children classes exist on a sub-namespace leading straight to these high level classes instead of a separate branch. But I understand that’s asking for a lot of refactoring for one user’s esoteric problem that may not even help.

If nothing else, this thread can provide a record in case someone else has the same problem. Hoping they’ll comment here and maybe we’ll see some commonalities with their situation.

You’re most welcome and thanks for listening.

I was using version 7.11.31. Your plugin recently updated to 7.11.32. If that file changed between versions it’d probably explain the discrepancy. Otherwise I’m not sure why.

• This reply was modified 5 years, 8 months ago by James Jones.

@zandpiloot

Thanks very much for the positive review! Yes, it’d be fairly difficult for WordPress to break this plugin. But I really should get onto updating it.

Hi RavanH,

Looks like your hunch was correct. That worked a charm. Thanks for that!

I don’t imagine there’s any way other solution at least not one that doesn’t involve a huge amount of work rewriting the plugin. Might be worth a note in your troubleshooting section.

Cheers,
James

@hudson-atwell

You’ve just got to think a little laterally and you’ll realise you don’t need any such constant in the plugin.

Put this code into your child theme or custom plugin:

<?php
add_filter('updraftplus_boot_backup', 'updraftplus_boot_backup');

function updraftplus_boot_backup() {
	if( defined( 'CUSTOM_DEACTIVATE_UPDRAFTPLUS_BOOT_BACKUP' ) && CUSTOM_DEACTIVATE_UPDRAFTPLUS_BOOT_BACKUP == true )
	    return false;
        return true
}

Then define that constant yourself in wp-config.php as true or false depending on whether it’s a staging site or live site.

• This reply was modified 6 years, 10 months ago by James Jones.

Hi Nathan,

I apologise for the late reply. I haven’t been monitoring this forum and didn’t see this message.

I looked up the team number 322711 and apparently it doesn’t exist. You can see this at https://fah-web.stanford.edu/cgi-bin/main.py?qtype=teampage&teamnum=322711. Contrast that with my team page and you see why you’re not getting any stats showing.

I’ll take a look at the error message that is thrown and see if I can make it more informative. I’ll also take a look at compatibility with the latest WordPress version, it should work fine in the WordPress 4.9.4 though.

Cheers,
James

Hi Ashley,

No apology needed. That snippet was very helpful and seems to have done just what I wanted. Thank you very much!

Cheers,
James

• This reply was modified 6 years, 11 months ago by James Jones.

Wow, would have taken me a while to think of trying a different Twitter account! Anyway, nice work and thank you! That CSS snippet has done the job for the time being.

I am not asking for support. I’m not confused. I’m not using your plugin at the moment. I was making a suggestion to improve user experience for users of your plugin. I suggest you add similar code to what you just suggested to your plugin.

I am talking about the WooCommerce options page. Not the options page for your plugin.

Thanks for the reply Adam. I’ve just submitted a pull request at https://github.com/Automattic/WP-Job-Manager/pull/551/files

@adam Hurlebaus

Thanks for the heads up. Issue created on github at https://github.com/Automattic/WP-Job-Manager/issues/542

Awesome thanks for the update David!!

Awesome thanks for the update David! I must admit that I went to one of your competitors on this project. But I generally prefer your plugin so will be back next time.