mpek

Let me explain a little more.

When you install ninja forms in wordpress with a system language that is already supported by ninja forms the custom labels are being installed in wordpress language.

If you install ninja forms in a multilanguage environment, where wordpress is in its native (english) language, all custom labels of ninja forms are in english as well.

If you need to offer forms in multiple languages you need to build the forms for each language individually. You need to adjust custom labels as well, otherwise they show in english only.
To make this process easier, it would be nice to be able to:

– import custom labels already shipped with ninja forms or
– import from a text file with translations in it, if language not supported.

What do you think?

Ok, got it. Thank you!

Okay, that helped, thanks a lot. I wasn’t sure if the conversion process would be started again when pressing the button…

Now that I have reinstalled the plugin on that site that is already converted, for mixed content filtering, the huge message in backend is not necessary, how can I get rid of it?

Thank you for your answers!

Is it enough to re-install the plugin to avoid manual fixing at the moment?

After conversion, I once deactivated the plugin and recognized that the site url in generel settings was reverted back to http, your suggestion said it is not to deactivate but to delete the plugin by ftp. Then i changed the site URL to be https and it worked, but with mentioned statement in Chrome.
Do I need to do the conversion again after re-installing it.

Please scroll down on URL the small pictures have the lightbox effect. Do you know why two are opening?

As stated in another topic, your plugin changes site url back to http when deactivating plugin. It is likely to be the reason for this issue.

Thanks for your fast reply.

I just reported another issue and the deactivation explains that home/URL was http, in my assumption after conversion, but it is by deactivating your plugin.

I guess it would be better not to revert back to http when deactivating plugin?

This topic is resolved! Thank you!
I was playing around with shortcodes to build an all events page and couldn’t see at first that this database error was due to wrong usage of shortcode parameters.

Could you check that your site url/home is actually as expected?

It was still at “http” ??

Thank you, regarding the manual backup, I’ll get back to you.

Okay, thank you very much!
I fixed that problem. After a change in event description the event status was changed to “draft” and no one from us recognized it after that change. I’m sorry, that I did not see that, but I couldn’t imagine that this could happen if you simpley change the description text.

One other thing while searching for the error above, is this error message i get:

[12-May-2017 11:17:48 UTC] WordPress-Datenbank-Fehler You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY event_start_date ASC, event_start_time ASC' at line 2 f??r Abfrage SELECT * FROM DaS_eme_events
       WHERE event_id IN () ORDER BY event_start_date ASC, event_start_time ASC von do_action('wp_ajax_wpseo_filter_shortcodes'), WP_Hook->do_action, WP_Hook->apply_filters, WPSEO_Shortcode_Filter->do_filter, do_shortcode, preg_replace_callback, do_shortcode_tag, eme_display_single_event_shortcode, eme_display_single_event, eme_replace_placeholders, eme_add_booking_form, eme_add_multibooking_form, eme_get_event_arr

• This reply was modified 7 years, 10 months ago by mpek.

I see, thank you for your answer. Luckily, I could solve the problem in between without that backup, but still, your answer does not fit to the problem exactly.

Well, the change to https is some weeks ago and the backup is from yesterday. Somehow UpdraftPlus does not recognize that backups are made from https and still sees http only.

I don’t want to leave unmentioned, that I have MainWP in place and manage a few sites from there, including backups with its UpdraftPlus extension. After the change to https, the website has been newly added to MainWP by telling it the new https-domain. Perhaps there is a conflict that is not regarded to your plugin but this extension (as well)? I asked their support as well already today, but you were quicker!

At least in future…