3T_MJ

No one there having any ideas?

Is this the only option? Creating an own widget just to add one or two post types?

I found a code for the original WP recent post widget but this doesn’t work for the Hueman dynamic tabs widget.

Is there a way to adapt this function so it would work for the hueman dynamic tabs widget or at least for the recent tab of the widget?

// display custom post type 'videos' and regular 'post' in recent posts widget
function wcs_cpt_recent_posts_widget( $params ) {
    $params['post_type'] = array( 'video', 'post' );
    return $params;
}
add_filter( 'widget_posts_args', 'wcs_cpt_recent_posts_widget' );

Any help would be appreciated.

@dmitri51 thanks so much. That’s the only solution that works. Now I got the arrows working again.

unfortunately my site isn’t live yet.

I discovered the behaviour both on the contact form select and buddypress select fields but only when using the hueman theme.

If I delete all the form css from the style.css (master hueman theme), then the standard selct display appears. It seems the form fields including the select fields are styled with certain css but no down-arrow got included for the select fields. I wonder if there is a way to add a down-arrow for the dropdown select field, Unfortunately I can’t upload a screenshot here.

This is the standard css which is used to style the form fields

/*  base : forms
/* ------------------------------------ */
input, textarea, button, select, label { font-family: inherit; }
.themeform input,
.themeform select,
.themeform textarea,
.themeform button,
.themeform label { font-size: 14px; }
.themeform input::-moz-focus-inner,
.themeform button::-moz-focus-inner { border: 0; padding: 0; }
.themeform input[type="text"],
.themeform input[type="password"],
.themeform input[type="email"],
.themeform input[type="url"],
.themeform input[type="tel"],
.themeform input[type="number"],
.themeform input[type="submit"],
.themeform select,
.themeform button,
.themeform textarea { margin: 0; -moz-box-sizing: border-box; -webkit-box-sizing: border-box; box-sizing: border-box; -webkit-border-radius: 0; border-radius: 0; }
.themeform input,
.themeform select,
.themeform textarea,
.themeform button { -moz-appearance: none; -webkit-appearance: none; -moz-transition: all .2s ease; -webkit-transition: all .2s ease; transition: all .2s ease; }
.themeform input[type="checkbox"] { -moz-appearance: checkbox; -webkit-appearance: checkbox; }
.themeform input[type="radio"] { -moz-appearance: radio; -webkit-appearance: radio; }
.themeform label { font-weight: 600; color: #444; }
.themeform input[type="text"],
.themeform input[type="password"],
.themeform input[type="email"],
.themeform input[type="url"],
.themeform input[type="tel"],
.themeform input[type="number"],
.themeform select,
.themeform textarea { background: #fff; border: 2px solid #ddd; color: #777; display: block; max-width: 100%; outline: none; padding: 7px 8px; }
.themeform input[type="text"]:focus,
.themeform input[type="password"]:focus,
.themeform input[type="email"]:focus,
.themeform input[type="url"]:focus,
.themeform input[type="tel"]:focus,
.themeform input[type="number"]:focus,
.themeform select:focus,
.themeform textarea:focus { border-color: #ccc; color: #444; -webkit-box-shadow: 0 0 3px rgba(0,0,0,0.1); box-shadow: 0 0 3px rgba(0,0,0,0.1); }
.themeform label .required { color: #3b8dbd; }
.themeform input[type="submit"],
.themeform button[type="submit"] { background: #3b8dbd; color: #fff; padding: 8px 14px; font-weight: 600; display: inline-block; border: none; cursor: pointer; -webkit-border-radius: 3px; border-radius: 3px; }
.themeform input[type="submit"]:hover,
.themeform button[type="submit"]:hover { background: #444; }

.themeform.searchform div { position: relative; }
.themeform.searchform div input { padding-left: 26px; line-height: 20px; }
.themeform.searchform div:after { color: #ccc; line-height: 24px; font-size: 14px; content: "\f002"; position: absolute; left: 10px; top: 6px; font-family: FontAwesome; }

bdbrown, I know it’s till available. I’m running the current version. I was just wondering for the future.

I wonder if it would break anything changing from the full to the lite version.

But If I can’t use a header image anymore, I’d probably have to look for a different theme what would be disappointing. Would be nice if the new owner would reply. For me it’s just about the header image.

Thanks for your support but this doesn’t make any difference. The problem is not soundcloud but how the audio post format is set up. I think it would be a good idea for the theme creator if he could add soundcloud support to the audio post format. I know there are themes that do have audio post format support for soundcloud but these have too many other drawbacks for me.

I do not want to modify the /inc/post-formats.php because I fear I don’t have enough knowledge for that.

The site is still in production status, so it’s on localhost only.

Not sure if you got me right. Of course, I can add a soundcloud link into the content area of a post but I can’t use the Audio post format then. If I choose the Audio post format without attaching audio files, a non working audio player gets inserted. The Audio post format is only working if I attach .mp3 and .ogg files to the post. That’s why I can’t use it for soundcloud. I’m looking for a workaround for this.

it creates twitternametwittername<//a&gt instead of twittername

Thanks for your info. Is this a feature planned for the future or not at all? Right now the only option I see would be adding the Zip code to the city field according the standard address format of a country but this makes only sense if not allowing user transmission. I fear otherwise it would confuse users.

I think changing the formatting only works for one single country. But what I need is different formatting according to country’s adress standard formats.

I have events from different countries, so changing just the formatting doesn’t work for me.

Any other suggestions?