jqz
Forum Replies Created
-
Just looked at the logging function,
stcr_utils::stcr_logger()– it seems the actual logging is behind an optionsubscribe_reloaded_enable_log_data, the default being off (and the log file is a.txtfile in the root directory of the STCR plugin installation folder, so I have answered my own question).What this means is that this plugin being active causes all PHP errors and notices to disappear into a black hole (unless the above option is manually changed from the default, wherever it is in the settings – I can’t find it on a quick glance through).
This is quite a significant bug. It means that minor errors anywhere on your website will go unnoticed. Then they will become major errors as you find an small innocuous upgrade or change breaks your site. Or there are some pages on your site that have errors and don’t load but you don’t immediately find out about them because they are not being logged.
My original file is not being included by
wordfence-waf.php, which looks like this:<?php // Before removing this file, please verify the PHP ini setting <code>auto_prepend_file</code> does not point to this. if (file_exists(__DIR__.'/wp-content/plugins/wordfence/waf/bootstrap.php')) { define("WFWAF_LOG_PATH", __DIR__.'/wp-content/wflogs/'); include_once __DIR__.'/wp-content/plugins/wordfence/waf/bootstrap.php'; }Should I just add an
includefor my file at the top of it, or is there some setting within the admin UI that would do this?Forum: Plugins
In reply to: [Product page shipping calculator for WooCommerce] English translationPossibly also “location” rather than “area” would be more commonly expected.
Forum: Reviews
In reply to: [**RapidDive** BARCLAY ePDQ Payment Gateway] Still WorksI hope the new version also works.
Yes, except that version 2.3.3+ seems to be no longer compatible with PHP 5.6, so ought to have had a bigger bump to the version number (though I guess you might not have tested against PHP 5.6 – it is well beyond EOL, for which reason I have not had time either to double-check this is the cause).
Forum: Plugins
In reply to: [Category Editor] Broken markup in category editorThe issue doesn’t affect the visual appearance of the category editor page for posts, but does affect the apparance of the product category editor page for WooCommerce product categories, because, as a result, additional fields added by WooCommerce are not in the
table.However, the invalid markup can be seen in both cases via ‘Web Developer > Page Source’ in Firefox (see https://www.qzdesign.co.uk/filetransfer/category-editor-markup.png – the errors are highlighted in red by Firefox itself). The extra
<table>start tag is not permitted here because it is not within a table cell (tdorth) – it doesn’t nest the tables but causes the first one to be closed and a new one to be started. The additional</table>closing tag means the fields added by WooCommerce are not in a table at all.- This reply was modified 5 years, 8 months ago by jqz.
Forum: Plugins
In reply to: [Category Editor] Broken markup in category editorIt’s on the ‘Edit Category’ admin page, e.g.
[host]/wp-admin/term.php?taxonomy=category&tag_ID=1&post_type=post. Theme is not relevant; it’s reproducible with the Twenty Twenty theme. I’ve double-checked with all other plugins disabled.Please contact our internal support team.
We need more information to find the cause of this failure.Turns out that custom taxonomies are only supported in the Pro version.
I am using a different plugin now for the current project.
To be fair, I tested about half a dozen similar plugins and all but one failed to pick up the custom taxonomy. To clarify, I mean a standard WordPress taxonomy (like proudct category or tag), not a ‘WooCommerce attribute taxonomy’ (which is a WordPress
termbut not a WordPresstaxonomy, AFAICS, using the precise but curious WordPress jargon).Hopefully that is enough for you to go on to see what is lacking.
I will certainly revisit your plugin for future projects 🙂
The taxonomy is a standard WordPress hierarchical taxonomy, registered using
register_taxonomy()with the$object_typeargument set toproduct, in exactly the same was as theproduct_cat(product category) taxonomy is registered.Thus products may be classified by this custom taxonomy as well as product categories and tags.
- This reply was modified 5 years, 10 months ago by jqz.
This doesn’t seem to help. Fields are not taxonomies. And in any case, neither method, including paid options, would appear to cater for hierarchical taxonomies.
Also, Akismet gets to read all your messages. What T&Cs have you agreed regarding privacy and data protection?
cPanel just picked up spam that this didn’t, because I forwarded a message:
SMTP error from remote mail server after end of data: 552 5.2.0 rahljx192QaXD :: CPANEL :: Message rejected for spam or virus content :: Please include this entire message when contacting support ::It was just text that Akismet DID NOT pick up as spam. (FAOD, it was a message submitted via comment form that Akismet said was OK.)
- This reply was modified 6 years ago by jqz.
If WordPress wasn’t so open to spam you wouldn’t have such a problem. There are many more effective ways of dealing with it that this plugin does not provide (e.g. honeypot fields in forms). These should be as standard in WordPress, IMO.
Forum: Plugins
In reply to: [All-in-One WP Migration and Backup] Export file is too big> Why was this feature removed?
Any answer from the developers?
A while ago I was considering giving your plugin a 5* review, as it has proved very useful. But probably not now…
