ratamatcat

This code option did work, i.e.

border: 1px solid #000!important;

but I had other new problems, like the padding wasn’t working.

So I decided to remove my original code which referenced the Forminator form ID(s) in favour of a div to enclose the do_shortcode that calls the form into my template. There seems to be no similar issues when it’s a div.

The hiding submit button code did the trick.

thanks for the help.

PS – a handy feature might be a ‘Calculator’ form mode which automatically hides the submit button, just a thought. In my case the form is a dimensions calculator for users to select different images and see what the size is.

If that’s my only warning message am I safe to selectively sweep the other sections i.e. leave “Term Sweep” alone for now

So I have all these items that look like they need sweeping but to stay safe I shouldn’t sweep at all. Doesn’t optimizing leave the things alone that it should?

Hi Patrick,

Do you mean if I created any new form that the existing form 8921 ID can get changed? I thought its ID would be the same always?

Please refer to below example URL

https://www.imjexa.com/virtual-gallery/nebula-stars-dust

Development site P/W as below

Pv2Umc8X4

The rating can appear as per the setting After Content or Before Content.

I’m not following about a direct link, i.e. what is wrong with the link I placed in the last post. I’m not sure how to correct this.

And the screenshot, is this of my front end site?

thanks,

Please refer to below example URL

https://www.imjexa.com/virtual-gallery/nebula-stars-dust

Development site P/W as below

Pv2Umc8X4

Thanks,

Hi yes I tried it before but it also results in hidden rating stars when the button is clicked.

I went to wpDiscuz > Settings > Article and Comment Rating and used the four checkboxes there.

thanks,

Thanks David I will look into that. So if I find myself needing to add more and more admin-type Att tags to my media and then needing to exclude them from the site front end, if I ‘defined an additional taxonomy’ it would exist outside the regular tags and prevent this need. It would display in WP sidebar for MLA as (My new Att. tag)

Library
Add New
Att. Category
Att. Tag
My new Att. tag
Assistant

The code runs like a watch.

As a followup and general question, is there a difference in choosing an Att tag or an Att category when needing a taxonomy for internal control? I am more or less just duplicating your previous recommendation of a tag (i.e. for linking the gallery media together).

The purpose is simply to be able to point custom fields to a particular media – in this case the No. 1 media upload in a gallery of media. There I can place some field controls to customize elements of the gallery textual content. These fields don’t need to be on the media edit screen of all the gallery media, only the No. 1 screen.

I suspect either an Att tag or Att category are equally suitable.

Hey it’s really well done. I like how it retains the column in the admin.

I’ll try the hiding function in Excel but I don’t think I need it now.

Thanks!

This works great, thanks a ton! You really nailed it

Thanks Nithin,

I see what you’ve done, it looks great, with each select list exactly aligned below the next:

https://drive.google.com/file/d/1uiYqpywg2e6ZMi_al7NTU1qjOD7vbdA2/view?usp=sharing

From a functional and usability perspective, what do you think regarding the field label being hidden though? Below I have done a similar thing to your spacing, but increase the spacing enough to just show the field label:

https://drive.google.com/file/d/1rHjEJOzTdQVNkYTzESvlhFqfzwSM33-L/view?usp=sharing

Although the first example with tight spacing looks good, with the looser spacing the user can see the ‘required’ field asterix, which is only going to be on the first field.

thanks,

It works great as you outlined. Only thing I changed was I used a class instead of an id because I ended up requiring two separate div containers.

<script>
jQuery(function(){
		 jQuery('#showall').click(function(){
			   jQuery('.targetDiv').show();
		});
});					
</script>

The targetDiv class went for each div.

Activated using a button

<button id="showall">Extend Overlays</button>

Naveen it’s hidden under development so I don’t think I could put a password here. FYI The domain is in the link field above it will have graphic imagery and illustrations etc. One day it will be up.

Jacob that did it perfectly.

Great!

I started with your thinking too, a table to hold certain information in a neat format, and trying to feed data into that.

If you’re publishing different rows, or blocks etc I can highly suggest the Repeater field type by Advanced Custom Fields.

Once you create a new repeater field, you enter and manage the data in it from an edit screen of your choice (i.e. any admin page, post, or other WP designated area) like a control panel, and then save it. Then to get this data onto your front end site, you add the PHP code they have under the heading “template usage” below

https://www.advancedcustomfields.com/resources/repeater/

So that code is quite compact and goes into your template file that is behind the particular front end page or post that is displaying the information to your users.

In a repeater you can nest all sort of sub fields to have specific and differentiated segments of data.

If you’re not using template files and only Gutenberg check out what ACF has done to integrate with the Gutenberg.

As for the selecting functionality, I’m not sure. You could ask ACF support though they’re great. Perhaps there’s already be some setup for it.