5

Assets does none of your four bullet points - these are all best done via CE Image as you're doing now (and it does all with aplomb). Why do you want to replace it? It's bar-none the best EE add-on for image manipulation (in the same way that Assets is the best file manager for EE). Re: S3 - Assets can store your files in an S3 bucket, but if you're going ...


5

You have an extraneous single quote ' in each of your opening tag pairs. {stash:ee_img_original_width'}{width_orig}{/stash:ee_img_original_width} Should be: {stash:ee_img_original_width}{width_orig}{/stash:ee_img_original_width}


5

PHP is letting you know that the maximum amount of memory that it is allowed to use has been exhausted. You need to either do less memory intensive things (work with smaller images, etc), or increase the maximum amount of memory PHP is allowed to use on your server. When working with really large images, or even doing processor intensive filters on ...


5

There are a few different ways to go about this, but the most succinct is probably to use the url_only= parameter: {exp:ce_img:single src="{your_custom_field}" url_only="yes" width="200"} You could also customize the output using the output= parameter: {exp:ce_img:single src="{your_custom_field}" output="{made}" width="200"} Or use the made variable in a ...


3

I haven't used CE Image, but looking at the documentation it seems you need a parameter "allow_scale_larger" http://www.causingeffect.com/software/expressionengine/ce-image/user-guide/parameters#allow_scale_larger And here's how you can achieve the cropping effect with CSS: http://jsfiddle.net/s552453s/ Unfortunately you are limited to cropping from the top ...


3

Yes, take a look at the text= parameter. :)


3

Use :pair tag {exp:ce_img:pair src="{your_custom_field}"} <img src="{made}" alt="" width="{width}" height="{height}" /> {/exp:ce_img:pair}


3

You didn't say which version of EECMS you're using. Some versions have parsing issues on conditionals with single quotation marks. Or, maybe, your version of Matrix have one of this issues. So, first of all, try to replace them. {if "{placement}" == "sidebar"} {exp:mx_jumper:put name="standard_image_width"}226{/exp:mx_jumper:put} {exp:mx_jumper:put ...


3

Okay, first, turn off early parsing for the myassetsimage variable. Then try and use Asset's {url} variable (see docs) in CI Img's src-parameter instead of the Low Variables name. That means that your code would look like this: {exp:low_variables:pair var="myassetsimage"} {exp:ce_img:pair src="{url}" width="640" height="400" class="img-polaroid" alt=""} ...


2

Looks like you're just missing conditionals based on the image {count}. This should get you in the right direction. I didn't add in your CE Image tags. {gallery} {if element_name=="galleryname"} {images} {if count == 1} <a class="fancybox-buttons" data-fancybox-group="button" href="{image}" title="pic{count}"> <...


2

You can try to play with parameter hide_relative_path and cache_dir. Based on what u use for upload, you can make this like: {news_image} {exp:ce_img:single src="{path}{file_name}" cache_dir="/cache/{location}/" hide_relative_path="yes"} {/news_image}


2

You need to use pair tag for this: {gallery_items var_prefix="file"} {exp:ce_img:pair src="{file:url}" max_width="1080" itemprop="image"} <img data-original="{made_url}" class="lazyload" alt="{file:alt_text}" width="{width}" height="{height}" /> {/exp:ce_img:pair} {/gallery_items}


2

Yes, there's an example on the CE Image docs (common solutions, option 2 - watermark) - essentially you need a blank image file that you can stretch as a watermark behind the resized graphic. Something like this (derived from the example on that page): {exp:ce_img:pair src="{logo}" parse="inward" max="150" crop="yes"} {exp:ce_img:single src="/images/...


2

Just use the width parameter. {exp:ce_img:single src="//mysite.s3.amazonaws.com/WebStatic/Images/Static/109/slide-1.jpg" width="1280"} See all the available parameters for CE Image.


2

CE Image can output just a URL to a manipulated image. Meaning that it could compress the image on the fly (if the image hasn't already been compressed on a previous page load), and can still output the image's URL where needed. CE Image has a quality= setting for jpg images, and uses filters to optimize png images automatically when possible. Additionally, ...


2

I'm the author of CE Image and looked into troubleshooting this with Jon. We figured out that he had the correct config settings, but that index.php config settings were moved too far down in the index.php file. Moving the files up above the require_once of the EE Bootstrap file solved the problem.


2

Looking at your CE_Img tags you haven't told it what size to make your image and you have a weird mix of PHP and EE tags going on. This is most likely the problem. You also don't need to be echoing out the width and height using PHP. CE_Img will create variables for both of these values. Just tell it what size you want your image using width, height, ...


2

CE Image 3.0.1 has been released and should take care of those pesky deprecation notices.


2

Ce img is not a fieldtype where you can expect any fields. It is image cropping and scaling plugin. AWS is a different plugin which gives you ability to upload/fetch images to/from bucket. Implementation is pretty simple. Suppose you have a file field (image) in entry. At frontend template you will write something like this: <img src="{image_field}" /&...


1

You also need to reset all your file upload paths and urls. this setting also comes in handy. $config['ce_image_cache_dir'] = '/images/made/'; http://www.causingeffect.com/software/expressionengine/ce-image/user-guide/configuration Also, as Blatant says, running the sync on the file upload prefs has been known to make everything better. what does this ...


1

A good way to do this is to cache the output of the tag. You can use built-in EE tag caching or something like CE cache, either with fragment caching or full page static. This way you're getting the resized URL and CE Image doesn't keep hitting S3. We've had extremely high traffic sites where we actually create a local redis key/value store to keep track ...


1

I know this issue has been addressed multiple times in the support forums (and possibly already on EE Stack Exchange), but hopefully answering here too will be helpful to others down the road: The long URLs are the automatic naming convention that CE image uses to prevent naming conflicts, and to mitigate the possibility of overwriting images. However, you ...


1

It's always the way - you solve you're own question after posting but Ive left it up in case anyone else might struggle with this for some reason. I got it to work with the following code, a mixture of 'total_files' and limiting entry numbers in the assets/files variable. It doesn't seem tidy, but it does work. (NB Im not using Content Elements built in ...


1

Think you're missing some key CE Image config variables - ce_image_current_domain and ce_image_document_root. I've got this setup using static.domain as the URL. Here's my config settings... Set some variables... $config['static_url'] = "http://static.${_SERVER['HTTP_HOST']}"; $config['static_path'] = "/...path-to.../static-ar/www/"; Set the upload ...


1

Step 1: Make sure you are passing parameters to CE Image If no parameters are passed into CE Image, it will simply return the original image. foamcow is right. You would want to make sure you are passing the desired width and height into CE Image, not simply outputting them in the HTML. Assuming your PHP Parsing Stage is set to "Input", this should work: {...


1

Since the source that is being passed into CE Image is not an actual image on the file system, you'll want CE Image to treat it as a remote image. You can accomplish that by using the parameter force_remote="y". Here's an example: {exp:ce_img:singe src="http://example.com/myimg.php?id=165" width="100" force_remote="y"}


1

CE Image 2.1.3 was released in June of 2011. There have been numerous updates and releases since that time. Upgrading to the latest version will allow the in-depth debug information to show.


1

There is no native way, and I have not seen anything in the 3rd party market. I would make a good FR - I can see just being able to set the compression level on each image manipulation.


1

I figure it would be possible to do this, but you probably need to write quite a large extension to channel images to make it possible. What's your skill level?


1

I am using following add-ons with EE2.8.1 from your list. 1. Assets 2. Cartthrob 3. Cartthrob Order Manager 4. Channel Images 5. Wygwam 6. Playa 7. Matrix 8. Profile:Edit


Only top voted, non community-wiki answers of a minimum length are eligible