Tag Info

New answers tagged

0

Given the amount of customization you're looking to make, your best bet may be to integrate a custom Walker function. From the Codex: For deeper conditional classes, you'll need to use a custom walker function (created in the 'walker' => new Your_Walker_Function argument). The easiest way to build a new walker function is to copy the default ...


0

I have had this issue before, the best solution is creating custom divs for the buttons and styling them differently overiding the defaults. This approach gives you control when you are theming and also helps you control different button colors and hover effects especially when you want to have a different color for each button.


0

You might wanna check : https://wordpress.org/plugins/tabsy/ . It's a responsive tab and shortcode ready so you don't have to add the code manually. I hope this helps. Thanks! Cheers, phpbits


0

Well first of all that CSS looks a little strange, you should only require: background: #DB397E !important; There are two parts to this problem, one is that the original rules are set to !important which means that your !important will not override it. (This also tells me that there is probably somewhere in your theme control panel that you can modify ...


0

For loading bellows script & style add bellows code on theme functions.php file. function add_e2_date_picker(){ //jQuery UI date picker file wp_enqueue_script('jquery-ui-datepicker'); //jQuery UI theme css file wp_enqueue_style('e2b-admin-ui-css','http://ajax.googleapis.com/ajax/libs/jqueryui/1.9.0/themes/base/jquery-ui.css',false,"1.9.0",false); } ...


0

It's very similar to how you set / access theme options: http://codex.wordpress.org/Function_Reference/update_user_option setting: update_user_option( $user_id, $option_name, $newvalue, $global ) <- taken from wordpress codex. and getting : http://codex.wordpress.org/Function_Reference/get_user_option get_user_option('color_option', $userID); To ...


1

CSS was indeed the issue. It works fine on a stock WP installation and I was finally able to track down the conflict with this developed site.


2

Achieving unaltered style via plugin for multiple themes is pretty difficult to achieve. How about this? Use any library among these e.g. Bootstrap in your plugin and then remove/comment the global properties from them. Since you will be author of the plugin, you can repeat the same thing in your plugin before releasing next update.


0

The problem you are seeing is that you have your declarations of the same importance from a CSS standpoint. If you add another style to give it more preference: #cqrm-current-item-list tr.cue-deletion.cue-coming-soon, #cqrm-current-item-list tr.cue-deletion.tr.cue-coming-soon *{ background-color: #fbb !important; filter: alpha(opacity=100) !important; } ...


0

From the spec: "EM is Equal to the computed value of the ‘font-size’ property of the element on which it is used." You have a different font-size value between the two URLs you provided (14px and 10px respectively). Line 273 of your style.css file is replacing the default Bootstrap font-size for the body element (line 5 of bootstrap.min.css).


1

The comment from @milo prompted me to take a closer look, and I realised I was chasing a false positive. The About page and Contact page were actually displaying the correct behaviour; it was Home and Services that were wrong. It seems at some point those two pages did have custom page templates, which were later turned into specialized page templates. ...


0

Without all the info of what is actually happening I'm assuming that the title is output with the Song Artist and the Song Name together. But like you said with a dash in the middle. With that assumption, then you can accomplish this with a custom function that filters the_title before it's output. Try putting this in your functions.php file: function ...


0

You have to put song title into <span> tag and .classOfContainer span{color:red;}


0

Try enqueuing your child theme's CSS like so: // Queue parent style followed by child/customized style add_action( 'wp_enqueue_scripts', 'theme_enqueue_styles', PHP_INT_MAX); function theme_enqueue_styles() { wp_enqueue_style( 'parent-style', get_template_directory_uri() . '/style.css' ); wp_enqueue_style( 'child-style', ...


0

You can use a more specific selector in your child theme's CSS so that it takes precedence. So instead of: .wp-caption { background: #2d2d2d !important; } Use: .entry .wp-caption { background: #2d2d2d; } You'll also want to be sure to enqueue your child theme stylesheet in your functions.php file if you aren't already. ...


0

There is a simple solution available in WordPress : add_image_size You can register as many sizes required in your theme, WordPress will generate the images in that size and crop it if crop is enable for that size. You can use regenerate thumbnails plugin to generate all the image sizes for older posts. Please check codex for more info.


0

The styles for the admin bar are generally printed in the head of the site, so perhaps your CSS code is being undone as the printed styles for the admin bar appear after your included style sheet. Maybe by using the wp_head action you can stop this, placing something like this in your functions file may do the trick: function modify_admin_bar_css() { ...


2

The following workaround is based on the wpeditimage/plugin.js file in the core. You could enqueue it or test it with: add_action( 'admin_footer-post.php', function() {?><script> jQuery(window).load( function( $ ) { if( ! $( "#wp-content-wrap").hasClass("tmce-active" ) ) return; var editor = tinyMCE.activeEditor; ...


0

I found this function which gets rid of the 32px 'bump' left over after using "show_admin_bar(false)" remove_action('wp_head', '_admin_bar_bump_cb'); That seems to do the job!


0

With add-on domain you probably mean a domain alias, right? Set your WP_HOME and WP_SITEURL to a dynamically value in your wp-config.php. This is how it's done, I use this code all the time it also will define some other constants. $root='public_html'; //Set this to the DocumentRoot. define('FTP_USER','<username>'); //Replace <username> with ...


1

Very helpful and thanks for defaultstyles pointers. I found merging arrays wasn't working until converting those default options to valid JSON (not valid JavaScript). Below allows appending the WordPress tinymce's drop-down instead of replacing Default options (JSON): $defaults = '[{ "title": "Headers", "items": [ { "title": "Header 1", ...



Top 50 recent answers are included