9
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
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
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
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
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
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
All you have to do is move the files to S3 from within Assets’ File Manager itself. If you do that, all of your existing data will automatically start pointing to the new location on S3.
2
I hit this recently. You need to increase the max_execution_time in php.ini. i went with 300 and this fixed it right up for me. Also make sure you have sufficient memory. I specify 128Mb+
2
Have you tried {url} or {server_path}? I suspect that {subfolder} (confusingly) refers subfolders of existing EE File Upload paths (i.e. subfolders that Assets recognizes, but EE does not).
2
The CE Image 'Bulk' tag may help you. It'll output the images placed within WYSIWYG editors, like Wygwam.
2
Go to Add-Ons > Modules > Wygwam > [your config name], and set the “Upload Directory” setting to blank, and Wygwam will start showing all of your upload directories.
2
Ninjaroll,
yeah, until we get Assets 2.2.2 out the door, which should happen any day now, there's an issue with fresh installs of Assets 2.2. If you run the following query, your issue should be fixed.
ALTER TABLE exp_assets_selections ADD COLUMN content_type VARCHAR(255) NULL AFTER element_id
2
If you're getting HTTP 403, rather than the cross-domain error, then you might be hitting the incompatible session bug. Assets uses Ajax to do a lot of things and that is processed via Frontend by EE, so if your Control Panel Session and User Session types are not compatible, the Ajax requests will think you're not logged in.
Can you go in Admin -> Security ...
2
You have to wrap the element_name in quotes:
{if "{element_name}" == "Address Content"}
2
In Assets 2.2.2 you can't create folders that begin with an underscore. Until we release 2.2.3 it is possible to rename a folder to a name that begins with an underscore, but this is a bad idea, as you'll be unable to index these files.
As for the reason why:
1) Since Assets now supports multiple source types, to eliminate the need for querying S3 and other ...
2
See this post for info Matrix (2.5.8) update database error
Sounds like it is the same or similar problem. I had this once and the info there was enough to go into the database and sort out the issue.
2
The quick way would be to use an SQL query (something like http://pastie.org/private/x6uue9y6ieqvlqf6ai59q), but that would not get you the URL, though, as that depends on several other settings. If you're confident that the settings for the upload folder (or Assets external source) for that will never change, this will probably not be an issue for you.
The ...
2
I could be wrong, but I think Safecracker File automatically appends a number to the end of any duplicate filenames to avoid collisions. Have you verified that your perceived issue is actually an issue?
2
If you're getting HTTP 403, rather than the cross-domain error that most people get, then you might be hitting the incompatible session bug. Assets uses Ajax to do a lot of things and that is processed via Frontend by EE, so if your Control Panel Session and User Session types are not compatible, the Ajax requests will think you're not logged in.
You cna ...
2
When updating files connected to a CloudFront distribution you can speed up the required waiting period by invalidating the modified files. In many cases this reduces the waiting period to update CloudFront edge locations from days to under an hour.
Details here:
http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html
Only top voted, non community-wiki answers of a minimum length are eligible