midimatt

It seems I may be able to accomplish what I am trying to do by filtering “the_content”.

Just a few ideas – Perhaps the content isn’t controlled via a widget.

Be sure to check the Customizer (Appearance > Customize) to see if you can find it in there.

If your theme has any kind of settings page, you might want to check there as well.

If the sidebar menu is built with a plugin, you could check any potential plugin’s settings also.

There’s also a possibility that it’s hard coded into header.php. Perhaps search the header.php file for “right-menu__adress” (no, that’s not a misspelling) and see if it’s found.

Good luck!

What I ended up doing is registering a custom post_status and using that (as the unique trait you mentioned), then added a scheduled event that removes such posts created over a day ago daily. Seems to work like a charm! Thanks again!

I like your idea there in the second paragraph. I’ll give that a shot. Thank you very much for the response!

Nope… That just sorts them in the opposite direction I want them to be sorted by default. It also prevents any non-default sorting from ever occurring on the list.

I had them sorted the way I wanted by default – The issue is that the arrow in the column heading (used for sorting) first wants to sort in ascending order, which by default I already had them in… So it takes two clicks (instead of one) to sort in descending order.

* I did keep the “if(is_admin())” portion of your code, though… I didn’t think to do that before.

Those tag[attribute] selectors would work on the form elements, but not on their labels. Some jQuery could handle the labels based on those selectors on the form elements, but that wouldn’t be as simple or efficient as having a special class applied to the entire element that contains both the field and the label.

To give an example, lets say I have a form with three required fields. Lets also say I want to have a red asterisk on the left side of each label of the required fields, and a colon on the right side of each label.

First I would need to hide the trailing asterisk:

.ctct-form-wrapper form label abbr {
	display: none;
}

Then I would add a colon to the end of all labels:

.ctct-form-wrapper form label:after {
	content: ':';
	margin-right: 4px;
}

Then I would place a red asterisk before the required labels:

.ctct-form-wrapper .ctct-form-field-email label:before,
label[for="first_name___185a1b2c3d4e5f6g7h8i9j0k1l2m90"]:before,
label[for="last_name___234n1o2p3q4r5s6t7u8v9w0x1y2z56"]:before {
	content: '*';
	color: #ff0000;
	margin-right: 4px;
}

Currently, that last bit of CSS may need to be applied to each required field individually as shown, and removing the “Required” property of a field at a later date would require modification to the CSS.

If a special class is added to the container of all required fields, such as “.ctct-form-field-required”, all “required” element labels could be styled without targeting individual field containers. That would remove the need to edit CSS when new required fields are added or the Required property is removed from an old field.

• This reply was modified 7 years, 7 months ago by midimatt. Reason: code correction

Excellent! Sorry I did not notice that.

This requested feature could be even better if the recipient email address could be specified for each individual form (rather than as a setting that affects all forms).

… And if that’s implemented, perhaps making the subject line customizable per-form would be beneficial as well.

Note: The instructions tell us to replace (within php.ini)
; curl.cainfo =
with
curl.cainfo = "C:\PHP\Extras\SSL\cacert.pem" (or wherever you saved your cacert.pem file)

My php.ini file did not contain
; curl.cainfo =
so I added the following to the bottom of my php.ini file, which got it to work:

[curl]
; A default value for the CURLOPT_CAINFO option. This is required to be an
; absolute path.
curl.cainfo = "C:\xampp\php\extras\ssl\cacert.pem"

That got things working!

Make sure to change the path to the .pem file as well if it’s different.

Hi @tw2113

By golly, that seemed to work!

Note: The instructions tell us to replace (within php.ini)
; curl.cainfo =
with
curl.cainfo = "C:\PHP\Extras\SSL\cacert.pem" (or wherever you saved your cacert.pem file)

My php.ini file did not contain
; curl.cainfo =
so I added the following to the bottom of my php.ini file, which got it to work:

[curl]
; A default value for the CURLOPT_CAINFO option. This is required to be an
; absolute path.
curl.cainfo = "C:\xampp\php\extras\ssl\cacert.pem"

Thank you very much for your support with this issue.

Would you like me to add my note above to the post from a few months back (referenced in your response)?

Hi @tw2113

I am impressed with your quick response! I am glad this suggestion will be further evaluated.

Just to clarify, it’s not so much about the usage of the asterisk as it is the ability to control the styling of “required” labels/fields (which includes, but is not limited to, the asterisk). Adding a class (such as .ctct-form-field-required) to the label/field container on “required” fields would make it very easy for a user to alter the style on required labels/fields globally rather than individually.

Thanks much!

What it is telling you is that there is no <meta name="description" content="Insert page description here." /> tag in the HTML <HEAD> section. It won’t result in an error to the end user, but for Search Engine Optimization purposes the description can be important.

I don’t have Yoast, but I believe Yoast would allow you to add page descriptions either dynamically to all pages or individually on each page.

How about something like this in your page template:

If the URL query string is ?my_varname=myvalue

<?php
$my_variable = htmlspecialchars($_GET["my_varname"]);
?>

<script type="text/javascript">
var my_js_variable = "<?php echo esc_js($my_variable); ?>";
</script>

I’m going to throw an idea out there… Do you have a plugin that handles redirects? If so, it may be repopulating the database by reading the contents of the .htaccess file. The same plugin may be repopulating the .htaccess file based on what it has stored in the database. If you find such a plugin installed, try disabling the plugin, remove the database records that the plugin may have created, and remove the rule(s) from the .htaccess file. I could be wrong, but I don’t believe WP stores redirect data in the database unless there is a plugin involved (or a set of functions in the theme).

Is the link still properly formed when you view the source code of the generated page (not the editor) ?