dohomi

Router.configure({
  layoutTemplate: 'layoutBackend',
  notFoundTemplate: 'page404',
  loadingTemplate: 'loading',
  i18n: {
    languages: TP.Const.AllowedLangKey,

    setLanguage: function (lang) {
      if (Meteor.isClient) {
        TP.Core.Functions.setLanguageKey(lang);

dohomi

Template.registerHelper(Schemas, Schema);

dohomi

<template name="pageTreeNav">
    <div id="pageTree" class="js-pa-sortable js-pa-container" data-parent-id="null">
        {{#each getPageNodes}}
        {{> pageTreeItem itemData=. level="2"}}
        {{/each}}
    </div>
</template>


<template name="pageTreeItem">

dohomi

Template.exerciseList.events({
    "keyup .js-exercise-text-search": function (ev, templ) {
        Session.set("ExerciseListFilter", {"name": {$regex: ev.currentTarget.value, $options: 'i'}});
    }

});


Template.exerciseList.helpers({
    exercises: function () {

dohomi

 {{#autoForm collection=Collections.Clubs id="createClubForm" type="method" meteormethod="createClub"}}

        <div class="form-group {{#if afFieldIsInvalid name='name'}}has-error{{/if}}">
            <div class="input-group">
                <span class="input-group-addon">
                    Name
                </span>
                {{>afFieldInput name="name"}}
                <span class="input-group-btn">
                    <button type="submit" class="btn btn-primary">

dohomi

${q(site).find('instanceof TYPO3.Neos:Document').property('_name') == 'blog'}

dohomi

<?php
# PackageStates.php

# This file is maintained by Flow's package management. Although you can edit it
# manually, you should rather use the command line commands for maintaining packages.
# You'll find detailed information about the typo3.flow:package:* commands in their
# respective help screens.

# This file will be regenerated automatically if it doesn't exist. Deleting this file
# should, however, never become necessary if you use the package commands.