Title: Roy Orbitson's Replies | WordPress.org --- # Roy Orbitson [ ](https://wordpress.org/support/users/lev0/) * [Profile](https://wordpress.org/support/users/lev0/) * [Topics Started](https://wordpress.org/support/users/lev0/topics/) * [Replies Created](https://wordpress.org/support/users/lev0/replies/) * [Reviews Written](https://wordpress.org/support/users/lev0/reviews/) * [Topics Replied To](https://wordpress.org/support/users/lev0/replied-to/) * [Engagements](https://wordpress.org/support/users/lev0/engagements/) * [Favorites](https://wordpress.org/support/users/lev0/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 81 total) 1 [2](https://wordpress.org/support/users/lev0/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/lev0/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/lev0/replies/page/4/?output_format=md) [5](https://wordpress.org/support/users/lev0/replies/page/5/?output_format=md) [6](https://wordpress.org/support/users/lev0/replies/page/6/?output_format=md) [→](https://wordpress.org/support/users/lev0/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Surfer – WordPress Plugin] Please fix the cron job](https://wordpress.org/support/topic/please-fix-the-cron-job/) * Thread Starter [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [5 months, 3 weeks ago](https://wordpress.org/support/topic/please-fix-the-cron-job/#post-18727566) * Seriously, what the heck are you doing? * `Surfer_GSC_Drop_Monitor::init()` makes sure that at 8am every Monday it runs` Surfer_GSC_Drop_Monitor::gather_position_monitor_data()`. This would be fine, but every time that function runs it dumps all its output, which nobody is requesting during a cron job, and it _does_ call `wp_die()`. * **You don’t call `wp_die()` in the middle of the site’s cron run!** * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Surfer – WordPress Plugin] Please fix the cron job](https://wordpress.org/support/topic/please-fix-the-cron-job/) * Thread Starter [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [9 months ago](https://wordpress.org/support/topic/please-fix-the-cron-job/#post-18594884) * Still occurring. * 🦗🦗🦗 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Easy WP SMTP – WordPress SMTP and Email Logs: Gmail, Office 365, Outlook, Custom SMTP, and more] Does not allow binding to a specific IP](https://wordpress.org/support/topic/does-not-allow-binding-to-a-specific-ip/) * Thread Starter [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [9 months, 4 weeks ago](https://wordpress.org/support/topic/does-not-allow-binding-to-a-specific-ip/#post-18558974) * > it’s not fully relevant for email providers like SendLayer, Mailgun, etc * But it is for other SMTP relays, and restricting by IP is a great additional measure as it prevents processing authentication when the origin is disallowed. * > only the provider’s IP address (i.e., the SMTP server’s IP) typically matters > in terms of email delivery reputation, SPF/DKIM/DMARC compliance, and spam > filtering. * I have seen mail sent via a relay, which doesn’t scrub `Received:` headers, be rejected because it contained IPs that weren’t in SPF, though the relay’s IP was. Adding the origin IP to SPF only works if it can reliably send from the correct IP. * > Most users use external SMTP providers (e.g., Gmail, SendLayer, SendGrid), > and these providers don’t care which IP your server uses to initiate the connection. * Gmail, when used with Google Workspace, has a specific config area that allows restrictions based on IPs, so it most definitely does care. Putting those restrictions on websites that need to send mail shouldn’t be the _only_ measure, but is just good security. It is also explicitly recommended in [Google’s help articles](https://support.google.com/a/answer/176600) that these restrictions be placed on devices that are unable to use OAuth. They wouldn’t make such recommendations if they didn’t care. * > PHPMailer acts as a client connecting to the SMTP server — the actual email > is sent out from the provider’s trusted infrastructure, not your server. * As I wrote above, some relays preserve the origin, so it must be correct. It’s more relevant to relays restricting incoming mail, and for that it can be critical. * I understand that SendLayer authors this plugin primarily to promote its own service, but it also presents the pluigin as being general purpose, and not being able to bind to an IP can make it a poor choice for that. * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Contact Form 7] Sadly, no emails received (due to the rigid rules)](https://wordpress.org/support/topic/sadly-no-emails-received-due-to-the-rigid-rules/) * [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [1 year, 2 months ago](https://wordpress.org/support/topic/sadly-no-emails-received-due-to-the-rigid-rules/#post-18342644) * This plugin does not change how email is delivered. It uses [the same core function of WordPress](https://developer.wordpress.org/reference/functions/wp_mail/) that everything else does. If you didn’t receive any email, you had something configured incorrectly. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[SMTP Mailer] Still uses sanitize_text_field() incorrectly](https://wordpress.org/support/topic/still-uses-sanitize_text_field-incorrectly/) * Thread Starter [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [1 year, 7 months ago](https://wordpress.org/support/topic/still-uses-sanitize_text_field-incorrectly/#post-18018768) * Don’t mark this as resolved if you have no intention of doing so. Users deserve to know what they’re getting. The code on SVN still uses raw `$_POST` everywhere, and `sanitize_text_field()` on fields that have nothing to do with HTML. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[SMTP Mailer] Still uses sanitize_text_field() incorrectly](https://wordpress.org/support/topic/still-uses-sanitize_text_field-incorrectly/) * Thread Starter [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [1 year, 10 months ago](https://wordpress.org/support/topic/still-uses-sanitize_text_field-incorrectly/#post-17845118) * I applaud your prompt response, but it’s still using `sanitize_text_field()` in several places it shouldn’t be, and using `$_POST`, directly, which [should not be done](https://developer.wordpress.org/reference/functions/stripslashes_deep/#user-contributed-notes) in WordPress without stripping slashes. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[More Mails for CF7] Conditional emails](https://wordpress.org/support/topic/conditional-emails/) * Plugin Author [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [2 years ago](https://wordpress.org/support/topic/conditional-emails/#post-17689101) * Hire someone. It’s explained in [this blog post](https://contactform7.com/2020/07/28/accessing-user-input-data/), the form could have a checkbox set like this: * ```wp-block-code [checkbox* interests use_label_element "a|Subject A" "b|Subject B" "c|Subject C"] ``` * Then something like this as the body of your custom plugin: * ```wp-block-code add_action( 'wpcf7_before_send_mail', function($contact_form, &$abort, $submission) { $interests = (array) $submission->get_posted_data('interests'); if (in_array('a', $interests)) $submission->add_extra_attachments('path/to/info-a.pdf'); ... }, 10, 3, ); ``` * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[More Mails for CF7] Conditional emails](https://wordpress.org/support/topic/conditional-emails/) * Plugin Author [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [2 years, 1 month ago](https://wordpress.org/support/topic/conditional-emails/#post-17682025) * Hi, * This plugin only creates the additional form parts for extra emails by duplicating what the original plugin uses in email (2). Since that does not have such conditional sending, nor do the extra ones. It’s not something I plan on building into this. * However, there is a filter called `wpcf7_additional_mail` in `[submission.php](https://plugins.trac.wordpress.org/browser/contact-form-7/trunk/includes/submission.php)` that can be used to inspect the current form submission and conditionally remove messages from that array. * The problem you’re describing isn’t necessarily a multiple emails issue. Wouldn’t it make more sense to send one email, but change its content and the set of attached files? That is also possible by using the filter/action hooks in CF7 and using` add_extra_attachments()`. * Regards. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Tiny gtag.js Analytics] GDPR / New Quebec 25 Law](https://wordpress.org/support/topic/gdpr-new-quebec-25-law/) * Plugin Author [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [2 years, 7 months ago](https://wordpress.org/support/topic/gdpr-new-quebec-25-law/#post-17078699) * Have a read of [Google’s consent docs](https://developers.google.com/tag-platform/security/guides/consent#tracking_consent_state). You could achieve this client-side (in the browser) by entering something like the following in the **Preliminary JavaScript** setting of this plugin: * ```wp-block-code gtag('consent', 'default', { 'ad_storage': 'denied', 'analytics_storage': 'denied' }); ``` * Then have your consent management code (pop-up, etc.) change that default if allowed with JS like this: * ```wp-block-code gtag('consent', 'update', { 'analytics_storage': 'granted' }); ``` * Alternatively, your own code (in plugins/themes) can use hook into this plugin’s` tiny_gtag_js_analytics_output` filter to modify the `pre_extra` value in options array. By default, this holds that same **Preliminary JavaScript** setting as above, which you could modify or replace based on the visitors’ consent responses. * It’s not feasible for me to have comprehensive privacy defaults for different jurisdictions around the world, or to integrate with the countless consent management tools available. I’ve made this plugin extensible so site owners can easily use the standard API that Google’s gtag.js provides. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Upload Media By URL] Fatal error in admin (with patch)](https://wordpress.org/support/topic/fatal-error-in-admin-with-patch/) * Thread Starter [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [2 years, 8 months ago](https://wordpress.org/support/topic/fatal-error-in-admin-with-patch/#post-16990686) * Oh, sorry about that. I added `admin_url('upload.php')` for the form action in my patched version and it works again. I used `printf` with `esc_attr__()` and` esc_html__()`, as it’s not advisable to pass raw HTML for translation. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Upload Media By URL] Fatal error in admin (with patch)](https://wordpress.org/support/topic/fatal-error-in-admin-with-patch/) * Thread Starter [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [2 years, 8 months ago](https://wordpress.org/support/topic/fatal-error-in-admin-with-patch/#post-16987605) * Thanks but you missed a bunch of the fixes in that patch: moving the permission check to after page check (permissions are irrelevant if you’re on the wrong page, and they’re slower to check); you lost the `href="#"` on the close/cancel buttons that avoid a full page reload; and you still have the `@media` CSS that’s no longer needed because the popup markup is now outside the footer. * Any reason you excluded the other improvements? Did you have problems with the patch as it was? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Upload Media By URL] Fatal error in admin (with patch)](https://wordpress.org/support/topic/fatal-error-in-admin-with-patch/) * Thread Starter [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [2 years, 8 months ago](https://wordpress.org/support/topic/fatal-error-in-admin-with-patch/#post-16982174) * Looks like this forum breaks `data:` URIs, but you can just add the scheme back to that link’s `href` to fix it. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Elementor Website Builder - more than just a page builder] CDN URLs broken by included webpack runtime](https://wordpress.org/support/topic/cdn-urls-broken-by-included-webpack-runtime/) * Thread Starter [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [2 years, 9 months ago](https://wordpress.org/support/topic/cdn-urls-broken-by-included-webpack-runtime/#post-16976108) * I was completely wrong about the cause. The runtime correctly detects public path, but then Elementor overrides the with its own config. The config property can be corrected by attaching to the `elementor/frontend/assets_url` filter in PHP, but it’s up to the site owner to add plugin code to do this, so the default behaviour of Elementor is still broken. It does not supply a similar filter for its `post.featuredImage` property, so one has to add a (temporary) filter to ` post_thumbnail_url`. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Memcached Redux] Maintainer](https://wordpress.org/support/topic/maintainer/) * Thread Starter [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [2 years, 9 months ago](https://wordpress.org/support/topic/maintainer/#post-16961427) * Or [@mikeschroder](https://wordpress.org/support/users/mikeschroder/)? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Tiny gtag.js Analytics] feature request：can support only visitor will loaded gtag，not logined user](https://wordpress.org/support/topic/feature-request%ef%bc%9acan-support-only-visitor-will-loaded-gtag%ef%bc%8cnot-logined-user/) * Plugin Author [Roy Orbitson](https://wordpress.org/support/users/lev0/) * (@lev0) * [2 years, 10 months ago](https://wordpress.org/support/topic/feature-request%ef%bc%9acan-support-only-visitor-will-loaded-gtag%ef%bc%8cnot-logined-user/#post-16853291) * Not a bad idea, I have seen other plugins do this. However, this is trivial to do yourself: create a plugin with only the following code, or add it to your theme’s functions file. * ```wp-block-code add_filter('tiny_gtag_js_analytics_output', function($options) { if (is_user_logged_in()) { $options['enabled'] = false; } return $options; }); ``` Viewing 15 replies - 1 through 15 (of 81 total) 1 [2](https://wordpress.org/support/users/lev0/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/lev0/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/lev0/replies/page/4/?output_format=md) [5](https://wordpress.org/support/users/lev0/replies/page/5/?output_format=md) [6](https://wordpress.org/support/users/lev0/replies/page/6/?output_format=md) [→](https://wordpress.org/support/users/lev0/replies/page/2/?output_format=md)