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
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
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
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
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
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}
...
3
You can use MX GetID3 plugin for this purpose. This addon seems updated before 1 year but it would work.
3
After updating back to 2.2.1, running the following query will fix this:
UPDATE exp_assets_selections SET content_type = 'matrix' WHERE row_id > 0 AND (content_type = '' OR content_type IS NULL)
We're about to release Assets 2.2.2 that addresses this, but, while it's still not out, the query above should take care of your problem permanently. This only ...
3
This is a pretty easy to resolve. Simply open up:
/expressionengine/third_party/wygwam/mcp.wygwam.php
and change line 139 from:
$all_sources = ee()->assets_lib->get_all_sources();
to
$all_sources = $this->EE->assets_lib->get_all_sources();
Looks like this is the only reference to the ee() global in the codebase. Because this code block ...
3
Ugh, wasn't logged in properly....
They sent me this on email support:
If you could just replace line 814 in Assets_lib.php file with
if (!(count($full_folder_list) == 1 && reset($full_folder_list) == ":any:"))
you should be fine :)
3
Fixed:
I found ini_set('memory_limit', '64M'); in /system/expressionengine/third_party/assets/sources/s3/source.s3.php and changed it to 1024M
3
This is due to a change in how EE validates Channel Form fields (not sure when this was implemented). When you upload a file via a file field, that field name isn't actually populated in the $_POST array, so EE doesn't know it's been submitted, and hence won't call the fieldtype which owns that field.
It works around this issue for native File fields inside ...
3
Suggest you contact the hosting provider recommended by EllisLab: https://ellislab.com/community/hosting
Also read this whitepaper supplied by them: https://www.nexcess.net/expressionengine/hosting-optimization
You could Google "expressionengine hosting" and contact numerous of the hosting providers to see what they would recommend and supply, then either ...
2
I know that channel files has an import function. Same with channel images if you needed that.
This might not be much of a useful answer, but it might be worth a chat with DevDemon. I haven't used the import feature yet.
As far as I am aware, you'll need create a list of entry ids, urls etc. Then you can import. You might need Export It or another ...
2
We were seeing this same issue running Assets in our EE 2.5.2 environment. After we updated to Assets 2.2.2 it began working as expected.
2
If you are on EE 2.6, 2.6.1, or 2.6.2 and using Assets 2.1.1, you should update to the latest versions of both. If you're stubborn, Rob's fix above will work for you.
If you even more stubborn and on EE 2.5.5 or below, then stop being stubborn and update. Said with kindness in my heart.
2
Not sure about setting it to enforce prior to upload, but it can be enforced after the fact in-template using CE Image's bulk tag pair wrapped around your Wygwam custom field.
2
I don't think it's possible to change the order of items in Assets as this is mainly intended as a global asset management addon and not particularly linked to display in front-end templates. You will probably be better off doing this in a Channel Entry where you pull in your assets and then set things like an order on the output.
Matrix (also by Pixel &...
2
It turns out that you must have at least one upload location (for that site, if MSM is enabled) present in order to set the upload location in Wygwam.
For instance, I just performed a migration of Wygwam (2.7.1) data from using the native EE uploads to using Assets (2.2.2). Initially, I moved all of the images from the native upload location to an assets ...
2
try setting the is_draft column in exp_matrix_data table to NOT NULL with the default of 0. This will be fixed in the next Matrix version.
2
It seems that signed URLs are not an option in Assets at present but the good news is that IntoEEtive have confirmed that Protected Links should work perfectly well with Assets files so it should be possible to provide secure file links on the front-end with the help of this addon.
Only top voted, non community-wiki answers of a minimum length are eligible
