Plugin need update ugently!

Thank you for the report. Judging by the error message, this could be a conflict with the plugin WP-PageNavi.

It looks like Error Log Monitor and WP-PageNavi both use a certain third-party library, but WP-PageNavi uses a custom version that includes a few additional bug fixes. The version included with Error Log Monitor doesn’t have those fixes. So when ELM is activated, it loads its version of the library annd WP-PageNavi tries to use that version, which triggers an error.

I’ve just released version 1.6.7 that should fix this error.

Thank you for prompt healthy attitude with fixing proactively the issue raised,however when attempted to updat the plugin it did not and receive this error on update page
“An error occurred while updating Error Log Monitor: Download failed. cURL error 28: Resolving timed out after 10001 milliseconds”

Once again,
Thank you for your confirmation as soon as accurately correctly completed today.

Keep up the good work!

That sounds like an issue either with the update server or the network connection. Unfortunately, that’s not something that I can fix. However, it’s probably just a temporary problem – please try again later.

Alternatively, you could also download the latest version manually and then upload it via FTP (overwriting the old version).

Did exactly s you just suggested still error exist
here is the exact text as reported by wordpress itself:

An error of type E_ERROR was caused in line 575 of the file /home/wp-content/plugins/error-log-monitor/scb/AdminPage.php. Error message: Uncaught Error: [] operator not supported for strings in /home/wp-content/plugins/error-log-monitor/scb/AdminPage.php:575 Stack trace: #0 /wp-includes/class-wp-hook.php(288): scbAdminPage->_action_link(”) #1 /home/wp-includes/plugin.php(208): WP_Hook->apply_filters(”, Array) #2 /wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/modules/Callables.php(324): apply_filters(‘plugin_action_l…’, ”, ‘wp-pagenavi/wp-…’, NULL, ‘all’) #3 /home/wp-includes/class-wp-hook.php(286): Automattic\Jetpack\Sync\Modules\Callables->set_plugin_action_links(Object(WP_Screen)) #4 /wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(false, Array) #5 /wp-includes/plugin.php(465): WP_Hook->do_action(Array) #6 /wp-admin/includes

Once again,
Thank you for your confirmation as soon as accurately correctly completed today.

Keep up the good work!

My apologies. I couldn’t reproduce this error on my own site, and I must have missed the real cause. Please try the development version instead.

Care to clarify,
Can you explain how the development version is a solution to the specific error issue given already?
How much extra time needed before fixing that error is accurately correctly completed?

The development version includes a new patch that should better address this issue.

How much extra time needed before fixing that error is accurately correctly completed?

Unfortunately, it’s impossible to answer that question. Since the error only happens on your site and not on my sites, I cannot reliably test the effectiveness of any attempted solution. It would be necessary to try the fix on your site before we can conclude that it actually works.

Then why not transfer the new patch to the current version as an update?

I was planning to do that once it’s been verified that the new patch works.

Hey @whiteshadow feel free to use my fork of SCB https://github.com/lesterchan/wp-scb-framework =)

• This reply was modified 5 years ago by Lester Chan.

Thanks! I already merged some of your fixes into my latest release.

Hello,

If one want to search the error log for a specific error,
is there an efficient way to do so from wordpress admin dashboard?
if not then how and where precisely one can search the error log to find a specific error?

Thank you for your confirmation as soon as accurately correctly completed today.

Keep up the good work!

No, this plugin currently doesn’t have the ability to search the log for specific errors.

One way to search the log would be to download the log file to your computer (e.g. via FTP), open it in a text editor and then search it with whatever search function(s) the text editor provides.

Alternatively, if you have shell access to the server, you could try the grep command.