• Translation BUG & Outdated documentation

    Translation BUG
    On your Documentation page(missing pictures too, seems to be deleted): https://www.wpsupportplus.com/knowledgebase/translate-plugin/

    On your documentation:
    – Create new directory wpsp in wp-content/languages directory(translation from this directory are not processed) if I put translation files in: wp-content/plugins – as: wp-support-plus-responsive-ticket-system-ro_RO.mo & .po translation are processed partially.

    Strings(text) that aren’t processed(translated) by menus, the translation is performed and saved & compiled but is not processed(only partial):
    #Menu Tickets(not processed translation) in submenu Apply Filters:
    -All (inside field, everywhere)
    -By field(& Created_by too, inside field)
    -Search…
    -Reset Filter button
    -Apply & Remember button
    -Cancel button

    #Menu FAQs:
    -FAQs
    -Category: (which is upside of field with categories, down are processed where show the FAQs questions & categories).
    -All(in field)
    -1 of 1 Pages(in Tickets menu this translation are processed, in FAQs menu not).

    #Menu Create New Ticket
    Remove(from attachements, after attachement are uploaded, done translation are processed).

    Other BUGs:
    Advanced Settings => Front-End Display => Open Ticket Action Buttons: Background-Color of “Change Status” & “Close Ticket” are inversed. If you put background color red at “Close Ticket” and background color yellow at “Change Status” the result will be:
    Change Status => background color = red
    Close Ticket => background color = yellow

    #Presale Questions
    Please understand that I’m a freelancer that I love build with WordPress and I try to switch all my customers from Jira Core & Jira Help Desk to WP Support Plus because are integrated with WordPress & for speed of your software.

    I will be your customer for a lot of websites with your premium addons for many years but please consider to solve BUGs quickly and mandatory to add as “preselected value” at:
    Priority(my customers want Medium as default preselected value).
    Category(they want general as preselected value).
    FAQs category(they want “General FAQs” as preselected category).
    Canned Reply to have categories too, even one as preselected(when agents offer support to different teams they must fast change category, autocomplete at canned reply will be a big plus too).

    Doesn’t matter if this implementations will be as premium addons, I will buy them!

    • This topic was modified 7 years, 9 months ago by Marius.
    • This topic was modified 7 years, 9 months ago by Marius.
Viewing 3 replies - 1 through 3 (of 3 total)
  • hi mariusfv
    did you find a way to translate this plugin correctly or not ?
    help me please , i want to be translate the plugin too.
    email me : [email protected]
    or telegram me : @ehsangh70

    Thread Starter Marius

    (@mariusfv)

    @ehsan102 – Nope, I didn’t a find a way to translate this plugin because of BUG(I have translated with Poedit a lot of plugins but this plugin have BUG’s).

    I see that documentation & support are treated with indifference.
    Shame to authors, this plugin can have potential on the market.

    Thread Starter Marius

    (@mariusfv)

    @gauravdohole – Do you check the translation BUG?
    In the near future do you integrate WP Support Ticket with WPML?

    • This reply was modified 7 years, 9 months ago by Marius.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Translation BUG – Documentation Outdated & Presale Questions’ is closed to new replies.