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 ...


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 ...


4

You'd be better off just 'stashing' the image urls and using the CE Image tag from within the layout. Article {f-archive-images} {exp:stash:set_list name="images"} {stash:url}{f-archive-images-image}{/stash:url} {/exp:stash:set_list} {/f-archive-images} Layout First image: {exp:stash:get_list name="images" limit="1"} {exp:ce_img:single src="{...


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

Welp, after even more testing an hair pulling I sorted it out. I forgot to set parse_tags="yes" on the exp:stash:set... d'oh! Model {!-- SINGLE VARIBLES --} {exp:stash:set parse_tags="yes" trim="yes" } {stash:share_image_url} {exp:ce_img:pair src="{cf_featured_image:url}" width="800" height="450" crop="yes" ...


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=""} ...


3

Thank you all for the help. After a lot of digging around, once again the culprit was everyone's friend htaccess. There was a rogue rule that included /images/ which seems to occasionally interfere, removing the rule, clearing the /made folder, clearing the EE tag cache and we are back in business. Phew... Lesson learnt, if in doubt it's always blooming ....


3

If you're using Structure 3.3.8, it already includes the Structure Entries functionality (Official Documentation). Maybe give the native version a try and see if that parses the Assets tag correctly? {exp:structure:entries parent_id="{embed:my_parent_id}"} ... {/exp:structure:entries}


3

I also just just noticed that you are using {page_image}...{/page_image} as a variable pair, and also using a single variable {page_image} inside that loop (that you are passing into the CE Image src= parameter). I think that's probably a typo, right? Shouldn't the single variable be {url}?


3

Would something like this Image Editor add-on work for what you need? http://devot-ee.com/add-ons/image-editor Another solution might be add select fields to allow the client control the crop position parameters for CE Image. For instance, if you had a select dropdown field called {horizontal_crop} with the values "left, center, right" and another ...


3

Well that was simple! just added the orderby="image_order" parameter to the matrix tag pair. I had tried that originally, but it was using the already cached images. Once they were deleted out, it regenerated the right ones. :)


3

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


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 ...


2

Personally I wouldn't look to switch to a different method unless you have a particular need to. If I were given the same scenario I would go with the same method that you use and combine Matrix and CE Image to apply watermarks on an ad-hoc basis. That combination sounds like it should both work well and do everything that you need it to do. If it aint broke,...


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

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

Let me give you a different spin on this that maybe a much easier situation for you to implement as it should work regardless of the add-ons being used your using. Rather than have individual addons upload the assets to S3, keep them on the local server, but setup a CloudFront distribution, but set it up to reverse proxy from your server. Let's say the ...


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

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

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

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

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

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


1

Add parse="inward" to the gwcode categories parameters.


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