Great plugin, with great support

Hi Vitore,

Would you mind going into more details about the bugs you are noticing? I just updated the plugin a short time ago.

The translations are brand new so it’d be great if you can give me some insight into how those are causing errors.

Thanks!

I’ve upgraded from the free version, in wich I had alrealdy configured 2 forms.

When I try to list the Entries, I get the following error: “Fatal error: Call to a member function entries_errors() on a non-object in /home/t1048734/public_html/wp-content/plugins/visual-form-builder-pro/visual-form-builder-pro.php on line 3645”

I tried to debug briefly, and the object $entries_list is NULL.

The translation is just wrong all accross the plugin, causing a little confusion. Not really causing erros in the functionality, but really messy.

I’ll look into the entries_errors bug.

As far as the translations, Português is not my native language and I used a translation service. Would you be willing to fix the messiness and send me the corrections? Or at least point me in the right direction so I know what to correct?

Thanks for letting me know about these issues. I disagree with your review that it’s awful, but you are entitled to your opinion.

Matthew,

I am willing to help with the translation, if you point me in the right direction (the tools to use, file format to use, etc.).

My first impression was really bad, but your attention really changed my oppinion. As soon as the bugs are corrected, I will change my review.

Thanks!

I use the Codestyling Localization plugin for translations.

Basically, you will go to Tools > Localization, scroll down to Visual Form Builder Pro and click on the Edit button for your language (Português/Brasil). Go through and update the strings. When you are finished, click on the ‘generate mo-file’ button at the top of this Edit page. Then, all you have to do is send me the .po and .mo files.

If you need more help with that, send me an email through my contact form.

Hi Vitore,

The Entries problem has been corrected in 2.2.6. It was introduced in 2.2.5 and had to do with the new translations.

Please let me know if you are still have issues.

Matthew,

Works like a charm! Thanks for the support. I also finished the translation to pt_br. If you want to include it in the next release, I can send you the .mo file.

Thanks again for the attention!