hube2 / acf-input-counter Goto Github PK

I have a text field which is capped at let's say 50 characters.

If I write a title which has 49 characters and includes an &, an error is thrown, since & gets stored as & which is 4 characters more and this not a 'valid input'.

Is there a way around this ???

but installs 1.3.1 and keeps nagging about 1.4.0. Setup mistake somewhere?

I'm wondering if I updated and got the WYSIWYG support working again if you would consider merging it here. @puntonero created this feature here when the plugin was at 1.4, but now it's no longer working for me with the current ACF release and this plugin is up to 1.5...

Definitely a feature I would be willing to help maintain and seems like it would make sense to have everyone contributing to the same code base. Just getting a sense for if I need to plan to maintain my own fork for this feature or not.

Thanks!

Not too familiar with either the plugin or ACF internals so apologies if I'm missing something obvious. I can see in dev tools that acf-input-counter.js is being loaded, my text field does have a limit of 160 characters (published the group twice after installing the plugin just to make sure) but I still cannot see counter appear.

Field definition:

Field in use:

Let me know how I can help nail down the problem.

Like it says, this should have a proper readme.txt file so that people can see what's been updated if they use github updater.

Hi Hube2. I discovered a conflict with yoast primary taxonomy feature. primary taxonomy feature will stop working when the acf-input-counter is active.

It's not really an issue, but are there any plans to have this plugin in the Wordpress Plugin repository? If so, that would be awesome. I'd love to assist you think it's a good idea.

Hi dude,

Is it possible to get a counter for Wysiwyg ?

Peace

After last update characters in other fields again began to show count as I typed. But way to set character limits in wysiwyg editors are now gone. I am not a coder. This was helping me a lot to write content for web pages without spilling over beyond design box boundaries. Request this to be addressed please. I truly appreciate all the hard work you put in, and it is because of people like you that some of us can have some relief in otherwise complex work. Thanks a lot, and wish you all the best.

Hi John, i find a small bug in file acf-input-counter.php

In line 61:

$len = strlen(get_field($field['name'], $post->ID, false));

With Debug TRUE, generated this error: Notice: Trying to get property of non-object

A user specific text domain was added by c73b35b.... remove it

Add filter so that display of max and count can be altered.

Is it possible to use placeholder instead of max-length to trigger the counter ? In fact, i would like this counter but i don't need to limit my characters with max-length

Now when you try to save (in my case options page) appears an empty ALERT preventing saved

Looks like acf-input-counter.php is version 1.4.1 but releases stop at 1.4.0

Just a heads up, I installed ACF Input Counter 1.4.0 and ACF 5.6.10 and on activation of ACF Input Counter the visual part of the wysiwyg no longer displays, the text in the field is shown as html and the visual tab no longer works.

Add filter to allow only adding counter to specific fields. Will require additional checks in JS to make sure containers exist before trying to insert count into non-existent elements.

I noticed that there is no counter/limit on the number field in ACF Pro.

Maybe that could be an addition ?

checking to see if the current page is the acf field group editor is somehow interfering with ACF