funkhaus / funkhaus-auto-seo Goto Github PK

Would be sweet if we could use auto seo to summarize a video too…

https://notegpt.io/blog/video-summarization-for-vimeo#:~:text=Vimeo%20Video%20Summary%20is%20your,this%20powerful%20video%20summarization%20tool.

Some clients don't want the image sizing, they only want to focus point and color functions. So perhaps we add some options to disable features.

Would be great if this used a TinyJPG still advanced compression package. We seem to get clients uploading 14mb JPG's a lot.

Currently this is really hard for us to sell access to. We need a way to generate an API key unique to the customer, not use the Azure API key's funkhaus has.

Getting this error again whenever uploading images to wordpress:

When uploading images from here: https://www.dropbox.com/scl/fo/h4wwgzgbi72hfhrh64g78/h?rlkey=0nnm34a4qtjbi2f4tnotw7px2&dl=0

The plugin fails to generate image meta data and shows the below error:

There is a function to regenerate the SEO data and color detect for all images. It's a button on the settings page. It doesn't work currently.

Would be great to have this work alongside the color detect.

https://github.com/kornrunner/php-blurhash

The hash should be added as a meta field to the image. We’d use JS on the frontend to reconstruct it.

A PNG with transparency currently gets a primary color saved to it. Probably better to save that as RGBA hex like #RRGGBBAA and the AA would be 00.

So, blue with transparency would be #0080FF00. Note the last 00 means it's fully transparent.

This GIF throws and error:

The error:

We don't use the composer class autoload feature, and so need to include adapter files manually.

Recent sites are having the following error when uploading images:

This happens regardless of image size.
Images are eventually being uploaded, but without meta.
Can be seen currently at resolve-api.flywheelsites.com

When the plugin is installed all image uploads fail. The following is from the PHP error logs. Deactivating the plugin fixes image uploads.

[12-Nov-2022 23:51:49] WARNING: child 270 said into stderr: "NOTICE: PHP message: PHP Fatal error:  Uncaught InvalidArgumentException: Image resource expected. Got: object in /www/wp-content/plugins/funkhaus-auto-seo/includes/utilities.php:29"
76.94.53.223 -  12/Nov/2022:23:51:49 +0000 "POST reset-content-api.flywheelsites.com/wp-admin/async-upload.php" 500 /www/.wordpress/wp-admin/async-upload.php 41671840 3145264 71.133 6144 42.17%
[12-Nov-2022 23:51:49] WARNING: child 270 said into stderr: "Stack trace:"
[12-Nov-2022 23:51:49] WARNING: child 270 said into stderr: "#0 /www/wp-content/plugins/funkhaus-auto-seo/includes/convert-image.php(22): fh_seo_image_has_transparency(Object(GdImage))"
[12-Nov-2022 23:51:49] WARNING: child 270 said into stderr: "#1 /www/wp-content/plugins/funkhaus-auto-seo/funkhaus-auto-seo.php(54): fh_seo_convert_to_jpg('/www/wp-content...', 'https://reset-c/...', 'image/png')"
[12-Nov-2022 23:51:49] WARNING: child 270 said into stderr: "#2 /wordpress/wp-includes/class-wp-hook.php(308): fh_seo_convert(Array, 'upload')"
[12-Nov-2022 23:51:49] WARNING: child 270 said into stderr: "#3 /wordpress/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array)"
[12-Nov-2022 23:51:49] WARNING: child 270 said into stderr: "#4 /wordpress/wp-admin/includes/file.php(1043): apply_filters('wp_handle_uploa...', Array, 'upload')"
[12-Nov-2022 23:51:49] WARNING: child 270 said into stderr: "#5 /wordpress/wp-admin/includes/file.php(1075): _wp_handle_upload(Array, Array, '2022-11-12 23:5...', 'wp_handle_uploa...')"
[12-Nov-2022 23:51:49] WARNING: child 270 said into stderr: "#6 /wordpress/wp-admin/includes/media.php(303): wp_handle_upload(Array, Array, '2022-11-12 23:5...')"
[12-Nov-2022 23:51:49] WARNING: child 270 said into stderr: "#7 /wordpress/wp-admin/includes/ajax-actions.php(2598): media_..."

When uploading images, I get the following warning if debug turned on

https://learn.microsoft.com/en-us/azure/ai-services/computer-vision/whats-new#computer-vision-32-preview-deprecation

On 13 September 2026, the Computer Vision 3.1 API will be retired. Before that date, you’ll need to migrate your Azure Computer Vision workloads to Computer Vision 3.2 API which provides:

Improved image captioning, image tagging and object detection
164 language support for OCR including handwritten support for 9 Languages: English, Simplified Chinese, French, German, Italian, Japanese, Korean, Portuguese, and Spanish
Up-to-date documentation and better customer support
After 13 September 2026, you won’t be able to make any API calls to Computer Vision v3.1.

Required action

To avoid service disruptions, migrate your workloads to Computer Vision v3.2 API by 13 September 2026. For guidance on how to migrate your workloads you can refer to our documentation.

The focal point of an image seems to be wrong, often off screen.