Tibor Paulsch

Thanks Ryan! I saved my AQL block as a synced pattern (apparently without the no results block), and it turns out it is not available when editing the pattern later on. To be honest, I did not even know it existed ??

Starting with a new AQL block from scratch, the no-results block showed up immediately.

Oh man…so very much this:

?(Be SURE to hit RETURN to submit the value and see it switch to a gray box for this to actually work. Otherwise, the field name will not be saved, and this will confuse the heck out of you).

Thank you very much for sharing!

@bossdat Indeed a great plugin, and as far as I can see it is still compatible with 6.3.

That being said, it would indeed be nice to have some extra features/options.

I would like to be able to set a default bg- and text color, as well as having the defined theme colors available in the tooltip color settings.

And for improved a11y some aria-tags in the rendered tooltip would be a great improvement too I think.

@chinteshprajapati Any chance you will publish the uncompiled src & package.json on GitHub? Seems like it could be a nice learning source too!

Cheers!

• This reply was modified 1 year, 3 months ago by Tibor Paulsch.
• This reply was modified 1 year, 3 months ago by Tibor Paulsch.
• This reply was modified 1 year, 3 months ago by Tibor Paulsch.

Thanks Mark!

Update: turns out there was some custom JS used in the form that was causing the problem.

I am having the same problem on a client’s site: when GF Zero Spam is active, all entries are being marked as spam. Looking at the entry dates this seems to be happening since the end of juli. Before that it was working perfectly.

There are no other anti spam plugins active.

GForms 2.5.9
GF Zero Spam 1.1.3

Hope this helps.

Cheers, Tibor

Haha: if found the cause: it was not clear that I also had to install the Sprout Invoices plugin to make this work. Although I do feel a bit stupid, you might want to add this to the plugin installation instructions as being a requirement and (even better) provide an admin notice upon activating the GForms addon.

Anyways: thanks for the support!

Nothing wrong with the form output. It has a name, address and product/price field, all with default settings (label, name etc.).

But the error tells me the Class ‘SI_Line_Items’ is missing. I have also done a search in the plugin’s files, but as far as I can see the class is indeed not defined anywhere.

Hi Elana,

So far there are no options set, since the error occures as soon as I click on the “Add new feed” button. The error says it is missing the Class SI_Line_Items that is called in this function on line 138:

public function feed_settings_fields() {

		$li_types = SI_Line_Items::line_item_types();
		$line_item_types = array();
		foreach ( $li_types as $value => $label ) {
			$line_item_types[] = array(
				'label' => $label,
				'name' => $label,
				'value' => $value,
			);
		}

Cheers, Tibor

I submitted the translation just now ??

However, I noticed that are some strings on the translation page that I did not see in the POT file in the plugin.

Alrighty! Will do!

Aargh..got it: I saved the updated translation in the plugin i18n/languges directory of the plugin itself, instead of in the /wp-content/languages/plugins folder. Issue fixed as well ??

I should take a break more often ??

Would you be interested to add the Dutch translation to the plugin? I could send it to you.

Thanks again for thinking with me!

Hi Richard,

Thanks for your quick response ??

This is on a local install. And as I said: I fixed the translation string (I am pretty sure the error was due to a typo I made in the part), but somehow I am still getting the old translation. I even tested this by changing the translation text. Quite weird. Any suggestions on what could cause this?

Update: I might be wrong..I added a Dutch translation and I think I might have made a mistake in that particular string. Weird thing is that I adjusted the translation, but am stille seeing the old trnaslation. I’ll keep you updated.

Ah, that makes sense ?? Thanks for the quick response!