What would an example syntax be for the Email button?

I cant find a list of the button objects anywhere.

Here is a makeshift example I am using, but I keep running into errors with it.

[if|13][button:mailme_visible][/if][endif|13]

a tag with this as the href: "/NewsDownloads/tabid/396/Default.aspx?Command=Core_Mail&EntryId=[entry:entryid]"

Has anybody used this button in their custom template? Still can't figure out what the proper syntax is.

Use a similar approach to the delete button:

a href="[button:delete_url]" onclick="Javascript:return confirm('[resources:DeleteConfirm.Text]');" class="document_delete-png link" title="[button:delete_text]" style="display:[button:delete_visible|block;none];"

So set the href to [button:mailme_url] and the visibility accordingly. You can opt to have a confirmation popup as well and a title as in the example above.

Peter

This works for the mail me, which we have already implemented. I guess I should have been more specific. I am looking for the mail option that allows emailing as an attachment to someone else. Below is my current configuration, when you click it, it takes you to the email page. Once filled out, and sent, it produces the following error:No valid documents to send were found

This is the resulting url, which seems valid:/NewsDownloads/tabid/396/Default.aspx?Command=Core_Mail&EntryId=13911

This is the error that needs resolved.

You're mixing up things here. You're trying to use the mailme visibility to switch the visibility of the mail button (another function). But if this is what you want you can do this you need to keep in mind you can't use the button object in the entry repeat template, only in the overall template. That is: the entry point or any conditional subtemplate of that. E.g. if you take the "minimal" template as an example it'll only work in the template.html, and not the entry.html.

Note that the MailMe visibility just tests for the user being logged in. It doesn't know anything about Mail App Permissions.

Peter

Peter,

I feel we are not on the same page in regards to the issue. I understand the mailme is not function I am looking for. I feel you are stuck on that as being part of the solution I am looking for, so lets start over.

What I am looking for, is what the syntax for what I am trying to accomplish is. I am using a modified version of the Default Template. On ViewEntry.html, I am looking to add a button that runs the email function/not the mail me function. I am looking for the syntax that adds a button, when clicked, directs you to the email document page where you fill out link/attachement, to address, body, etc. Specifically, what should [button:delete_text] be changed to in order to get me to the proper page.

Currently I have implemented what I would call a hack, which can be found above. When logged in as a superuser, I click the button, and it takes me to the right page. I fill out the info, and send, wich is when it loads up the error:No valid documents to send were found. I am assuming this is due to the hack, but could not find any information in regards to what I am trying to accomplish.

What confuses me is that in your post of 23 aug you included this snippet: [button:mailme_visible] Note the "mailme" in there. "Mailme" is the phrase used throughout DMX for the "Mail Me" function.

Now, regarding the link. The pattern that is expected is this:
?Command=Core_Mail&CollectionId=1&EntryList=ent3

- CollectionId allows the app to return to the folder previously selected.
- EntryList is used instead of EntryId, because you can potentially send more than one item at a time
- "ent3" is used to tell DMX it's an entry and it's EntryID is 3. In the current version you'll need to stick to that pattern.

Peter

This last response is more what I was looking for. Below is the final link I came up with, using advice from Peter, which works properly.



I am surprised there is no built in object to do this for us, like every other button in the template

Example:


Where it has the href set to button:lock_url. I was expecting the to be one similar, like: button:emailApp.

End result, though, is that it works, thanks largely in part to Peter continuing to work through our issues, and find a resolution