6

Try this: <li class="large-4 small-3 columns"> {right_image_1} {if description} <img class="avatar w-alt" alt="{description}" src="{url}" /> {if:else} <img class="avatar wo-alt" alt="{title}" src="{url}" /> {/if} {/right_image_1} </li>


5

Here is one approach: Put the users in a member group that has the member preference "Can edit entries authored by others" set to "No" Use Channel Images or Channel Files to manage the file uploads. These add-ons have per-entry file management, so they will create separate directories per Channel entry. This combination effectively makes it so that ...


3

If you have command line access on the server, you can setup a Symbolic Link: http://www.wallpaperama.com/forums/linking-files-with-symbolic-links-linux-unix-shell-command-tutorial-guides-t479.html Apparently you can also set up a Symbolic Link without command line access using PHP: http://perishablepress.com/use-php-to-create-symbolic-links-without-shell-...


2

Yes, it is that easy, I've done this many times. In some earlier versions of Assets I had some issues doing this on a couple of sites, but later versions smoothed out the bumps. As always, do this on a dev copy of the site first - or at the veery least, take a full DB backup first.


2

I had this same problem and after some head scratching, found that for some reason the other member groups didn't have file upload priviledges. So, check: Content -> Files -> File Upload Preferences -> Edit (select at least one location) And check that at least one upload location allows the Member Groups to upload files.


2

There's no built in way to do this. You'd need to build an add-on that triggers the manipulations, similar to how it's triggered when the images are uploaded through the control panel. An easier way to handle this might be to do the resizing on the frontend using the CE Image plugin. The manipulations get generated when they are needed, so you don't need to ...


2

Assets is the most advanced file manager for EE, so if it doesn't do it then there isn't an out of the box solution for EE.


2

The default file manager does not allow for browsing of subdirectories. You would need to use something like Assets ( http://devot-ee.com/add-ons/assets ).


2

This was a bug, and was fixed in 2.10: https://support.ellislab.com/bugs/detail/20866/javascript-error-in-cp-file-manager


2

Did you run an EE upgrade recently?? They changed how they detect mime types: https://ellislab.com/expressionengine/user-guide/about/changelog.html Look at the change log for 2.10. They use a different mime-type library now... sounds like you upgraded, but it's possible your PHP version is out of date or missing a required module... please let us know your ...


2

It turns out my database.php file had an extra blank line at the beginning. (see that extra line?) And this was corrupting output in EE. Any php file that is included (called by the main php file) needs to have the opening php tag on the first line! Otherwise bad things will happen.


2

what happens if you don't specify a folder? EE will normally give you the options for the folders you have rights to upload into


2

It depends upon what you call 'easy'. It can be done, but is quite complicated, and AFAIK none has written a utility to do this migration for you (though it probably could be created). Assets bases its file referencing on the File Upload directories used natively by EE, but actually references the files stored in a quite different way. For EE native ...


2

I've been working on upgrading an EE2 6-site MSM installation up to EE5 and in the process realised that Assets now requires a separate license for each site. So to save myself $600 I wrote a script that converts all instances of Assets to EE's native File including Assets used in Matrix columns (for various reasons I can't use EE's Matrix to Grid converter ...


2

The best way would be to use the Model service to create Channel Entries and files: https://docs.expressionengine.com/latest/development/services/model.html This will guarantee you are saving complete records, which you can't guarantee if you are just blindly inserting data in the database. This also means you are triggering EE's extensions system, so ...


1

Have you tried 'sync'ing'? I believe this updates the database with the actual content of folders (and creates any manipulations that may exist).


1

I just encountered this issue last week, and EllisLab confirmed it as a bug that can present itself under certain conditions (related to a special character in a file name causing json_encode() to fail). They fixed it in my problem install, so if you have a support plan I'd suggest you open a ticket with them. Kevin said it would be fixed in the next point ...


1

You started fine with the manual deletion; you just need to complete the process. Open your Edit form and find your entry_id. Then, go to your field groups and find the field_id of the file field. Then head to your channel_data MySQL table, find that entry_id (if your field_id is 10 and entry_id is 20, use SELECT field_id_10 FROM exp_channel_data WHERE ...


1

What version of EE are you using? Modern (2+) use an array to identify mime type allowances. In my version I'm looking at (2.9.2), it looks like this: $mimes = array( 'ai' => 'application/postscript', 'aif' => 'audio/x-aiff', 'aifc' => 'audio/x-aiff', 'aiff' => 'audio/x-...


1

This is a bug, and a solution from EllisLab can be found at https://support.ellislab.com/bugs/detail/20972


1

I had a similar issue recently when PHP was reconfigured. It turned out PHP's fileinfo extension wasn't enabled. Fixing that fixed the upload problem I was having. Might at least be something to check on in your case too.


1

I think that linking non-image files didn't start happening until 2.7.0. In the docs for the 2.7.0 update under General Changes: "All files regardless of type are now linked for viewing in the File Manager."


1

Sounds like you need to change your uploads directory permissions. The non-generation of thumbnails pretty much verifies that it is a permissions problem. First, take a general look at the EE Upgrade Instructions, in particular the section on Verify File Permissions. Check everything matches the recommendations. Then check your File Manager Permissions in ...


1

I don't think ExpressionEngine will allow such behaviour out of the box although the exp_files table 'does' include a 'uploaded_by_member_id' column so it's possible that you could leverage that through a custom file select field type to limit what the user can pick from.


1

If you have FTP access, you should just be able to overwrite the file on the server. Anywhere it's referenced on the site then, should pick up the file.


1

There is no native way to do what you want. It's either "images" or "all". If one does not already exist then creating a custom fieldtype that would only permit uploads of a particular type should be possible. Start with the existing file fieldtype and see if you can modify it to do what you need.


1

The issue was that the member had the ability to change file upload preferences on their own. They used that power to remove their own access and so the system was confused.


1

I was doing just this last week on a few thousand entries. Assets works really well at converting. First make sure Assets is synchronised with your upload paths. Assets creates a reference to all the files in exp_assets_files. EE File fieldtype stores it's data in the format {filedir_x}your-file.ext, where x is the reference to upload paths config. When ...


1

Turns out it was caused by Generate HTTP Page Headers being set as on in output and debugging. This caused a real delay in the full page load and this caused the issues file manager.Turning it off and this sorted my problems


1

I had this problem and what fixed it for me was changing the Image Resizing Protocol to GD2 (it was set to ImageMagick, which probably was not installed on this server). Image Resizing Protocol (in EE3.5) is in Settings > Content and Design. So in other words, make sure the Image Resizing Protocol is set to what is installed on your server.


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