Download the PHP package dd/evolutioncms-snippets-ddsendfeedback without Composer

(MODX)EvolutionCMS.snippets.ddSendFeedback

A snippet for sending users' feedback messages to you. It is very useful along with ajax technology.

Supports sending messages to:

• Email
• Telegram
• Slack
• Sms.ru
• Custom HTTP request

The snippet returns a JSON string with the following fields:

Requires

• PHP >= 5.6
• (MODX)EvolutionCMS >= 1.1
• (MODX)EvolutionCMS.libraries.ddTools >= 0.62
• (MODX)EvolutionCMS.snippets.ddMakeHttpRequest >= 2.3.1

Installation

Using (MODX)EvolutionCMS.libraries.ddInstaller

Just run the following PHP code in your sources or Console:

• If ddSendFeedback is not exist on your site, ddInstaller will just install it.
• If ddSendFeedback is already exist on your site, ddInstaller will check it version and update it if needed.

Manually

1. Elements → Snippets: Create a new snippet with the following data

1. Snippet name: ddSendFeedback.
2. Description: <b>2.9</b> A snippet for sending users' feedback messages to you. It is very useful along with ajax technology..
3. Category: Core.
4. Parse DocBlock: no.
5. Snippet code (php): Insert content of the ddSendFeedback_snippet.php file from the archive.

2. Elements → Manage Files

1. Create a new folder assets/snippets/ddSendFeedback/.
2. Extract the archive to the folder (except ddSendFeedback_snippet.php).

Parameters description

General

• result_titleSuccess

  • Description: The title that will be returned if the letter sending is successful (the title field of the returned JSON).
  • Valid values: string
  • Default value: 'Message sent successfully'

• result_titleFail

  • Description: The title that will be returned if the letter sending is failed somehow (the title field of the returned JSON).
  • Valid values: string
  • Default value: 'Unexpected error =('

• result_messageSuccess

  • Description: The message that will be returned if the letter sending is successful (the message field of the returned JSON).
  • Valid values: string
  • Default value: 'We will contact you later.'
• result_messageFail
  • Description: The message that will be returned if the letter sending is failed somehow (the message field of the returned JSON).
  • Valid values: string
  • Default value: 'Something happened while sending the message.<br />Please try again later.'

Senders

• senders

  • Description: Senders and their params. You can use several senders at the same time.
  • Valid values:
    • stringJsonObject — as JSON
    • stringHjsonObject — as HJSON
    • stringQueryFormatted — as Query string
    • It can also be set as a native PHP object or array (e. g. for calls through $modx->runSnippet):
      • arrayAssociative
      • object
  • Required

• senders->{$senderName}

  • Description: A sender, when the key is the sender name and the value is the sender parameters.
    • Keys are case insensitive (the following names are equal: 'Telegram', 'telegram', 'TELEGRAM', 'tEleGRaM', etc).
  • Valid values: object
  • Required

• senders->{$senderName}->tpl

  • Description: The template of a message/letter/data.
    • All senders use this parameter as main data.
    • For text senders (like email, telegram, etc) it is just a message you want to send in relevant format (e. g. HTML, Markdown, etc).
    • For API senders (like customhttprequest) it is request data in HJSON/JSON format.
    • Use [(site_url)][~[+docId+]~] to generate the url of a document ([(site_url)] is required because of need for using the absolute links in the messages).
    • Available placeholders:
      • [+docId+] — the ID of a document that the request has been sent from
      • Any item of $_POST
      • Any item of senders->{$senderName}->tpl_placeholders
  • Valid values:
    • stringChunkName
    • string — use inline templates starting with @CODE:
    • object — if set as an object, each item will be parsed as an independent template and then the result will be converted to JSON, it can be useful if you need to send a JSON object
  • Required

• senders->{$senderName}->tpl_placeholders

  • Description: Additional data has to be passed into the senders->{$senderName}->tpl.
    • Nested objects and arrays are supported too:
      • {"someOne": "1", "someTwo": "test" } => [+someOne+], [+someTwo+].
      • {"some": {"a": "one", "b": "two"} } => [+some.a+], [+some.b+].
      • {"some": ["one", "two"] } => [+some.0+], [+some.1+].
  • Valid values: object
  • Default value: —

• senders->{$senderName}->tpl_placeholders->{$placeholderName}

  • Description: The key is a placeholder name, the value is a placeholder value.
  • Valid values: mixed
  • Required

• senders->{$senderName}->isFailDisplayedToUser

  • Description: Display a failure message to user when sending is failed, or just log it.
  • Valid values: boolean
  • Default value: true
• senders->{$senderName}->isFailRequiredParamsDisplayedToLog
  • Description: Display a failure message to the CMS log when required parameters are not set.
  • Valid values: boolean
  • Default value: true

Senders → Email

• senders->email

  • Description: The sender parameters.
    • Send method (PHP mail() or SMTP) sets up in CMS config.
  • Valid values: object
  • Default value: —

• senders->email->to

  • Description: Mailing addresses (to whom).
  • Valid values:
    • array
    • stringCommaSeparated
  • Required

• senders->email->to[i]

  • Description: An address.
  • Valid values: stringEmail
  • Required

• senders->email->subject

  • Description: Message subject.
  • Valid values: string
  • Default value: 'Feedback'

• senders->email->from

  • Description: Mailer address (from who).
  • Valid values: stringEmail
  • Default value: $modx->getConfig('emailsender')
• senders->email->fileInputNames
  • Description: Input tags names separated by commas that files are required to be taken from.
    • Used if files are sending in the request ($_FILES array).
  • Valid values:
    • array
    • stringCommaSeparated
  • Default value: —

Senders → Telegram

• senders->telegram

  • Description: The sender parameters.
  • Valid values: object
  • Default value: —

• senders->telegram->botToken

  • Description: The bot token that will send a message, like botId:HASH.
  • Valid values: string
  • Required

• senders->telegram->chatId

  • Description: ID of the chat to which the message will be sent.
  • Valid values: string
  • Required

• senders->telegram->textMarkupSyntax

  • Description: The syntax in which the message in senders->telegram->tpl is written.
  • Valid values:
    • 'markdown'
    • 'html'
    • ''
  • Default value: ''

• senders->telegram->disableWebPagePreview

  • Description: Disables link previews for links in this message.
  • Valid values: boolean
  • Default value: false
• senders->telegram->proxy
  • Description: Proxy server in format 'protocol://user:password@ip:port'.
    • E. g. 'theuser:[email protected]:5555' or 'socks5://someuser:[email protected]:5555'.
  • Valid values: string
  • Default value: —

Senders → Slack

• senders->slack

  • Description: The sender parameters.
  • Valid values: object
  • Default value: —

• senders->slack->url

  • Description: WebHook URL.
  • Valid values: stringUrl
  • Required

• senders->slack->channel

  • Description: Channel in Slack to send.
  • Valid values: string
  • Default value: Selected in Slack when you create WebHook.

• senders->slack->botName

  • Description: Bot name.
  • Valid values: string
  • Default value: 'ddSendFeedback'
• senders->slack->botIcon
  • Description: Bot icon.
  • Valid values: string
  • Default value: ':ghost:'

Senders → Sms.ru

• senders->smsRu

  • Description: The sender parameters.
  • Valid values: object
  • Default value: —

• senders->smsRu->apiId

  • Description: Secret code from sms.ru.
  • Valid values: string
  • Required

• senders->smsRu->to

  • Description: A phone.
  • Valid values: string
  • Required
• senders->smsRu->from
  • Description: Sms sender name/phone.
  • Valid values: string
  • Default value: —

Senders → CRM LiveSklad.com

• senders->crmLiveSklad

  • Description: The sender parameters.
  • Valid values: object
  • Default value: —

• senders->crmLiveSklad->login

  • Description: API login.
  • Valid values: string
  • Required

• senders->crmLiveSklad->password

  • Description: API password.
  • Valid values: string
  • Required
• senders->crmLiveSklad->shopId
  • Description: Location (shop) ID.
  • Valid values: string
  • Required

Senders → Custom HTTP request

• senders->customhttprequest

  • Description: The sender parameters.
  • Valid values: object
  • Default value: —

• senders->customhttprequest->url

  • Description: The URL to request.
  • Valid values: stringUrl
  • Required

• senders->customhttprequest->method

  • Description: Request type.
  • Valid values:
    • 'get'
    • 'post'
  • Default value: 'post'

• senders->customhttprequest->sendRawPostData

  • Description: Send raw post data. E. g. if you need JSON in request payload.
  • Valid values: boolean
  • Default value: false

• senders->customhttprequest->headers

  • Description: An array of HTTP header fields to set.
    • E. g. ['Accept: application/vnd.api+json', 'Content-Type: application/vnd.api+json'].
  • Valid values: array
  • Default value: —

• senders->customhttprequest->userAgent

  • Description: The contents of the 'User-Agent: ' header to be used in a HTTP request.
  • Valid values: string
  • Default value: —

• senders->customhttprequest->timeout

  • Description: The maximum number of seconds for execute request.
  • Valid values: integer
  • Default value: 60

• senders->customhttprequest->requestResultParams

  • Description: Parameters for response parsing.
  • Valid values: object
  • Default value: — (see below)

• senders->customhttprequest->requestResultParams->checkValue

  • Description: Value considered as success/failure.
  • Valid values: mixed
  • Default value: true

• senders->customhttprequest->requestResultParams->isCheckTypeSuccess

  • Description: Checking the success or failure?
  • Valid values:
    • true — use if the response contains data about successful status (e. g. response: {"success": true})
    • false — use if the response contains data about failure status (e. g. response: {"error": true})
  • Default value: true

• senders->customhttprequest->requestResultParams->checkPropName

  • Description: Name of the response property to check for success/failure status.
    • Use it only if the response is an object. In this case the Sender will convert the response data into an object and get the required property value to check success/failure.
    • You can also use '.' to get nested properties. Several examples:
      • error, ok, success, status — get first-level property
      • sms.status — get second-level property
  • Valid values:
    • null — means that response is not an object
    • string — property name for checking if response is object
  • Default value: null
• senders->customhttprequest->requestResultParams->errorMessagePropName
  • Description: Name of the response property that contains text of an error message.
    • Use it only if the response is an object.
    • If you want to use this property, you should define senders->customhttprequest->requestResultParams->checkPropName.
    • You can also use '.' to get nested properties. Several examples:
      • description, title, message — get first-level property
      • error.message — get second-level property
  • Valid values:
    • null — means that response is not an object
    • string — property name with error message
  • Default value: null

Examples

All examples are written using HJSON, but if you want you can use vanilla JSON instead.

Send to email

Send to Telegram

Send to Slack

Send to Sms.ru

Run the snippet through \DDTools\Snippet::runSnippet without DB and eval

Links

• Home page
• Telegram chat
• Packagist
• GitHub