archon810
Forum Replies Created
-
@davdebcom We use composer for plugins, plus I’m really busy right now, so I’ll take a pass this time. Hope you can find testers and release soon. We had to pause deprecated warning reporting to Sentry and logs, so I’m looking forward to the fix and getting those re-enabled.
Just updated to PHP 7.2 and started seeing these as well.
Forum: Plugins
In reply to: [Date/Time Now Button] DateTimeNowButton has a deprecated constructorI hope the dev will fix it so we don’t have to fork it just for this fix.
Forum: Plugins
In reply to: [Regenerate Thumbnails] Feature request: Run on specific time slicesThe reason is when I want to reprocess just a certain month because I know something screwed up or needs to be reprocessed for whatever reason. I’m sort of scared of running it on 7 years worth of images, so I’d rather take it slower, but 350 APKs at a time isn’t ideal either (as per the other thread).
I do have access to wp-cli, but I’m not familiar with using it at all at the moment. It sounds like it’d need some scripting to query for media IDs, then passing them to wp-cli.
Alright, I found the issue by stepping through your code with a debugger.
Turns out this is a misnamed webp file. It fails precisely here:
file_is_displayable_image()Bah, false alarm!
May I suggest a better error message, however?
Afraid it’s not very helpful.
{“error”:”"307889-PDP-Overview-SSGS7-Active-img2@2x" (ID 455763) failed to resize. The error message was: Unknown failure reason.”}
Sure, let me check.
Awesome! A complete rewrite is pretty scary to use on a prod install right away, any chance of a quick hotfix on the current base?
Wanted to clarify the file name on disk. It’s “nexus2cee_307889-PDP-Overview-SSGS7-Active-img2@2x.png”
Also, oddly, this one (maybe the space in the name?):
“carbon black-hero” (ID 455765) failed to resize. The error message was: Unknown failure reason.
The file info is:
“carbon black-hero
File name: nexus2cee_carbon-black-hero.jpg”Edit: Actually, disregard this one. It’s an invalid jpg.
- This reply was modified 8 years, 6 months ago by archon810.
Forum: Plugins
In reply to: [Disable REST API] Restrict plug-in use of REST APIThanks for the quick response, @dmchale.
Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 (Version 4.8) – Sending does not workI left a suggestion for the author of https://wordpress.org/plugins/disable-json-api/ to enable whitelisting API endpoints so we could get the two plugins to work together here: https://wordpress.org/support/topic/restrict-plug-in-use-of-rest-api/#post-9396702. Chime in there if you’d like it to happen.
Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 REST APII left a suggestion for the author of https://wordpress.org/plugins/disable-json-api/ to enable whitelisting API endpoints so we could get the two plugins to work together here: https://wordpress.org/support/topic/restrict-plug-in-use-of-rest-api/#post-9396702. Chime in there if you’d like it to happen.
Forum: Plugins
In reply to: [Disable REST API] Restrict plug-in use of REST APIMay I suggest the ability to whitelist certain endpoints? For example, Contact Form 7 has recently switched to the WP REST API and broke itself in the process (as of v4.8) for many users who have no idea why it broke and have this plugin installed.
https://wordpress.org/support/topic/contact-form-7-4-8-using-rest-api/
https://wordpress.org/support/topic/contact-form-7-version-4-8-sending-does-not-work/
https://wordpress.org/support/topic/contact-form-7-rest-api/The endpoint it uses is: wp-json/contact-form-7/v1/contact-forms/<NUM>/feedback. If we could whitelist it for public use, and the rest would remain blocked off, that’d be great.
Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 (Version 4.8) – Sending does not work4.8.1 still doesn’t work if you disabled the WP REST API like we did with https://wordpress.org/plugins/disable-json-api/. The request now uses the API, which returns a 401 if you’re not logged in.
Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 REST APIWe disable the WP API using https://wordpress.org/plugins/disable-json-api/ too, and the 4.8 update broke Contact Form 7. There needs to be a toggle to disable it and get back to the old version.
- This reply was modified 8 years, 9 months ago by archon810.