ContributionsMost RecentMost LikesSolutionsRe: Is it possible to execute an endpoint from another user? if you're using the /messages/id/${message_id}/edit REST call I believe that you can specify the author as part of the querystring. See this link: https://developer.khoros.com/khoroscommunitydevdocs/reference/rest#rest---http-putpostdelete-api-v2 for details and good luck. Re: Overriding ForumPage MessageListThanks Paolo. I suspected that that was the case.Overriding ForumPage MessageList HI all, I'm trying to figure out if there's a way to modify the way forum topics are rendered in the MessageList on the ForumPage quilt. MessageList generate a table but I would like to move away from that while still maintaining the ability to do batch processing and the built-in paging functionality. Is this possible or would have to write a custom component/paging and lose out on the batch processing feature? Re: Changing Menubar textThanks Kaela. The pseudo class did the trick along with some other CSS to hide the actual label text. Re: Changing Menubar textas a corrollary to this: Is there a way in textdefs to pin-point a specify board when defining a text definition? something along the lines of: menubar.button.board_options@coreNode.id:myideas = My shiny options or something along those lines. I know that I can hone in a specific page type using something like: menubar.button.board_options@page:IdeaExchangePage = Ideas options but if I have multiple idea boards this doesn't really work.Re: REST API v2 URL?Check out http://community.lithium.com/t5/Community-API-v2/Getting-started/ta-p/113193#browser. It talks about submitting LiQL queries directly. You'll need to get a few bits of info from Lithium to get going with it, but perhaps this will work for you. Personally, I'd just include the LiQL inside a custom endpoint or component and go from there.Changing Menubar text Hi everyone, So I have a standard menu-bar component that I'm using on an IdeaPage quilt. I have one menu-bar that controls options for the idea itself and then one for each comment on the idea. The problem is that both types of menu-bar dropdown utilize the same text key, menubar.button.thread_options. This is problematic because I'd like the Idea options to use the default, "Idea options" but for each comment, I'd like the dropdown text to read "Comment options". How can I get the dropdown to use different text depending on the context? Does the "menu-bar" component take any parameters that would help with this? Cheers, Tripp SolvedRe: Uploading image to album from within an End PointThanks Doug. I'll do just that.Re: Uploading image to album from within an End Point So I've done a little more testing on this and noticed something: I added a new field to the form: <input type="text" name="image.title" value="The light is green" /> and I commented out the "file" input field. Submitting the new form to the endpoint I found that the new field is also not found. So I removed the form's enctype attribute and resubmitted the form and the image.title parameter is now found and shows the correct data. So it appears that the multipart/form-data enctype is confusing the endpoint (or at least http.request.parameters). Any thoughts on this? Cheers, Tripp Re: Uploading image to album from within an End Point VarunGrazitti Thanks! I'm running into an interesting issue: Here's the content of my test endpoint: <#assign status = "error" /> <#assign message = "no errors" /> <#assign upload_payload = http.request.parameters.name.get("image.content", "") /> <#compress> <#attempt> <#assign response = rest("/users/id/${user.id}/media/albums/default/public/images/upload?image.content=${upload_payload}") /> <#assign status = "success" /> <#recover> <#assign message = .error /> </#attempt> </#compress> and this is the test form that is submitting to the EP: <form method="post" action="/my-path/upload-test" enctype="multipart/form-data"> <input type="file" name="image.content"><br /> <input type="submit" value="Upload" /><br /> </form> So super simple. What I'm seeing is that the line: <#assign upload_payload = http.request.parameters.name.get("image.content", "") /> is setting the variable "upload_payload" to an empty string, probably because we failed to find a request param called "image.content". Is there another way I should be getting at the image.content variable that's being uploaded by the form? Thanks for your help! Cheers, Tripp