flowdee / ohdear

Oh Dear WordPress Plugin

Hey, I'm Florian 👋

I'm a passionated web developer from Germany 🇩🇪 who loves to build software and online services. 💻

Follow me on Twitter @flowdee 🐦

ohdear's Issues

Widgets should only be visible to at least editor role

Scheduled Tasks / WP Cron

Would love to add support for OhDear's scheduled tasks and track WP cron execution, so you can monitor if it runs properly on your site.

When you set up a "Scheduled Task" in OhDear, they give you a "Ping URL" which needs to be called frequently.

Besides that, you can set up the frequency how often the URL should be called (Grace period is unimportant for our implementation).

So the idea is, that on our settings page, we add a new section "Scheduled Tasks (WP Cron)", as well as the following settings:

• Ping URL (url field)
• Frequency (number field; values from 1 to 60; no comma)

When Ping url or frequency are empty, our plugin does not do anything here at all.

Once input is available, our plugin sets a custom cron interval based on the settings given: https://developer.wordpress.org/plugins/cron/understanding-wp-cron-scheduling/

For the event function, we just call the entered ohdear ping url.

Here's a example I currently used for our sites:

/*
 * Setup cron interval
 */
add_filter( 'cron_schedules', function ( $schedules ) {
   $schedules['fdmedia_cron_check'] = array(
       'interval' => 300,
       'display' => __( 'Every 5 Minutes' )
   );
   return $schedules;
} );

/*
 * Schedule cron event
 */
if ( ! wp_next_scheduled( 'fdmedia_site_cron_check' ) ) {
    wp_schedule_event( time(), 'fdmedia_cron_check', 'fdmedia_site_cron_check' );
}

/*
 * Cron check function
 */
add_action('fdmedia_site_cron_check', function() {
	// Call OhDear API
	$response = wp_remote_get( 'https://ping.ohdear.app/d0a8ea91-dd58-400b-8a3a-1835a6126f4e' );
	// Do nothing.
});

Prefix admin view HTML ids and classes

After the release we should optimize the views as follows:

All classes/ids should be prefixed with ohdear-. Otherwise, we risk overwriting global classes in the admin area, which we don't want on purpose.

Afterward, the CSS file must be updated as well.

FR: add MUWP support

Hi! Thanks for providing this handy plugin. Just started installing it.

I have a feature request. I'm running multiple Wordpress sites, based on 1 single install, using the multisite feature of wordpress.
I noticed I had to configure each website separately, which makes sense when separate websites are managed by separate people, who might have or not separate Oh Dear accounts.

It might perhaps make sense, to centralize configuration, for multisite setups, in a "Network Admin" admin page of said install?
Also, Multisite wordpress, also allows to define a domain alias for the site, so one can have "www.mylittleshop.com" instead of "littleshop.mymultisitewp.net". You might want to look at that and try to automap sites in WP with urls in Oh Dear.

Thank you for considering this. If you need testing, I'll gladly help.

Pre-Release Review

Redesign of their website

We must apply the redesign to the plugin by switching the logo/icon and also to the WP org header + logo graphics

Release 1.0.2

Could you please prepare & release version 1.0.2?

• Update version number in main plugin file + readme.txt
• readme.txt: Tested up to & stable tag
• readme.txt: Changelog
• Push to master
• Create and push tag 1.0.2
• Check if auto-deploy to wporg went through properly

Setup Airbrake for your PHP application

Installation

Install Airbrake using Composer by running the following command from your project's directory:

composer require airbrake/phpbrake

Configuration

Copy the following configuration snippet into your PHP app. It shows how to initialize Airbrake and register the instance as an error handler:

$notifier = new Airbrake\Notifier(array(
    'projectId' => 283568,
    'projectKey' => 'fc19f3848f145ddf8d713512df2a1085'
));

Airbrake\Instance::set($notifier);

$handler = new Airbrake\ErrorHandler($notifier);
$handler->register();

To send a test error, you can call Airbrake directly like in this try/catch example:

try {
    throw new Exception('hello from phpbrake');
} catch(Exception $e) {
    Airbrake\Instance::notify($e);
}

Framework integrations

• Symfony integration
• Monolog integration
• CakePHP 3.x integration
• Zend integration

Full documentation

Check out our official GitHub repo for info on additional features like:

• Adding custom data to your errors
• Filtering specific errors
• Extra config options

Dashboard Widgets

Wouldn't it be awesome if we could provide 3 Oh Dear dashboard widgets which you can drag & drop and show/hide if you need them?

• Uptime Widget
• Performance Widget
• Broken Links Widget

I would only show the widgets, after you entered an API key and a site was selected, of course.