Common upload errors on the HelloVEB interface

If an error persists after several attempts:

• it is worth reviewing the editing guidelines,
• or contacting the HelloVEB editorial team: [email protected]

The most common reasons:

• the event has been saved but not published,
• a required field is missing (e.g., date, location, main image),
• the event was uploaded with an expired date,

This usually occurs due to the following reasons:

• copied text (from Word, Facebook) with hidden formatting,
• overly long, unbroken paragraphs,
• unnecessary line breaks or emojis.

Solution:
Before pasting, it is advisable to paste the text "without formatting" and then re-format it on the interface.

Sometimes an event exists but does not appear on thematic pages or when filtering. This usually occurs when:

• an inappropriate main category, category, or genre has been selected,
• the Active, Sports & Exercise main category has not been selected for active events,
• Too many irrelevant tags have been entered.

Solution:
Select the filters from the main categories that best describe the event and use only relevant tags. For sporting and movement-related events, select the active tags so that they appear in the Sportregio2026.hu event calendar.

One of the most common mistakes is to enter the entire event description in the card description field. However, this field is not intended for this purpose. The card description is the basis for all list and thematic displays, so it is visually and technically very limited.

What is the problem in this case?
Text that is too long:

• it disrupts the uniform appearance of the cards,
• it is cut off on mobile devices,
• it reduces the clarity of the program schedule.

Solution:
Card description:

• should be a single sentence,
• 120-160 characters long,
• without formatting, lists, or emojis,
• a genuine "lead" summary.

The detailed description should always be placed in the Content block.

Possible causes:

• The address is missing or incorrect in the location settings.
• the location has not been saved.

Solution:
check that the address is accurate and complete.

A common mistake is to re-register an existing location or performer with minimal name differences.

Why is this a problem?

• Events are scattered across multiple locations,
• the system becomes difficult to navigate,
• it becomes more difficult to maintain the content.

Solution:
Before creating new content, always check that:

• the location,
• the person,
• or the group is already in the database.

If so, use and expand it.

In the HelloVEB system, it is not necessary to set a specific time for an event.

If, for an event:

• a date is selected,
• and you publish the content,

the event will automatically appear in the program calendar based on the specified date(s).
In this case, the system will manage visibility itself, and no further action is required in relation to timing.

This is the most common and recommended operation, especially if the event can already be communicated publicly. When is it worth using a delay?

Delay should only be set in special cases when the content is already ready in a technical sense, but cannot yet be made public for communication reasons.

A typical example from editorial practice:

• the event data sheet has already been prepared,
• the dates have been set,
• but the official announcement of the event will only be made later, for example, in a week's time,
• the organizer knows that on the day of the event, they will not have time to log into the system and publish the event.

In this case, scheduling is a convenience and security feature.

Scheduling allows you to:

• prepare content in advance,
• publish it in advance,
• but set when it should be available to visitors.

This ensures that:

• the content appears exactly at the time of the official announcement,
• there is no delay in communication,
• you do not need to log into the system manually on the given day.

Scheduling is not a mandatory feature and is not part of the basic upload process.
It is only worth using if:

• you are working in advance,
• the publication date is fixed,
• and you know that you will not have the opportunity to intervene immediately later.

If the event is already public and there are no communication restrictions, then setting the timing is unnecessary and you can safely skip it.

In practice, this means that:

• all content contributors can see existing events, locations, and people,
• not only content recorded by their own organization is available,
• the system can thus ensure a uniform appearance and interconnected content.

This makes it possible, for example, to:

• link multiple events to the same location,
• display all events for a performer in one place,
• users get a complete picture of the regional offering.
• Why is this good for content providers?

  Shared visibility creates cooperation rather than competition.

  Advantages:

  • No need to recreate existing locations or people.
  • content reinforces each other (searchability, recommendations),
  • the program can appear on multiple platforms with a single upload.

  This mechanism enables the principle of "one upload – countless appearances".

  Does this mean that anyone can edit other people's content?

  No.
  Although the content is visible, special permissions are required to edit it.

  The system:

  • provides a transparent database,
  • but editing rights remain restricted.

  This ensures both:

  • collaboration,
  • and data security.
  • What should you pay attention to when uploading content?

    Since a lot of content is visible at the same time, it is particularly important to:

    • check before uploading whether an event, location, or person already exists,
    • search for keywords in the media,
    • Use descriptive, unambiguous file names.
    • Consciously link to existing content.

    This helps to ensure that the system remains transparent and usable for everyone.

After filling in the content in Hungarian:

• by clicking the translate button, the system automatically prepares the foreign language version (translation -> target language -> English),,
• the translation is placed in the appropriate language fields,
• The text can then be freely edited.

The translation is a non-live link, meaning that:

• subsequent Hungarian modifications are not automatically updated in the foreign language fields,
• the translation must be checked again after each change.

It is not necessary for the partner, but a subsequent check is recommended. The editorial team accepts no responsibility for the quality of content translated by DeepL.

The uploader is responsible for all uploaded content.
The editorial staff of HelloVEB sets the editorial guidelines, but does not assume responsibility for the content.

The system works with specific image formats. If images that differ from these are uploaded, the system will crop, distort, or display the material in poor quality.
Common errors:

• image resolution too low,
• photos cropped unevenly
• Uploading a portrait image instead of a landscape image,
• Using an image containing text or a poster as the main image.

Solution:

The main image should always be a mood image, not an informational poster. Use a high-quality, landscape-oriented, visually clear image that is not a poster and does not contain too many captions. The hints below the card, cover, and share images will help you choose the right proportions. The image sizes uploaded to the content repository are fixed.Detailed posters can be uploaded to the content repository in their original dimensions.

The following content types can be uploaded to the media library:

• image files (for events, places, people),
• images intended for galleries,
• videos (typically embedded or linked),
• documents (e.g., program booklets, informational PDFs).

The primary goal of the media library is to ensure that content can be reused for multiple events and platforms, therefore, only materials that are:

• are of good quality,
• can be interpreted in multiple contexts,
• can be used over a longer period of time.

The goal of the media library is not to collect unique files, but to create a commonly used visual resource.

In practice, it is recommended to use the following formats:

• Images: .jpg .jpeg .png .webp
• Documents: PDF

The following is particularly important for images:

• suitable resolution (recommended minimum: 1200 px width),
• compliance with the specified image dimensions (in the case of cards and wine labels),
• avoid distortion and pixelation.

Files with an inappropriate format or aspect ratio:

• may display poorly,
• may result in automatic cropping,
• may impair the uniform visual appearance.

The file name is not a technical detail, but one of the most important organizational elements of social media.

The document specifically emphasizes that file names should:

• be descriptive,
• refer to the source and type of content,
• facilitate retrievability and legal compliance.

• IMG_4567.jpg
• plakat_final2.png
• kep_uj.jpg

These do not reveal that:

• what can be seen in the image,
• who or what it relates to,
• where it comes from.

The file name contains:

• the name of the location/event/organization,
• the source (e.g., Facebook, Instagram, stock),
• the function (cover, gallery, press photo).

Examples according to the basic principles:

• balaton_conference_press_photo_anna_nagy.jpg
• revfulop_festival_fb_cover.jpg
• keszthely_exhibition_insta_post.jpg
• fishing_free_license.jpg

Since the media is public, it often happens that:

• an image has already been uploaded from a location,
• another editor has already added media to an event,
• the same image would be added from multiple sources.

If this is not checked:

• duplicates are created,
• the media becomes unmanageable,
• the database will grow unnecessarily.

Solution:
Before uploading, it is always worth:

• search for keywords in the media (location, event name),
• check whether an existing image can be used,
• if so, do not upload it again, but use it instead.

This is why keyword file naming is so important.

Yes, and this fits perfectly with the logic of the system.

In the HelloVEB media library, neutral, general mood images can be used freely, for example:

• city life images,
• nature photos,
• sports, cultural, and community scenes.

These:

• can be used for multiple events,
• do not become obsolete after a certain date,
• and help to create a uniform visual appearance.

The document emphasizes that the media also functions as a visual resource, not just as a collection of illustrations for individual events.

This is not an error, but is due to the way the system works.

What happens in this case?

• After uploading, the image is still being processed,
• it may appear gray or missing for a short time.

Solution:
After saving and publishing:

• wait a moment,
• refresh the page,
• the image will appear.

Yes. In many cases, uploaders upload A4 posters as card/cover images, with small text, logos, and dates, which is not recommended. The image sizes of images uploaded to the content repository are, so detailed posters can be uploaded to the content repository in their original image size. Why is this not acceptable?

• It is unreadable on mobile devices,
• it is visually overloaded,
• it does not comply with the logic of the card display.

Solution:

• place the poster in a gallery or in the content,
• card/cover image should always be clean, without text or with minimal text.

• If possible, do not upload many very similar images from the same event.
• Only submit legal, usable content.
• If the material comes from an external source, the source must be indicated in the content.

If these fields:

• remain empty,
• contain poor content,
• or contain the same text in all three places,

then:

• search engine optimization will deteriorate,
• social sharing will be weak,
• and the content will be difficult to interpret on card interfaces.

This is not a technical error, but a content editing problem.

• We write each field for a specific purpose.
• We do not copy the same text.
• We adhere to character limits.
• The tone is always appropriate for the context.
• The three descriptions together form a coherent content system.

The primary goal of SEO is to ensure that content appears high in search engine results (Google, Bing, etc.).
This text is not intended for visitors to the site, but rather for users arriving via search engines.

Accuracy according to the editing principles:

• length: 155-160 characters,
• concise, informative wording,
• rich in keywords,
• clearly describes what the content is about,
• may contain subtle calls to action,
• does not contain HTML, emojis, or special characters.

Common mistake:
Advertising text, overly long descriptions, or copying the card text into the SEO field.

Solution:
The SEO description should always be written as if it were a Google search result that can be understood on its own.

The share button appears when the page is:

• on Facebook,
• on Messenger,
• LinkedIn,
• or other social media platforms.

This text is not intended for search engine optimization, but rather to attract attention.

Exact match according to the basic principles:

• length: 1-2 sentences (approx. 200 characters),
• more direct, friendly tone,
• evokes emotion or curiosity,
• may include event names, highlights,
• may encourage action (e.g., "Check it out," "Come on over").

Common mistake:
The share description is left blank or contains the same dry text as the SEO field.

Solution:
The sharing description should always be written in human, social language, not search engine language.

The card description is one of the most important elements of HelloVEB, because it appears:

• in event lists,
• on thematic pages,
• in mobile view,
• card recommendations.

This text is not a detailed explanation, but rather a quick identifier.

Accuracy according to the basic principles:

• length: short (160 characters)
  (the system may deviate from this in the case of events, but the principle of brevity still applies),
• keyword-rich,
• easy to read on mobile devices,
• does not contain breaks or lists,
• visually complements the image.

Common mistake:
A full event description, several sentences, or marketing text is included here.

Solution:
The card description should always be a single short thought that helps the user decide whether to click on the content.

Basic formal rules according to the document:

• date: July 1, 2025 (according to Hungarian spelling rules),
• duration: 10:00 a.m. to 6:00 p.m. (with a hyphen, without a comma),
• address: complete and accurate,
• phone number: +36-xx-xxxxxxx,
• listing in bullet points rather than long paragraphs,
• italics only for keywords, dates, and locations,
• italics should only be used for source references, quotations, and CTA text.

Common mistake:
Too much emphasis within a paragraph, resulting in visually "noisy" content.

Solution:
Highlighting should always be functional, not decorative.

One of HelloVEB's fundamental principles is that content should never be a closed endpoint in itself.

Editorial experience:

• missing links,
• non-clickable URLs,
• copied text without source.

Correct solution:

• active, clickable link,
• in a separate text block at the end of the content,
• marked in italics,
• and, if possible, supplemented with a CTA button (e.g., "Learn more," "View the program guide").nbsp;

This ensures that the user does not get stuck in an information dead end.

Expected style:

• neutral,
• informative,
• clear,
• not from the organizer's point of view.

Avoid:

• "we organize," "we look forward to seeing you" (except as quotations),
• excessive promotional language,
• emotional overheating where informational content is needed.

We recommend separate styles for different types of content (events, locations, article, gallery, etc.), but in all cases, the common principle is that the reader should be able to find their way around quickly and reliably.

The entire text should be divided into sections more carefully.

Basic principle:
The purpose of the content is to:

• quickly convey the essence of the event or location,
• be visually well structured,
• encourage further action (ticket purchase, registration, details).

Solution:

• the content always starts with the text on the card,
• subheadings must be used for longer texts,
• A summary description instead of a complete program plan,
• Detailed information linked, not copied.