Dave
Forum Replies Created
-
Forum: Plugins
In reply to: [Ally - Web Accessibility & Usability] Update v4.0.0 crashes sitesAha, I see now @dubovikia – Well, thank you for pointing this out to us then, much appreciated!
Forum: Plugins
In reply to: [Ally - Web Accessibility & Usability] Update v4.0.0 crashes sitesHi @dubovikia. I just installed the update and here it works.
Thank you for the quick fix π
Forum: Plugins
In reply to: [Ally - Web Accessibility & Usability] Update v4.0.0 crashes sitesHi there,
Yes, same here. On our site we also get a critical error:
Stack trace:
#0 /public_html/wp-content/plugins/pojo-accessibility/modules/connect/module.php(31): EA11y\Modules\Connect\Module::get_connect()
#1 /public_html/wp-content/plugins/pojo-accessibility/modules/legacy/module.php(64): EA11y\Modules\Connect\Module::is_connected()
#2 /public_html/wp-content/plugins/pojo-accessibility/includes/manager.php(48): EA11y\Modules\Legacy\Module::is_active()
#3 /public_html/wp-content/plugins/pojo-accessibility/plugin.php(92): EA11y\Manager->__construct()
#4 /public_html/wp-content/plugins/pojo-accessibility/plugin.php(107): EA11y\Plugin->includes()
#5 /public_html/wp-content/plugins/pojo-accessibility/plugin.php(49): EA11y\Plugin->__construct()
#6 /public_html/wp-content/plugins/pojo-accessibility/plugin.php(111): EA11y\Plugin::instance()
#7 /public_html/wp-content/plugins/pojo-accessibility/pojo-accessibility.php(78): require_once('/home/customer/...')
#8 /public_html/wp-includes/class-wp-hook.php(341): Pojo_Accessibility->init('')
#9 /public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array)
#10 /public_html/wp-includes/plugin.php(522): WP_Hook->do_action(Array)
#11 /public_html/wp-settings.php(593): do_action('plugins_loaded')
#12 /public_html/wp-config.php(94): require_once('/home/customer/...')
#13 /public_html/wp-load.php(50): require_once('/home/customer/...')
#14 /public_html/wp-blog-header.php(13): require_once('/home/customer/...')
#15 /public_html/index.php(17): require('/home/customer/...')
#16 {main}
thrown in /public_html/wp-content/plugins/pojo-accessibility/modules/connect/module.php on line 38Additional info:
- WP version: 6.9
- All other plugins up-to-date
- Divi theme (with child theme)
- Apache server with PHP 8.1
Happy to provide more info if it helps. Thank you for looking into this.
Dave
Hey Jyoti, that’s good to know. I’ll look into it. Thank you for bringing it to my attention π
Thank you very much Jyoti – that will be exciting!
Thanks for your help π
Forum: Plugins
In reply to: [YMC Filter] Callback Function no longer found after 3.0 updateThank you for pointing me in the right direction. This is now working again for version 3 of the plugin. I’m sharing my new code below for reference.
Thanks again π
/**
* FILTERS & GRIDS v3+ β callback-based advanced query
*/
/**
* 1) Whitelist callback (global).
*/
add_filter('ymc/filter/query/wp/allowed_callbacks', function ($callbacks) {
$callbacks[] = 'ww_filter_cpt_by_terms_v3';
return $callbacks;
});
/**
* 2) The callback: returns WP_Query args.
*
* @param array $ctx {
* @type array $post_type List of post type slugs.
* @type array $taxonomy List of taxonomy slugs.
* @type array $terms List of term IDs to filter by.
* @type int $page_id Current page ID.
* }
* @return array WP_Query args
*/
function ww_filter_cpt_by_terms_v3( $ctx ) {
// Normalize inputs from plugin context
$post_types = !empty($ctx['post_type']) && is_array($ctx['post_type'])
? array_map('sanitize_key', $ctx['post_type'])
: array('post');
// We implement AND within a single taxonomy (use the first provided).
$taxonomy = !empty($ctx['taxonomy']) && is_array($ctx['taxonomy'])
? sanitize_key($ctx['taxonomy'][0])
: '';
$terms = !empty($ctx['terms']) && is_array($ctx['terms'])
? array_values(array_filter(array_map('intval', $ctx['terms'])))
: array();
// Base query (also used for "show all" fallback)
$base = array(
'post_type' => $post_types,
'posts_per_page' => -1,
'post_status' => 'publish',
'ignore_sticky_posts' => true,
);
// No taxonomy provided? Show all for the chosen post type(s).
if (empty($taxonomy)) {
return $base;
}
// Determine βall selectedβ to trigger the fallback.
$active_term_ids = get_terms(array(
'taxonomy' => $taxonomy,
'fields' => 'ids',
'hide_empty' => true,
));
if (is_wp_error($active_term_ids)) {
$active_term_ids = array();
}
// Fallback to "show all" when no terms selected OR effectively all selected
if (empty($terms) || ($active_term_ids && count(array_unique($terms)) >= count($active_term_ids))) {
return $base;
}
// True AND filtering within the single taxonomy selected.
$base['tax_query'] = array(
array(
'taxonomy' => $taxonomy,
'field' => 'term_id', // important: use term_id
'terms' => $terms,
'operator' => 'AND',
),
);
return $base;
}Forum: Fixing WordPress
In reply to: how to kill sudden fake users registrationYes, it’s weird. That’s why I thought are they real emails coming from your website? Or is it just your email getting spammed? I mean, I could write an email message with the content that a new user has been registered on a website and send that out hundreds of times… What happens if you block your site from sending emails altogether with something like “Disable Emails Plugin”? Do you still get those emails then? If yes, they are not coming from your site and you can start looking at preventing email spam instead. It’s just a hunch, but maybe it helps…
Forum: Fixing WordPress
In reply to: how to kill sudden fake users registrationAre you sure new users are actually registered? Could also simply be fake emails?
I’d be sure to check in the database for users and see if there are any that shouldn’t be there.
If your site is not open to new user registration you could also consider blocking it completely. A search for “Disable User Registration in WordPress” would give you several options: through settings, .htaccess, or programatically.
If the emails are not fake, I’d also check themes and plugins and run a malware scan on the site with a plugin such as Wordfence.
I hope this helps. Good luck!
- This reply was modified 8 months ago by Dave.
Forum: Fixing WordPress
In reply to: Website too old. Better copy or staging?Hey, that sounds tricky. I”ve updated old websites in the past that hadn’t received any maintenance for years, and for me a multistep proces has worked, where I first made smaller/minor updates, before attempting bigger updates.
I’d make a backup first, if possible through your host. Then also maybe take a static backup of the site with a tool such as WinHTTrack website copier. This wouldn’t give you back WordPress if anything went wrong, but at least you’d be able to recover content. Also, take an export of the content through Tools > Export. And then a backup with a backup plugin such as Duplicator (possibly download and install an older version of the plugin that’s still compatible with your older PHP version).
Then with backups sorted best as you can, try updating as follows:- Update to PHP 7.3 or 7.4 and check the site to see if anything breaks.
- Update the database to an intermediate version first if possible
- Update WordPress an intermediate version
- At this point some things might break and you might get some warnings, but hopefully the site stays accessible – you can fix those warnings later
- Update to PHP 8.0 – check the site
- Update database again to a higher version
- Update all plugins and themes to their latest versions
- Update WordPress to the latest version
For me such a staged approach has worked a few times, but it’s delicate. Be prepared to test a lot, roll back PHP or database version (if possible), troubleshoot, and find and use older versions of plugins and WordPress by doing manual updates instead of automatic ones. If things don’t work out, you can note at what point it went wrong, reset PHP and database to how it was when you started, and reinstall the site with your Duplicator package, then try again.
If you can do it all on a staging site, that’s great. And if you can get it to work on there, it should work on the live site as well. Just be mindful if you can change PHP and database version on your staging site independently from your live site, otherwise things will break on the live site when you start changing versions.
I hope this helps a little. Good luck!
Forum: Plugins
In reply to: [Deposits & Partial Payments for WooCommerce] PHP WarningThank you for the support.
Forum: Plugins
In reply to: [Deposits & Partial Payments for WooCommerce] PHP WarningHi Sanesh, thank you for getting back to me about this. Yes, I’ll be in touch over live chat about this. Thank you.
Thank you Tino: “Run on existing user” and creating a new user if no user found – that did the trick for me.
This way both existing users and new users/guests can get something in my WooCommerce shop and then be added to my list in Mailerlite, which is exactly what I wanted.
This is a screenshot of my current settings:

Works great, thank you @tinocalvo π π
Thank you for your help @tinocalvo – all sorted now.
Linking to the other ticket just in case (I accidentally created 2 for some reason): https://wordpress.org/support/topic/woocommerce-user-triggers-seem-not-available/
π π
Forum: Plugins
In reply to: [CBX Bookmark & Favorite] Bookmarks limit and pagination?Great Sabuj. Thank you for clarifying that.
Forum: Plugins
In reply to: [CBX Bookmark & Favorite] Bookmarks limit and pagination?Thank you very much Sabuj @manchumahara π
I will consider the pro version for the bookmark limit. So without it people can have unlimited bookmarks, is that correct?
All clear about the shortcode – thank you for linking to the documentation for that. I’m using the customizer integration right now, but I may switch to the shortcode way then.
Thanks again π
Dave