Uploading files through simple edit

I need our staff to be able to update uploaded files through the simple edit interface. Is there a keyword I can put on the details page to allow them to upload new versions? We're using the asset builder to create new files and it's working fine.

There is a bug that stops the file upload interface from appearing if you are using layouts for file assets. It is being fixed as we speak.


There is no workaround for this bug other than removing the layout for the FILE details screen.

Thanks. I've remove the details screen and it seems to work. Unforunately this means no metadata and that they don't need to lock images/files before uploading but I can live with that.

OK,


I've come back to looking into the Simple Editor. Question 1 (Im guessing this will be a 10+ part series)



1 Does the Layout Manager need to be set to Live to get the Simple Edit interface working?



Thanks!

My one is

Layout Manager itself does not need to be live, but the Layouts do. They also need to be Readable by the users (Public Read is fine too).

OK, that's a start :slight_smile:


2. Can anyone provide me with what they have in their Layout to control the editing of a standard page. And how is that applied in the Layout Manager? What are the crucial layout types that I need to add to enable the Simple Edit interface.

it's ok. got it going now - thank god

Layouts I recommend for Standard Page:

  1. Details
  2. Contents
  3. Workflow (if applied)
  4. Metadata (if applied)



    Those are the ones I use.

It would be great to be able to edit content on an Asset Listing page, but I assume that the nature of this type of asset would mean that you can only edit a limited section of the page?

How about putting an edit link next to each item? That's what we're using.

Yeah, I do that too. If you want to get very clever, switch the container type of the Format bodycopy to "nest content", then use a multi-div standard page to hide the "edit" link from people who don't have edit permission (by setting permission on that div).

Thanks for the tips. Avi - sounds a little bit too clever for me, but I'll have a go and see if I can implement it…

How would add a edit link for differnt pages? I am trying to think, what would work universally… I tried ./_edit and /_edit for the link, but both edit the root of the site, not the current page. What are you guys using for the link?

[quote]How would add a edit link for differnt pages?  I am trying to think, what would work universally… I tried ./_edit and /_edit for the link, but both edit the root of the site, not the current page.  What are you guys using for the link?
[right][post=“11615”]<{POST_SNAPBACK}>[/post][/right][/quote]



Where are you trying to add this link? You need to make sure you append /_edit to the end of the URL of the asset you wish to edit.



For example, to add a global Edit button in the design, you could use this code:



[html]<a href="<mysource_print id_name=“global” var=“asset_link” full_url=“true” />/_edit">Edit this page</a>[/html]



Or, if you are listing assets in an asset listing, you could use:



[html]<a href="%asset_url%/_edit">%asset_name%</a>[/html]

Thanks, but what if I wanted to just add that to a page with the WYSIWIG editor? I want it to only show up for certain users, so that is why I need it to be in it's own DIV, and be able to set permissions.


Actually, what I would love to do is, when the admin is logged in, there is a DIV that appears above all other content on the site, and asks if you want to edit this page, and give the info of who the person logged in is. How can I add a DIV above my main edit area, that can contain a "edit" link that will work globally? Yes, I know about Nesting content, but I am having a hard time understanding how to nest a DIV, and how I can edit the permissions of it. Will it show up as an item in the asset tree?

I would suggest using a show_if design area for this. Set the HTML to only appear if the user is logged in and has write (or higher) permission to the current asset.

I got it working using your suggestion. Thanks so much!