Hot answers tagged

11

Turns out my problem was the {exp:low_variables:pair} tag was nested in a {exp:channel:entries} tag. To fix this you have to use the var_prefix="" parameter. {exp:low_variables:pair var="lv_my_image" var_prefix="assets"} {assets:url} {/exp:low_variables:pair} With this syntax you can access all of the Assets' tags. {exp:low_variables:pair var="...


8

The solution was to recurse 777 to the /system/expressionengine/cache/ directory as there are thumb directories that Assets creates to hold thumbnails, etc. Thank you Lisa Wess (from Pixel & Tonic) for the solution!


8

The problem is that many developers don't know how to write compliant SQL statements - they're software developers who find themselves also filling the role of database developers. This problem crops up in many addons and was recently fixed in EE core code. For Assets v2.6 Change line 615 of ft.assets.php FROM: $sql = "SELECT DISTINCT a.source_type, a....


5

Backup your database first, of course, but theoretically this should be easy-peasy: Just add your S3 sources in the settings and then, in the Assets File Manager just drag all your files and folders from your EE sources to S3 sources and that's that - no changes in entries should be required at all.


5

If you have an Assets field called “article_images”, you can create a simple HTML upload input like so: <input type="file" name="article_images"> <input type="hidden" name="article_images_filedir" value="1"> The first input is the actual File input, and the second tells Assets which upload directory to place it in. In time, Assets will also ...


5

If you look in system/expressionengine/config/mimes.php, is 'flv' in that list? If not, try adding: 'flv' => 'video/x-flv',


5

Issue appears to be with User Session Type in Security and Settings. Ensuring that: Control Panel Session Type = Cookies and Session ID User Session Type = Cookies only seems to fix the issue for me. Flipping the user session type to Cookies and Session ID made the error recur on my setup. I seemed to be running into issues with sessions on other ...


5

Tim, currently this is not possible, but we do have some interesting ideas that would allow you to accomplish this in the next Assets release, which is currently in active development. I don't have an ETA for you, but we are working on it


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

EE simply removes any tags corresponding to custom fields that have no data. So by the time EE is ready to parse the outer {if} conditional, it will look like this: {if > 0} Try wrapping the field tag in quotes: {if '{tech_documents:total_rows search:doc_thumb="IS_EMPTY"}' > 0}


5

Okay, this definitely is an Assets issue, but here's a temporary fix. Open up ft.assets.php and look up the grid_replace_tag method, around line 1771. In there, you can see this line of code: $field_name = ee()->db->select('field_name')->from('channel_fields')->where(array('field_id' => $this->field_id))->get()->row('field_name'); ...


4

I've had a similar issue, which in the end had to do with me not being consistent with the usage of www. Is the behaviour the same when you use www or not? You could also add $config['assets_site_url'] = '/index.php'; To the config file of EE, maybe that helps?


4

Assets does work with the built-in image manipulations when using local sources. See Asset Image Manipulations ie: {my_assets_field:url:my_manipulation}


4

Doh! The answer is to use the documented var_prefix parameter so I can then reference the entry's {title} field as normal :$ That Brandon fella has thought of (nearly) everything :)


4

To make sure extra processing is done before the var is put in the template, use the tag syntax rather than the variable syntax: {exp:low_variables:single var="my_wygwam_var"}


3

Your JS forms look like they're attempting a cross-domain communication: HTMLHttpRequest cannot load http://condley-intranet.dev/. Origin http://condley-banking.dev is not allowed by Access-Control-Allow-Origin. Are you able to locate where you're crossing domains and make them consistent? I'd start with your General Config and/or /system/...


3

Well, if you don't need all of that functionality in a single add-on, you can obfuscate your links (and track the downloads, etc) using Link Vault, which pretty much works with any file field.


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

The Garnish UI library used by Assets tests for a single left click using the mousedown and mouseup events. Unfortunately IE 8 returns the value of 1 when the left mouse button is clicked, and the garnish library tests for 0, which is what the W3C says it should be. Please see http://www.quirksmode.org/js/events_properties.html#button I've had to fix this ...


3

See here: https://stackoverflow.com/a/6135485/462702 You need to increase PHP's maximum upload size. This is nothing to do with Assets (otherwise it would be broken in your development environment too). You need to change TWO settings (PHP will use the lowest). You can either change them in php.ini (preferable, if you have access to it), or your .htaccess (...


3

This was solved by adding $config['assets_site_url'] = 'http://site1.com/index.php'; for real - on the first try something had went wrong for Adrian silently, apparently. Using the CP to add this option worked as expected.


3

Yes you can. I just tested with this code: {exp:channel:entries search:pt_assets="not IS_EMPTY"} <h1>{title}</h1> {/exp:channel:entries} <hr /> {exp:channel:entries} <h1>{title}</h1> {/exp:channel:entries} and definitely got only entries back that had Assets in the first set of entries; and all entries in the second. I hope ...


3

I have solved this issue. The Assets error message did not seem very helpful, it was inconsistent with the issue. The Assets response implied the Amazon credentials were wrong, but they were not. So therefore I needed to debug tha actual Amazon response. So in the function listBuckets() in system/third_party/assets/sourses/s3/lib/S3.php I could see there ...


3

This was a bug in Assets and will be fixed in the next release. In the meantime, the patch is: in mcp.assets.php in the save_source() method, line 1000 is: $data = array( 'name' => $name, 'settings' => Assets_helper::get_json((object) $save_data) ); I changed it to: $data = array( 'name' => $name, 'settings' => Assets_helper:...


3

I just came across this issue too and it turns out while the EE filemanager doesn't mind a missing trailing slash on the server path, Assets does. Make sure your upload directory server path has a trailing slash. Resolved the issue for me.


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

Thanks to the great people at PixelandTonic I have this resolved. I was having session issues with another plugin earlier and the solution to this was to change the session preferences in the control panel from "Sessions IDs only" to "Cookies only". As usual, fixing one thing will break three. The response from P&T: In your security and session ...


3

Generally when this happens it’s because either your system is off, or your .htaccess file intercepting Assets’ Ajax requests. If it’s the latter, you can try adding this to system/expressionengine/config/config.php: $config['assets_site_url'] = "/index.php"; Assuming you don’t have a .htaccess redirect that forces “index.php” out of the URL, that should ...


3

All results of queries created by the exp:channel:entries module are parsed by the function parse_images on $this->EE->typography. When you use the exp:query module, you need to do this by your own; but, luckily, Rob Sanchez coded an addon for this. {exp:query sql="SELECT field_id_1 AS file FROM exp_channel_data" parse="inward"} {exp:parse_file_paths} ...


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