You are here

Home » API reference » Lockr 8.2

lockr.ui_text.yml in Lockr 8.2

Same filename and directory in other branches
  1. 8.4 config/install/lockr.ui_text.yml
  2. 8.3 config/install/lockr.ui_text.yml
  3. 4.x config/install/lockr.ui_text.yml
config/install/lockr.ui_text.yml
2 string references to 'lockr.ui_text'
LockrAdminController::getStatus in src/Controller/LockrAdminController.php
LockrAdminController::overview in src/Controller/LockrAdminController.php

File

config/install/lockr.ui_text.yml
View source 
  1. admin_page:

  2.   header:

  3.     not_registered: |

  4.       Welcome to Lockr! You're just a few steps away from storing your

  5.       keys safe and secure. To make things simple we've laid out a few

  6.       key elements (pun intended) that the system requires in order to

  7.       run. Fill out the forms below and once all rows on the table are

  8.       green, you're good to go! It's that simple! If you'd like

  9.       assistance in getting up and running be sure to

  10.       <a href="mailto:support@lockr.io">email us</a> or connect with us

  11.       on <a href="http://slack.lockr.io">Slack</a>.

  12.     registered: |

  13.       All systems are a go! Your site is registered, your certificate

  14.       is valid and everything seems good on our end. The table below

  15.       will give you the status of all elements. Should anything look

  16.       out of the ordinary just let us know on the Slack channel and

  17.       we'd be happy to help. Happy Keying!

  18.   status:

  19.     cert:

  20.       valid: |

  21.         You're a certified Lockr user! We've found your certificate and

  22.         it validates with our system.

  23.       not_valid: |

  24.         Oops! Looks like we need to know who you are before we give you

  25.         the keys to the castle. Your certificate is not valid, please

  26.         register for one. If you've already gotten a certificate, we are

  27.         unable to find it. Please check the advanced settings to ensure

  28.         your path is correct (or if you're on a hosting partner contact

  29.         their support).

  30.     path:

  31.       exists: |

  32.         We've found your private directory and are stashing the

  33.         certificates there for now. We HIGHLY recommend moving the

  34.         certificates to a directory OUTSIDE the webroot that is not

  35.         publicly available.

  36.       invalid: |

  37.         We cannot find your private directory to temporarily store the

  38.         certificates that are generated. Please ensure you have a private

  39.         directory and reload the page.

  40.       unknown: |

  41.         We cannot find your private directory to temporarily store the

  42.         certificates that are generated. Please ensure you have a private

  43.         directory and reload the page.

  44.     registered: |

  45.       You're one of the family. We've got your site registered and

  46.       you're all good to go!

  47.     not_registered: |

  48.       Who are you again? We don't have your site registered with Lockr.

  49.       Please use the form below to register your site.

  50.     cc:

  51.       has: |

  52.         We've got your credit card safely on file and you'll be recieving

  53.         regular invoices for your key usage.

  54.       missing:

  55.         required: |

  56.           Uh oh! Without a credit card we cannot issue a production

  57.           certificate. Please add one before migrating to production.

  58.         not_required: |

  59.           You're all set, no credit card needed for your account.

  60.         partner: |

  61.           Since you're on a partnering host, a credit card is not necessary

  62.           to move to production. However, please make sure you get a card on

  63.           file ASAP. We will contact you if there is no card on file within

  64.           30 days of moving to production use.

  65.