Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-seo-pack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the betterdocs domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the check-email domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rank-math domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

WordPress database error: [Disk full (/tmp/#sql_1_1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_wfblocks7`

WordPress database error: [Disk full (/tmp/#sql_1_1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_wfblocks7`

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the insert-headers-and-footers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

WordPress database error: [Disk full (/tmp/#sql_1_1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_options`

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the google-analytics-for-wordpress domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

WordPress database error: [Disk full (/tmp/#sql_1_1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_wfblocks7`

WordPress database error: [Disk full (/tmp/#sql_1_1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_wfblocks7`

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the listable domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpserveur-hide-login domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the translatepress-multilingual domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the listable domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6121

WordPress database error: [Disk full (/tmp/#sql_1_1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_wflivetraffichuman`

WordPress database error: [Disk full (/tmp/#sql_1_1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_wflivetraffichuman`

WordPress database error: [Disk full (/tmp/#sql_1_1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_options`

WordPress database error: [Disk full (/tmp/#sql_1_1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_options`

{"id":24644,"date":"2020-09-11T12:00:56","date_gmt":"2020-09-11T12:00:56","guid":{"rendered":"https:\/\/framen.io\/?post_type=docs&p=24644"},"modified":"2020-09-15T11:31:48","modified_gmt":"2020-09-15T11:31:48","slug":"wie-lege-ich-eine-neues-listing-an","status":"publish","type":"docs","link":"https:\/\/framen.io\/en\/help\/wie-lege-ich-eine-neues-listing-an\/","title":{"rendered":"How do I create a new listing?"},"content":{"rendered":"

Falls du wissen m\u00f6chtest, wie du auf dein Vendor-Dashboard zugreifst, schaue vorab bei diesem Artikel <\/span><\/a><\/strong>vorbei.<\/p>\n

So kann dein Vendor-Dashboard aussehen. Die Listings sind dann jeweils mit individuellen Namen zu deinen Locations ausgestattet.<\/p>\n

\"\"<\/span><\/p>\n

Wenn du ein neues Listing erstellen m\u00f6chtest, kannst du ganz einfach auf das „+“ klicken.<\/p>\n

\"\"<\/span><\/p>\n

Im ersten Schritt kannst du deiner Location hier einen Namen und eine Beschreibung geben. Dazu kannst du noch das Feld „Tag Line“ ausf\u00fcllen. Hier empfehlen wir eine kurze Beschreibung der Art von Location, um das Suchen f\u00fcr unsere Advertiser zu vereinfachen.<\/p>\n

Mit der Auswahl unserer vorgegebenen Kategorien, kann deine Location dann final von uns gruppiert werden.<\/p>\n

\u2013 Hast du das Gef\u00fchl, dass keine der Kategorien zu deiner Location passt? Dann kontaktiere uns direkt hier<\/span><\/a> <\/strong>und wir f\u00fcgen gerne eine Weitere hinzu!<\/p>\n

Sobald du den deskriptiven Part des Listings ausgef\u00fcllt hast, musst du nun weitere Bedingungen angeben. Dazu z\u00e4hlt der m\u00f6gliche Buchungszeitraum f\u00fcr Advertiser und die \u00d6ffnungszeiten deiner Location. Im n\u00e4chsten Schritt kannst du einen Preis f\u00fcr dein Listing angeben. Falls du dir nicht sicher bist, wie hoch du deinen Preis ansetzen kannst, empfehlen wir dir, dich an den anderen Locations zu orientieren.<\/p>\n

Im letzten Schritt gibst du noch die Adresse an, wo sich die Bildschirme befinden.<\/p>\n

\"\"<\/span><\/p>\n

Wenn du alles ausgef\u00fcllt hast, kannst du das Listing speichern und im Nachgang noch mit Fotos und weiteren Infos best\u00fccken. Sobald du einen Player verbunden<\/span><\/a><\/strong> hast, kannst du die Location auf „Online“ setzen. Nach einem schnellen Approval von unserer Seite, ist deine Location dann sofort f\u00fcr Advertiser verf\u00fcgbar.<\/p>\n

\"\"<\/span><\/p>\n

Hier<\/span><\/a><\/strong> erf\u00e4hrst du mehr zu Bookings.<\/p>\n

Hier<\/strong><\/span><\/a> erf\u00e4hrst du mehr zu Invoices.<\/p>\n

Hast du noch weitere Fragen?
\nWende dich gerne an einen unserer Experten unter
info@framen.io<\/a> <\/strong><\/span>oder ruf uns unter +49 (69)-2713-6789-0<\/a><\/strong><\/span> an. Alternativ kannst du hier<\/a><\/strong><\/span> auch einen kostenlosen Beratungstermin vereinbaren.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"

Falls du wissen m\u00f6chtest, wie du auf dein Vendor-Dashboard zugreifst, schaue vorab bei diesem Artikel vorbei. So kann dein Vendor-Dashboard aussehen. Die Listings sind dann jeweils mit individuellen Namen zu deinen Locations ausgestattet. Wenn du ein neues Listing erstellen m\u00f6chtest, kannst du ganz einfach auf das „+“ klicken. Im ersten Schritt kannst du deiner Location […]<\/p>","protected":false},"author":2,"featured_media":0,"parent":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"doc_category":[192,166],"doc_tag":[],"class_list":["post-24644","docs","type-docs","status-publish","hentry","doc_category-screen-provider","doc_category-marketplace"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/framen.io\/en\/wp-json\/wp\/v2\/docs\/24644","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/framen.io\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/framen.io\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/framen.io\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/framen.io\/en\/wp-json\/wp\/v2\/comments?post=24644"}],"version-history":[{"count":5,"href":"https:\/\/framen.io\/en\/wp-json\/wp\/v2\/docs\/24644\/revisions"}],"predecessor-version":[{"id":24731,"href":"https:\/\/framen.io\/en\/wp-json\/wp\/v2\/docs\/24644\/revisions\/24731"}],"wp:attachment":[{"href":"https:\/\/framen.io\/en\/wp-json\/wp\/v2\/media?parent=24644"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/framen.io\/en\/wp-json\/wp\/v2\/doc_category?post=24644"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/framen.io\/en\/wp-json\/wp\/v2\/doc_tag?post=24644"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}