tripp-bishop
Mentor
Joined 14 years ago
User Profile
User Widgets
Contributions
- 312ViewsSign in to react to this post2Comments
- ViewsSign in to react to this postComment
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?ViewsSign in to react to this postComments- ViewsSign in to react to this postComments
- ViewsSign in to react to this postComments
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.ViewsSign in to react to this postComments- ViewsSign in to react to this postComments
Our text keys are not node aware. They would know the difference between a root message and a comment, an Idea and a Blog, but not one Idea from another Idea.
Best bet might be using a psuedo class like:
options-menu:after{
content: 'Comment Options';
}
- ViewsSign in to react to this postComment
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, TrippViewsSign in to react to this postCommentsRe: 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, TrippViewsSign in to react to this postComments
312Views
2Comments