Bluefox1

Hi there,

sorry to interfere in this topic as i don’t have a solution but was wondering if there are plans to integrate it. The thing is that i also like to have some checking. For now i’m only letting registered users post things.

Did read this link:
https://support.bestwebsoft.com/hc/en-us/articles/202352499-Add-Google-Captcha-reCaptcha-plugin-to-a-custom-form-on-my-Wordpress-website

and based at: https://wpadverts.com/documentation/child-themes-and-templates/ i guess the file that should be adjusted is add.php

Have to say that i’m a newbie to WordPress so maybe i’m totally wrong but just wanted to drop a note.

hi guys,

This topic is an old one but it might be usefull to others so will answer. Am using WordPress 4.4.2 + WP Tab Widget 1.2.4 and did also ran into translation problem.

Instead of English I did want to see the text in Dutch so did translate the text with PoEdit and created some Dutch language files.

Maybe I’m wrong but did install the translated files to this folder:
../wp-content/plugins/wp-tab-widget/languages/

In that folder are these files: default.mo + default.po but making changes into those files doesn’t seem to be recognized. Did take a peak at a different plugin how it was done and named my Dutch files as “wp-tab-widget-nl_NL.mo” + “wp-tab-widget-nl_NL.po”.

As a result these files are in that folder:
– default.mo
– default.po
– wp-tab-widget-nl_NL.mo
– wp-tab-widget-nl_NL.po

don’t know if the Dutch language files are going to be overwritten in case of an update but things seem to be working for now.

The key part here is that you need to add the name of the plugin (wp-tab-widget)+ language tag (nl_NL in my case).

just to be helpfull..

Greetings,
Blue

Thx for the clarification Jason and yes you have some good points there.

Actually I’m aware of the things you mentioned as I did take part in development of a free script myself so can fully understand it.

you are right and will do that when the fix is there.

This is a known bug

ah ok, didn’t knew that but in that case it’s clear.

We are going to release an update in the next few days to correct the problem.

good to know that and thx

did take a peak in the readme.txt and am seeing this note

4.3.1
————-
[Fix] PHP warning being displayed in textareas (settings) under certain circumstances (thank you, [Chris](https://www.ads-software.com/support/topic/in-php-debug-mode-errors-appear-in-textareas))

so maybe it’s related to that change

Not sure if it makes a difference but am running PHP 5.3.29

hmm, can it be related to settings of the textarea field?

did try to add something to “extensions to track” within the tracker tab and it wasn’t stored either. the radio buttons are stored.

@photocrati

Unofrtunately I’m unable to give a clear answer to the problem but this issue can be closed. Can state it wasn’t related to NextGen.

Did uninstall some plugins and tried to reinstall NextGen. Was presented with a white screen so enabled WordPress debug and tried again. Upon install i was again presented with a white screen but this time with a memory text pointing to “…/pomo/entry.php”.

So increased memory by adding “define(‘WP_MEMORY_LIMIT’, ‘128M’);” to wp-config. After that nextgen did install.

Didn’t receive the deprecated message so would say that was due to something else (likely another plugin).

I would if i could but can’t give a clear answer.

It seems it’s related to something else, this as i did install a clean WordPress offline and when enabling NextGen there was no issue at all so you are right it’s most likely that it’s related to something else.

Next thing i want to do is to use the files of the website to test but didn’t had the time (yet) to test thoroughly

alright, will do

thx for the reply.

Ah yeah am seeing it in the changelog so i guess it should be related to something else. Will test locally and if do find the problem i’ll let it know.

Greetings,
Blue

…