dogsday

@tekgirlymama
Been in this game a long time and I still have some ‘flat’ html sites running where functions are simple, even a few with very basic cart functions.
However, modern times require some broader services beyond simple code, and bespoke coding is beyond the means of the vast majority of us.
WP as a core is, IMHO, the best supported open platform at the moment and far far better than it was even 5 years ago.
Personally, I think the key is to keep the number of plugins per install to a minimum and to test vigorously on development sites. It’s far too easy to add plugins to get more functionality, but more functionality is not always a requirement.

DD

just tested 1.3.1 on a second production site previously showing the error when logged in and all is now working fine.
I have other test sites/sites in dev using the same theme as the two production ones showing a problem, also using LW as host, an there was no problem with them using 1.3, so maybe issue is with other plugins?

Hope others post some observations on this.

CF observations by @tekgirlymama are interesting, but could that affect DG plugin in this way? (I’ve had issues with CF an other plugins, but understand why, given that those plugins would be affected by caching pages)

Have tested one site (using DG1.3.1) and error seems to have been resolved.

No error-message on front-end when not logged in, nor when logged in as admin.

Will test a second site with virtually same set up and see what happens.

Any other users testes 1.3.1?

• This reply was modified 6 years ago by dogsday.

ok.
I’ll need to test on a production site exhibiting the problem as a test site that I was looking at was ok. Leave it with me a short while to backup etc and I’ll be back.

quick bit of further digging here…

The error shown is on the front end only when logged in as an admin (it would appear)

Here’s an example….

This page is front end not logged in with DG1.3 active as of a few mins ago…
https://www.zoeharcombe.com/2018/10/fiber-a-plausible-mechanism/

Screen grab of Same page when logged in
https://2020unlimited.co.uk/images/2018/DGerror20181029-2.png

Thanks for the tip on displaying errors. Will revert to someone much cleverer than I to get that looked into.

Happy to help if I can, but you may work out from the plugin list that these are not simple installs and switching to a default theme would cause site disruption.
I can try with a test environment if that would help?
Meanwhile, here’s how the error manifests front end on a site with the above setup, minus the simple press install..
https://2020unlimited.co.uk/images/2018/DGerror20181029.png

Feel for you on the debug. Here’s the environment for a site where I’m seeing the issue (Have reverted to DG 1.2 to keep working).

Happy to help with some more detailed info off-line.

WordPress
Version: 4.9.8
Language: en-GB
Character Set: UTF-8
Theme: ColorMag Pro Child

PHP
Version: 7.2.7-1+0~20180622080852.23+jessie~1.gbpfd8e2e
Memory: 256M
Max Upload: 10M
Timeout: 300

MySQL
Version: 5.5.5
Prefix: wp_

Server
Version: Apache/2.4

WP Plugins
Akismet Anti-Spam (4.0.8)
amr shortcode any widget (3.6)
CC Cookie Consent (1.2.0)
Custom Sidebars (3.2.1)
Disable Gutenberg (1.2)
Featured Images in RSS w/ Size and Position (1.4.8)
Google XML Sitemaps (4.0.9)
MemberPress Developer Edition (1.3.40)
MemberPress Developer Tools (1.1.17)
MemberPress User Roles (1.0.4)
Oomph Hidden Tags (0.2)
Really Simple SSL (3.1.1)
Simple:Press (5.7.5.3)
Simple Tags (2.4.7)
User Role Editor (4.46)
User Submitted Posts (20180822)
WP REST API (2.0-beta15)

I get the same error on a number of sites with same WP version but with different plugins.
The error is on the front end of the site, at the very top of a blog post (Have a screen grab if I can somehow send?).
Common to all is the hosting platform, Liquid Web. I’ve had another recent issue with a different plugin that seems unique to them. I see another poster refers to them too. Would the environment details help?

Thanks for the update, Jeff
For me, the problem shows up on WP 4.9.8 running Disable Gutenberg 1.3
DG 1.2 works fine.
Thanks again
DD

Same here, also on Liquid Web hosting following 1.3 update…
Warning: call_user_func_array() expects parameter 1 to be valid callback, function ‘disable_gutenberg_get_edit_post_link’ not found or invalid function name in /xxxxxxxxx/class-wp-hook.php on line 288