interfacelab
Forum Replies Created
-
Doesn’t support any versions of PHP less than 5.6.
You should really upgrade because 5.5 became unsupported in mid-2016.
Are you using PHP 5.4?
Ok. I looked into the site icon stuff in WP and it’s pretty gross. I won’t have time to really look for a fix for awhile, a couple of months probably.
My only suggestion is to skip it and go old school and upload the favicons to your site directly via ftp or similar.
Try turning off auto compress.
In Imgix settings, do you have:
– “Auto Format” turned on?
– “Auto Compress” turned on?I’ve never used the site icon feature of WordPress, so I’ll have to dig into how it works. In the meantime are any of the above options turned on?
site icon background changes from transparent to white via imgix
What does that mean?
The plugin doesn’t support changing storage providers. It also doesn’t support being removed because it’s a cornerstone fundamental of your architecture.
You can remove the S3 data from your attachments using this (back up your DB first though):
add_action('init', function(){ $attachments = new \WP_Query([ 'post_type' => 'attachment', 'post_status' => ['publish', 'inherit'], 'posts_per_page'=> '-1' ]); foreach($attachments->posts as $attachment) { $meta = wp_get_attachment_metadata($attachment->ID); if (isset($meta['s3'])) { unset($meta['s3']); if (isset($meta['sizes'])) { $metaSizes = $meta['sizes']; foreach($meta['sizes'] as $size => $sizeData) { if (isset($sizeData['s3'])) { unset($sizeData['s3']); $metaSizes[$size] = $sizeData; } } $meta['sizes'] = $metaSizes; } } wp_update_attachment_metadata($attachment->ID,$meta); } });Thanks,
Jon.
This 100% will upload directly to S3, but only if you are using Imgix and using the direct uploader:
Imgix is needed for cropping/resizing images.
I hate to bounce you back to them, but the problem is with their plugin. I suspect they are trying to read the image file from the server, but it probably isn’t on the server (if you have the “Delete From Server” option selected in Storage Settings).
I’ve never seen an error “parsererror 200: SyntaxError: Unexpected token in JSON at position 0”. Is this a PHP error? Where do you see this error? Can you upload a screen shot to imgur.com?
Thanks,
Jon.
Can you turn on the debugger, insure you have php logging enabled and logging to a file and then paste the output after trying to upload the big file again?
Thanks,
Jon.
I’ll definitely look into it but it wouldn’t be for several months. I’m neck deep in client work until well after Christmas. 🙁
There are two versions of WP Smush (same with EWWW too). The “free” one does local optimizations and “pro” one does cloud based stuff.
The benefit of Imgix is not only optimization but being able to add new sizes to your theme and just have it work without having to regenerate thumbnails. I have a lot of clients that do watermarking too, and with my plugin it’s easy to do and the watermark can be changed in the future – again without having to manually regenerate anything.
I just tested with EWWW, ShortPixel, Imagify and WP Smush.
WP Smush works fine.
EWWW works too, but it made all the image file sizes a bit larger than the non-optimized ones, so *shrug*.Imagify and ShortPixel do not work because those are web service based. If you are going to use an image optimization plugin, use one that isn’t web service based because you are doing a lot of extraneous uploading and downloading.
I honestly don’t know because I use Imgix on every site I build, which does the optimizations for you. Imgix is the primary reason I built the plugin in the first place.
This plugin inserts itself at the end of every upload hook/filter with a priority of 10,000. The image optimization plugins should insert themselves before that to work properly. I know some of them defer processing because they use an online service for optimization, so they likely wouldn’t work.
To be perfectly honest, I doubt I will ever worry about compatibility with these kinds of plugins because of my religious feelings about Imgix. I am accepting pull requests though 🙂
Thanks,
Jon.
- This reply was modified 8 years, 6 months ago by interfacelab.
That error pops up if you’ve not specified a key, a secret *and* the bucket.
Can you confirm that these options are set:
ilab-media-s3-bucket
ilab-media-s3-access-key
ilab-media-s3-secretThanks,
Jon.