sanjakl

Hi,

I understand how translation and .po files works. However, it is wrong to translate only once (let’s say T) because it needs to be translated twice. Tuesday and Thursday are not the same day and let’s say in our language they would be translated as (T -> T and T -> ?).

The same applies to Saturday and Sunday (S -> S and S -> N).

Hi,

the errors mentioned in the first comment have been tested and everything is working correctly.

However, the errors mentioned in the second comment have not yet been fixed. Can you please fix these errors?

Thank you in advance.

Hi,

the ‘load more’ button works correctly now.

The search engine is not working yet. Can you fix this error?

Thank you in advance.

Hi,

the first problem is fixed and works correctly.

The problem mentioned in the second part has not yet been solved. That is: When Performers / Organizers is clicked, a select appears for selection, but this element is too far away from the main element (offset upwards).

Can you fix this error?

Thank you in advance.

• This reply was modified 12 months ago by sanjakl.

Hi,

In the plugin settings we have a Language tab. Here we can translate certain texts such as Organized by, View Details …
However, here you can enter a translation in one language only. What is wrong is that if a translation is placed here, nothing else is taken into account. So if we mark English as the user language, everything is displayed again in English (original texts), except for those texts that are translated in the settings (for these, the original text is not displayed).

On the other hand, if we don’t translate the texts in the Language tab, the Loco Translate translation is not taken into account at all for those words. Organized by text, as I mentioned before, is not listed, and View Details does not detect the translation at all.

Can you fix the errors?

Thank you in advance.

Hi,

I have noticed another localisation error.

esc_html__( ‘S’, ‘eventprime-event-calendar-management’ ),
esc_html__( ‘M’, ‘eventprime-event-calendar-management’ ),
esc_html__( ‘T’, ‘eventprime-event-calendar-management’ ),
esc_html__( ‘W’, ‘eventprime-event-calendar-management’ ),
esc_html__( ‘T’, ‘eventprime-event-calendar-management’ ),
esc_html__( ‘F’, ‘eventprime-event-calendar-management’ ),
esc_html__( ‘S’, ‘eventprime-event-calendar-management’ ),

These are short names for the days of the week. However, the same letter is only displayed once for the translations. Let’s say T. I can’t translate it twice, which is wrong.

Thank you in advance.

Hi,

I understand that now, but when I click on the button and a new form page opens, the form fields are empty. Can you check this?

Thank you in advance.

There are a few little things that doesn’t translate within the plugin itself.
– After clicking on the Search button, the Applied Filters bar will appear below the search bar. Within it, the Days or Keyword filters are displayed in order. Neither word (Days, Keyword) is localised, although translations exist.
– In the calendar itself, localisation is performed, but the calendar title (ep-calendar-title-short) is not localised. E.g. for me it currently says October 2023 above the calendar.
– In Calendar View: When hover over an element (event) in calendar, a popup opens. The image, date, day, and other information is displayed in order. The day in the displayed list is not translated, even though a translation exists.
– In Square Grid View: If an event is not marked as All day event, the month is not localised. E.g. ?et, 05 Oct 12:00.
– When you add an event to the wish list, an alert in the top right corner shows that everything is OK. The Success title cannot be localised because it is not on the localisation list. The same applies for Error message.
– In Add new event submission form (frontend): When you click on Add more dates, you will see a line with a delete button at the end. The Delete text cannot be localised.
– In Add new event submission form (frontend): In the section for defining Preformers there is a text (Add new Event Performer). This text is translated as two separate texts (Add new Event) and (Performer). When the two translations are placed together on the screen, the translation is very meaningless. Also the Select text within the input field is not localised.
– Is it possible to arrange localisation for Google Maps?

• This reply was modified 1 year, 1 month ago by sanjakl.
• This reply was modified 1 year, 1 month ago by sanjakl.

<div class="ep-input-group">
     <select id="ep-filter-performer" name="" class="ep-form-control ep-form-control-sm select2-hidden-accessible" placeholder="translated text" .... aria-hidden="true">
        <option value="1287">.......</option>
     </select>
     <span class="select2 select2-container ..." ...>
         <span class="selection">
            <span class="select2-selection ..." ...>
                <ul class="..."></ul>
                <span class="...">
                    <textarea class="select2-search__field" ... placeholder="Performers" ...></textarea>
                 </span>
             </span>
         </span> ....
     </span>
</div>

This is also something related to the localisation of the plugin itself. In the search bar, among the Additional Filters, there are also Performers and Organisers. When using LocoTranslate to translate both texts, no change happens on the frontend, or it’s just not visible. As can be seen in the code above, the change happens in the first part which is hidden but not in the select2 element where it could also appear.

I also noticed that in the search bar, the wrong calendar is opening. When the calendar icon is clicked (From date), the calendar for the To Date opens.

• This reply was modified 1 year, 1 month ago by sanjakl.
• This reply was modified 1 year, 1 month ago by sanjakl.
• This reply was modified 1 year, 1 month ago by sanjakl.