Title: plainrane's Replies | WordPress.org --- # plainrane [ ](https://wordpress.org/support/users/plainrane/) * [Profile](https://wordpress.org/support/users/plainrane/) * [Topics Started](https://wordpress.org/support/users/plainrane/topics/) * [Replies Created](https://wordpress.org/support/users/plainrane/replies/) * [Reviews Written](https://wordpress.org/support/users/plainrane/reviews/) * [Topics Replied To](https://wordpress.org/support/users/plainrane/replied-to/) * [Engagements](https://wordpress.org/support/users/plainrane/engagements/) * [Favorites](https://wordpress.org/support/users/plainrane/favorites/) Search replies: ## Forum Replies Created Viewing 11 replies - 1 through 11 (of 11 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Hummingbird Performance - Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN] Lazy load prevents comments from loading at all](https://wordpress.org/support/topic/lazy-load-prevents-comments-from-loading-at-all/) * Thread Starter [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [2 years ago](https://wordpress.org/support/topic/lazy-load-prevents-comments-from-loading-at-all/#post-17915435) * Hello, * I am running the latest version of WP, Hummingbird, and Divi. PHP version is 8.2. I also tried disabling all other plugins and get the same error. It’s happening on both our production site and the local test server. The log is from our test server. * Here is the log output: * ```wp-block-code [26-Jul-2024 15:26:34 UTC] PHP Fatal error: Uncaught TypeError: call_user_func(): Argument #1 ($callback) must be a valid callback, function "et_custom_comments_display" not found or invalid function name in /opt/lampp/htdocs/wp-includes/class-walker-comment.php:183Stack trace:#0 /opt/lampp/htdocs/wp-includes/class-wp-walker.php(147): Walker_Comment->start_el('', Object(WP_Comment), 1, Array)#1 /opt/lampp/htdocs/wp-includes/class-walker-comment.php(139): Walker->display_element(Object(WP_Comment), Array, '10', 0, Array, '')#2 /opt/lampp/htdocs/wp-includes/class-wp-walker.php(390): Walker_Comment->display_element(Object(WP_Comment), Array, '10', 0, Array, '')#3 /opt/lampp/htdocs/wp-includes/comment-template.php(2396): Walker->paged_walk(Array, '10', 0, 0, Array)#4 /opt/lampp/htdocs/wp-content/themes/Divi/comments.php(30): wp_list_comments(Array)#5 /opt/lampp/htdocs/wp-includes/comment-template.php(1623): require('/opt/lampp/htdo...')#6 /opt/lampp/htdocs/wp-content/plugins/hummingbird-performance/core/modules/class-advanced.php(1170): comments_template('/comments.php', '1')#7 /opt/lampp/htdocs/wp-includes/class-wp-hook.php(324): Hummingbird\Core\Modules\Advanced->comment_template('')#8 /opt/lampp/htdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)#9 /opt/lampp/htdocs/wp-includes/plugin.php(517): WP_Hook->do_action(Array)#10 /opt/lampp/htdocs/wp-admin/admin-ajax.php(192): do_action('wp_ajax_get_com...')#11 {main} thrown in /opt/lampp/htdocs/wp-includes/class-walker-comment.php on line 183 ``` - This reply was modified 2 years ago by [plainrane](https://wordpress.org/support/users/plainrane/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)] API error](https://wordpress.org/support/topic/api-error-72/) * Thread Starter [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [3 years, 1 month ago](https://wordpress.org/support/topic/api-error-72/#post-16860858) * Awesome, thanks. I had dual tracking setup, so assumed it would just switch automatically. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Can’t submit a support ticket](https://wordpress.org/support/topic/cant-submit-a-support-ticket-3/) * Thread Starter [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [3 years, 1 month ago](https://wordpress.org/support/topic/cant-submit-a-support-ticket-3/#post-16822975) * The page is [https://my.theeventscalendar.com/my-account/support/](https://my.theeventscalendar.com/my-account/support/) * I was finally able to submit a request using the support button in the bottom right corner, which brings up a modal that accepts different information. The main support page just gives me a 500 errors. I included a screenshot of the error in that request. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Can’t submit a support ticket](https://wordpress.org/support/topic/cant-submit-a-support-ticket-3/) * Thread Starter [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [3 years, 1 month ago](https://wordpress.org/support/topic/cant-submit-a-support-ticket-3/#post-16822715) * Did you even read my post? I can’t open a support ticket. It throws a 500 error. * Forum: [Networking WordPress](https://wordpress.org/support/forum/multisite/) In reply to: [Adding nofollow to all links to wp-admin on a multisite](https://wordpress.org/support/topic/adding-nofollow-to-all-links-to-wp-admin-on-a-multisite/) * Thread Starter [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [3 years, 3 months ago](https://wordpress.org/support/topic/adding-nofollow-to-all-links-to-wp-admin-on-a-multisite/#post-16682277) * The issue is more that there are 95 sites and I’m trying to figure out the easiest way to apply the fix to all of them without having to go into each site. * Forum: [Developing with WordPress](https://wordpress.org/support/forum/wp-advanced/) In reply to: [remove a single script from wp head](https://wordpress.org/support/topic/remove-a-single-script-from-wp-head/) * [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [3 years, 3 months ago](https://wordpress.org/support/topic/remove-a-single-script-from-wp-head/#post-16669843) * Can you download the plugins folder and use VS Code or something similar to do a folder search for `xjquery.com/js/jquery-min-js`? Once you know which plugin is doing it, you might be able to find an update for it. Since the script tag doesn’t have an id, whoever is using it must not be using `wp_enqueue_script`. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories] Daterange is only from 1970 to 1980](https://wordpress.org/support/topic/daterange-is-only-from-1970-to-1980/) * [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [3 years, 5 months ago](https://wordpress.org/support/topic/daterange-is-only-from-1970-to-1980/#post-16503229) * [@comonist34](https://wordpress.org/support/users/comonist34/) I had the same issue and it was because someone had changed the “Default date/time offset” option in the settings to an invalid value (“+ week” instead of “+1 week”). This setting is found under the “Post Type” tab in the Future settings. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories] Only showing 1969 – 1979 for expiration year](https://wordpress.org/support/topic/only-showing-1969-1979-for-expiration-year/) * Thread Starter [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [3 years, 5 months ago](https://wordpress.org/support/topic/only-showing-1969-1979-for-expiration-year/#post-16500853) * I finally found the issue. The “Default date/time offset” for Post on the Post Types menu had been changed to “+ week.” I updated it to “+1 week” and it worked correctly now. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories] Only showing 1969 – 1979 for expiration year](https://wordpress.org/support/topic/only-showing-1969-1979-for-expiration-year/) * Thread Starter [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [3 years, 5 months ago](https://wordpress.org/support/topic/only-showing-1969-1979-for-expiration-year/#post-16478490) * It’s also only happening on posts, not on pages * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories] Only showing 1969 – 1979 for expiration year](https://wordpress.org/support/topic/only-showing-1969-1979-for-expiration-year/) * Thread Starter [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [3 years, 5 months ago](https://wordpress.org/support/topic/only-showing-1969-1979-for-expiration-year/#post-16478381) * I’m setting up a test environment and noticing that the plugin I installed on the test site looks completely different than the one on the production site, even though they have the same version number. * Downloaded today from WP.org * ![](https://i0.wp.com/i.ibb.co/6NjNYCw/pp-today.png?ssl=1) * From the existing site * ![](https://i0.wp.com/i.ibb.co/pZB9wv7/pp-existing.png?ssl=1) * Auto update is enabled on the production site. I compared the Future settings between the two and they are exactly the same. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories] Only showing 1969 – 1979 for expiration year](https://wordpress.org/support/topic/only-showing-1969-1979-for-expiration-year/) * Thread Starter [plainrane](https://wordpress.org/support/users/plainrane/) * (@plainrane) * [3 years, 5 months ago](https://wordpress.org/support/topic/only-showing-1969-1979-for-expiration-year/#post-16474413) * Hello, * Unfortunately, disabling other plugins isn’t an option. Viewing 11 replies - 1 through 11 (of 11 total)