Forum Replies Created

Viewing 15 replies - 121 through 135 (of 141 total)
  • IT Hertz

    (@it-hertz)

    On second thought, and I haven’t tried this, but you may be able to mask the text using a borderless div layer with background-color that matches your page theme. You may be able to pull this off via table cells. Do let us know if it works.

    IT Hertz

    (@it-hertz)

    I think you meant beside the file select/explorer button. You can’t remove or edit this via WP plugin, because it’s browser-dependent. You’d have to hack the browsers.

    If you view your form in the various browsers, you’ll see that Chrome says “No file chosen”, FF says “No file selected”, and in IE it’s blank. In FF and IE, the attachment button label is “Browse”, while in Chrome it’s “Choose File”.

    IT Hertz

    (@it-hertz)

    As mentioned above, you need a supplemental plugin like this one.

    Keep in mind that a single attachment button will .zip the user’s file selections. You won’t be able to limit filetypes (unless you run some kind of filter on the .zip), which can be a security risk, since they could include executables.

    Of course, you could run a virus scan on the .zip prior to opening, but it’s still a hassle.

    I thought about using a single button for multiple files, and that linked plugin does work well, but decided on putting multiple buttons on my form instead, due to the above reasons.
    ____

    P. S. excuse the double-post; dunno what happened there, but I can’t delete the earlier one…

    • This reply was modified 8 years ago by IT Hertz.
    IT Hertz

    (@it-hertz)

    As mentioned above, you need a supplemental plugin like this one.

    Keep in mind that a single attachment button will .zip the user’s file selections. You won’t be able to limit filetypes (unless you run some kind of filter on the .zip), which can be a security risk, since they could include executables.

    Exactly what I needed for a new custom role, thanks!

    Thread Starter IT Hertz

    (@it-hertz)

    I set up a staging subdomain on my host and am experiencing the same issue, so it isn’t a wamp or local issue.

    I’ll give you a brief example.
    SKT parent main.css:

    /* Links------------------------------------------------- */
    a {color:#86c301; text-decoration:none; outline:none;}
    a:hover,a:focus,a:active {color:#eeeded; }
    
    /* NAVIGATION */
    #site-nav{ width:100%; margin:0; padding:0 0 60px; background:url(../images/menu-bg.png); text-transform:uppercase; font:300 16px 'Roboto Condensed', Arial; }
    

    My child css (I tried the modifications one at a time and none worked):

    /* Links------------------------------------------------- */
    a {color:#a3a3a3 !important; text-decoration:none; outline:none;}
    a:hover,a:focus,a:active {color:red !important; }
    
    /* NAVIGATION */
    #site-nav{ width:50% !important; margin:0; padding:0 0 60px; background:url(../images/menu-bg.png); text-transform:uppercase; font:300 12px 'Roboto Condensed', Arial !important; }
    

    All the above properties that come before !important do not work w/o the !important rule. As indicated, this applies to everything — color, text, size, classes, divs, etc.

    Though not shown here, my css does refer to the parent template in a comment line.

    I tried various enqueues — main.css only, style.css only, main plus style, even changed the filename of my modified css to main and style to match the parent being enqueued. Nothing works.

    Thread Starter IT Hertz

    (@it-hertz)

    I tried it last night with the free version of SKT Full Width theme, which has a vertical nav menu similar to KingSize, and am experiencing the same issue. I have to rule most properties !important in the child or they won’t work. Some do work w/o ruling them !important, and some don’t work even when I do rule them !important.

    I’ve looked for, among other things, specificity/hierarchy conflicts and can’t find what is preventing my child css from controlling.

    I also tried using Child Theme Configurator. It’s supposed to account for older themes that need @import and set them up accordingly. No joy; I have the exact same !important issue as when I install the child manually.

    I can, of course, keep using !important for the stubborn properties and perhaps use workarounds for those with which even !important doesn’t work, but I prefer to keep my css clean and eliminate !important rules as much as possible.

    Thread Starter IT Hertz

    (@it-hertz)

    Hello,

    It’s a premium theme (KingSize). I’m working on replacing it with a public domain theme, but have not tried a child theme with that one yet. My support period expired with the KS folks, and since I’m replacing it, I’m not going to pay for additional support from them.

    It isn’t a serious problem, since I can just use the modified parent theme until I perfect the replacement theme’s child (assuming I don’t have this problem with that one as well). I was just curious as to why this odd behavior is occurring.

    I neglected to mention that I’m using wamp to build/alter the site. I don’t see how that could be the culprit, since the only changes are css, but I suppose it might be.

    The hosting plan for this site is not multi-site and I can’t trash the live site by switching to a defective child. I could probably install the child on a subdomain for sandboxing, though.

    Thread Starter IT Hertz

    (@it-hertz)

    My mistake. I see that hovering over the path in the Foxit popup does reveal the full path. ugh…

    Thread Starter IT Hertz

    (@it-hertz)

    update: Nope, not working on live site, either. No matter what I try with this plugin, the upload path stays at default.

    Thread Starter IT Hertz

    (@it-hertz)

    I ended up just using CSS to eliminate the separator line (border) between the ticker and the menu item above it, so that the ticker appears to be in the “host” item’s Description area.

    Thread Starter IT Hertz

    (@it-hertz)

    I ended up just doing it with CSS alone to eliminate the separator border between the shortcode item and the item above it.

    Thread Starter IT Hertz

    (@it-hertz)

    Ok, I managed to get the ticker in the Description space by inserting the following above the similar <h6> line in menu-walker.php: $description = ! empty( $item>description ) ? '<div class="desc menuticker '.$selc.'">'.do_shortcode( $item->description ).'</div>' : '';
    and then commenting out the original line.

    With a little CSS magic, some div work and the has_shortcode function, it shouldn’t be too difficult to have a customized menu description and/or shortcode ticker in the description area and make it clickable or not.

    Thread Starter IT Hertz

    (@it-hertz)

    I tried to do this via CSS and simply remove the item separator line from above the shortcode and then negative margin the ticker up to where the item description normally resides, but that didn’t go well.

    I then tried using this plugin’s function has_shortcode( $content ) { and inserted the $item_output = do_shortcode( $item->description ); into my theme’s menu-walker.php, but no joy. 8-/

    Thread Starter IT Hertz

    (@it-hertz)

    I’ll concede it may have been a bit unfair of me to expect compatibility with premium themes, since most devs wouldn’t shell out money on a lot of premium themes just to ensure compatibility.
    If I could remove the review, I would, but I don’t see that option, so I’ll bump the rating in view of the positives that I previously mentioned.

Viewing 15 replies - 121 through 135 (of 141 total)