szabesz

Thanks for the tip, it is good to know! I have just tried it but it did not help in this case.

Hungarian translation IS used properly when the locale is set to Hungarian, however, when I set it back to English, these few labels do not change. It is not a big deal, and I just wanted you to know about it. Your devs might want to look into this as it appears to be an issue with NextGen, but when we have to deal with WordPress, one never knows…
Thank you anyway!

The screen capture shows a state in which WordPress was set to use its default English language. So the labels of the tabs and also the labels of the accordion are in English. However, the labels of the radio buttons are in Hungarian (except for Basic TagCould, but that one is probably not translated). Shouldn’t they be in English too? At least, that is what I expect to happen.

Thanx for replying! I will check out how i can possibly contribute to translations.

About the issue:
You say “if the strings have not been translated they will revert to their default which in this case is English”.
Actually, I am “missing” the default English labels, not the translated ones. I mean, those strings did not revert back to English, and that is this issue, not the other way round. Sorry, I was not clear.

So if you take a look at my screenshot, the “display types” are still in Hungarian, even though all the other strings have been switch to English. The translated strings are OK< but not the default English counter parts. Strange issue…

Thank for taking a note of this.
I always use E_ALL just of keep an eye on “everything” and 95% of the plugins I use on various WordPress based websites never generate Notices of any sort. I understand that PHP code can run just fine with Notices, however one sign of high quality code is the complete absence of Notices. At least, in my point of view ??

Keep up the good work, and thanks for providing a free version of NextGEN!

NextGEN and NextCellent are the only plugins that realize the need of being able to store and organize the files of galleries in separate folders, and it is also important not to litter the WP uploads folder with useless image sizes that WP and other plugins keep generating even when they are not needed at all. But this was off topic ??

Thanks for your reply!
I figured it out, it was an issue with the Theme, which has this rather unconventional rule:
div { position: relative; }
Strange, but it has not have any other side effects so far. I overwrote it so that it is back to the default “static” value and the buttons behave as expected. Luckily, only one div on the whole site seems to be using relative positioning, so I just had to fix that element and nothing else.

I hope this helps others who happen to run into this.

Anyway, thanks Cais!

Hello mastercourse,
Thanks for your reply!
cheers,
Szabesz

Hi mastercourse,
I have just answered a similar question at:
https://wordpress.stackexchange.com/questions/207131/reset-my-password-links-to-itself-page-refreshes
What was your solution? As far as I can see, your “my-account/lost-password/?reset=true” page no longer displays the form.

@wpready
Hi,
Thank you for informing us.
Cheers!

@marty861
Have you tried the workaround Adriano provided on wp-types.com? Although he said it is not the best approach to fix it, I’ve applied it (to the child theme, of course) and everything seems to work fine. Note that I might have missed something since I do not use all the features of either WP Types or NGG.

@photocrati
I have not myself tried to analyze the issue in detail, but based on Adriano’s description, NGG should be “fixed”, since NGG uses Select2 in an unconventional way. Just correct me if I’m mistaken.

Hi,
Thank you for dealing with the issue, I really appreciate it!
regards
szabesz

Thanks for your reply! Actually, I am trying to use the Types plugin (wp-types.com) and NGG together, however, Types normally uses the official version but fails to do so because your version takes precedence. You can reproduce the conflict if you install both plugins, create Parent/Child (1-to-many) post type relationships a try to set the “parent” on a custom post type. The Select2 UI used by Types fails, since it cannot use the official Select2 library.

For more details, please see:
https://wp-types.com/forums/topic/how-2-solve-the-cssjs-conflict-with-nextgen-gallery-on-wp-typ-post-relationship/

As far as I understand, the conflict arrises because of the way the modded select2 is being used.

I hope you can deal with this issue. Although not too many plugins use Select2, those that do might fail to work properly as well.

regards,
Szabesz

Hi,
I also hope the author will be able to push out the update soon. WordPress 4.3 is out in a few days.
Thanx

Thank you for your response, I do appreciate it! On all my sites Duplicator is back to normal… Keep up the good work, Duplicator is an outstanding tool!

Hi Cory,

Thank you for your quick reply! I have run into the recent collation issue too (in my case non-ASCII characters were not displaying properly), but I could solve it by using define(‘DB_CHARSET’, ‘utf8’); in wp-config.php instead of define(‘DB_CHARSET’, ‘utf8mb4’); But I suppose it is an unrelated issue.

Simply removing and reinstalling Duplicator did not help, so I used the “Cleanup” tools as well. After reinstalling the plugin I also used “Delete Legacy Data” and “Clear Build Cache” and right now on all four sites – on sites having these issues – Duplicator is back to normal.

Is it possible that this was the solution? I used to use all these clean up functions after duplicating a site with the plugin, but recently I started to skip these steps in favor of only using the cleanup function displayed at the end of the installer, assuming that the latter is enough.

Thanks in advance,
Szabesz