deltafactory
Forum Replies Created
-
Thank you!
The issue I found was that the <input> with id=”php-[KEY]” was not created but the ajax request tries to get the value of that element for the post data.
There are multiple statements that query for an element and then attempt to use the object without checking whether one was found. This could be improved for overall stability.
To clarify, our customizations exclusively use hooks, filters, and template extensions which is should be a valid consideration during your development cycle. The key is that the version of WooCommerce is old enough that certain WC API/function calls do not exist where you assume they do.
There are a number of hooks that are registered for WooCommerce orders regardless the detection of WooCommerce. The stats gathering and subscriber syncing cannot be disabled in a non-invasive way, and have disrupted the checkout process in multiple ways.
I’m asking for minimal version/compatibility checks against a plugin that you are trying to integrate with. I’m also hoping for greater isolation of those integrations for those who find that level of data collection disruptive or inappropriate.
I am likely in the minority but I don’t think it’s appropriate that the plugin has decided that our customers are also subscribers, and has taken upon itself collating sales data about them.
It appears that your command-line version of PHP doesn’t have mysqli enabled, preventing WordPress itself from running properly. You could probably replicate this from running
php <web document root path>/index.phpYou might want to check your cron/command-line options with your hosting provider.
Forum: Plugins
In reply to: [Modern Events Calendar Lite] Extra close tags breaking layoutsThe sites were already using v4.4.5 PRO and had the issue that was reported.
The latest version of the lite plugin also still has the extra <div> tag at the end of it.
I would think so. This version of it is very purpose-driven and doesn’t do anything more than it needs to. If it works for you, keep using it.
Forum: Plugins
In reply to: [CDN Enabler] Cause error if content is PDF binaryI’m guessing that your dynamic PDF queries a post. The CDN plugin rewrites the content field of the post when retrieved. Could that be related to the issue?
Can you explain what it’s doing and what it should be doing instead?
Forum: Plugins
In reply to: [CDN Enabler] Uninstall PluginThe plugin will change URLs in your page’s HTML output to the CDN’s URL.
Not sure what you’re seeing and whether this plugin is the cause. Beware cached redirects, they’re a pain to get your browser to forget, short of emptying the entire browser cache for the site.
If you’re still having issues add some details of the redirect.
It’s not unreasonable for a plugin to raise memory just prior to a memory intensive operation.
It would be unreasonable to raise the memory for all page requests based on the possibility that one request of thousands might be memory intensive.
Forum: Plugins
In reply to: [Debug Bar Rewrite Rules] not working with wordpress latestStill happening. Changed method to public and it works fine.
Following up: I have confirmed that the output error/missing newsletter issue is caused by a separate plugin but is directly related to the size out of the output.
Optimizing/reducing the Newsletter listing request is still important me and my (premium) clients. Thanks.
I’m curious to know the reason as well, though I won’t go as far as to demand it. 🙂
Forum: Plugins
In reply to: [MailPoet - Newsletters, Email Marketing, and Automation] Newsletter problemPerhaps related to https://wordpress.org/support/topic/php-7-3-5/ ?
Forum: Plugins
In reply to: [MailPoet - Newsletters, Email Marketing, and Automation] PHP 7.3The dependency that is causing the issue, css-tidy, fixed this 2 weeks ago.
https://github.com/Cerdic/CSSTidy/commit/6342bdce367bd0b6b66ab715f749e18dae93eaf4Hopefully a future release of MailPoet will include the updated package.
Other plugins have the same problem as detailed here:
https://www.thenewsletterplugin.com/forums/topic/spamassassin-gets-crazy-uri-for-compromised-wordpress-site-possible-malwareIn short, SpamAssassin treats any email with a common WP path in a link URL as suspicious. If enough other points are added, it can flag the message as likely-SPAM.
@kitcummings had a similar issue:
https://wordpress.org/support/topic/uri_wp_hacked_2-uri-for-compromised-wordpress-site-possible-malware/This could be addressed with some URL rewriting but ideally SA could write a better rule.
Forum: Plugins
In reply to: [Force HTTPS (SSL Redirect & Fix Insecure Content)] PHP 7 CompatibilityThe quick fix should be to remove the & in front of $this in both of those lines.
I’ll submit a fix to the author.