by Andrew Ferguson 1 (0 reviews)

Dunstan-style Error Page

Name: Dunstan-style Error Page
Author: Andrew Ferguson

See http://www.andrewferguson.net/wordpress-plugins/dunstan-style-error-page/ for the latest updates.

Dunstan-style Error Page ranks #43,563 among WordPress.org plugins with 10+ active installations, is #684 of 1,908 in the Calendar & Events category, a 1/5 rating from 0 reviews, and was last updated Mar 23, 2007. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 2.1 (Current: 7.1.1)

v1.3.1 Current Version v1.3.1

Updated 19 years ago Last Update on 23 Mar, 2007

Refreshed 17 hours ago Last Refreshed on

#684 of 1,908 in Calendar & Events Top 50% by installs No update in over a year

View on WordPress.org

Rank

#43,563

+3064 this week

Active Installs

10+

— No change

KW Avg Position

N/A

— No change

Downloads

4.7K

+1 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 20

Total Progress 30%

10+ 20+

41,493

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 7 more installs to reach 20+

Rank Changes

Current #43,563

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.3.1
Last Updated: Mar 23, 2007
Requires WP: 1.5+
Tested Up To: 2.1
PHP Version: N/A
Author: Andrew Ferguson

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

Event count countdown date timer

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,758

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

BackWPup – WordPress Backup & Restore Plugin

400K+ installs

#134

LightStart - Maintenance Mode, Coming Soon and Landing Page Builder

400K+ installs

#136

Activity Log – Monitor User and Agent Changes

200K+ installs

#219

Popup Builder - Create highly converting, mobile friendly marketing popups.

200K+ installs

#271

Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress

100K+ installs

#363

پارسی دیت – Parsi Date

100K+ installs

#379

Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories

100K+ installs

#407

View all Calendar-and-events plugins

Frequently Asked Questions

Common questions about Dunstan-style Error Page

http://faq.wordpress.com/2005/10/19/api-key/

This is known problem and a fix will be rolled into the next release. In the meantime, read on: Apache makes a note below the ErrorDocument documentation: Microsoft Internet Explorer (MSIE) will by default ignore server-generated error messages when they are "too small" and substitute its own "friendly" error messages. The size threshold varies depending on the type of error, but in general, if you make your error document greater than 512 bytes, then MSIE will show the server-generated error rather than masking it. More information is available in Microsoft Knowledge Base article Q294807. My best recommendation is to inflate the size of the error document. But some garbage text between two comment tags and see what that does.

This is also a known problem and I'm working on a way to combat it. In the mean time, your best bet would be to disable the quick error report part. There are several ways you could do it, but the easiest and cleanest is to just remove lines 395 to 403: Quick error report ... </form>